// METHODOLOGY

What Is My IP

How your public IP address is detected on page load, and why the location shown may not be yours.

Open the What Is My IP toolRuns: on our server

// What is tested

  • The public IP address your connection presents to this server, taken from the proxy headers Vercel sets on the request.
  • If those headers do not carry a usable public address — on a local network, or where the address is private or reserved — the geolocation provider is asked to report the address it sees instead. The result records which of the two was used.
  • Country, region and city associated with that address, plus the ISP or hosting provider and the ASN that announces it.
  • The reverse DNS (PTR) hostname for the address, when one is published. This is best-effort: a failure here does not fail the rest of the result.

// Data sources

Request headers
The client address as seen by the hosting platform. This is the address of whatever last relayed your traffic — a VPN exit, a corporate proxy or a mobile carrier gateway, if one is in the path.
IP2Location
Commercial IP geolocation database, queried live per lookup for country, region, city, ISP and ASN.
DNS over HTTPS
Cloudflare (1.1.1.1) with Google Public DNS as fallback, used for the reverse DNS lookup.

// Limits

  • The address shown is where your traffic enters the public internet, which is not necessarily where you are. VPNs, corporate networks and mobile carriers all move it, sometimes by hundreds of kilometres.
  • City-level placement is inferred rather than recorded, and is the least reliable field. Country is the field to trust.
  • Nothing here identifies a person or a household. It describes a network.
  • Results are not cached — the response is marked no-store — so a reload re-runs the whole lookup.