Website server location checker

Where is my website actually served from?

DNS records, A/AAAA lookups and the final response IP — a focused scan for engineering and ops, not a full compliance report.

Endpoint, NS records and MX records are listed separately. Edge ≠ origin.

https://
Homepage only · Usually under 10 seconds

Website server location checker

DNS records, A/AAAA lookups and the final response IP — a focused scan for engineering and ops, not a full compliance report.

Edge ≠ origin

A "Frankfurt" endpoint may be a Cloudflare or Fastly anycast edge. The IP may be registered in the US even though the edge serves EU traffic from Frankfurt. We label known CDN ranges directly ("X CDN") so this confusion does not silently mislead a reviewer.

NS and MX are context, not a verdict

DNS hosting does not imply customer data processing, and MX records do not show where your form submissions are sent. We list them under "context" and exclude them from the geographic verdict. The verdict uses only the homepage endpoint and observed third-party endpoints.

Frequently asked questions about this angle

  1. Why do NS or MX records get excluded from the verdict?

    They tell you who hosts your DNS and who accepts your email — not where user data submitted through your website ends up. Mixing them into the same count as the homepage endpoint would distort the signal.

  2. Can I tell edge from origin in the result?

    When the IP matches a known CDN range (Cloudflare, Fastly, Akamai, Imperva, Bunny), we annotate the row with the CDN name and say "edge" in plain language. Otherwise we report the geolocation as found.

  3. Why does the homepage IP sometimes geolocate to a different country than expected?

    Anycast networks serve from many regions but are commonly registered to one. Public geo-databases reflect registration, not current serving location. The annotation with the CDN name flags this explicitly.