Skip to content
AdminKit

What does your IP lookup result actually show — and how accurate is it?

A public IP lookup, like AdminKit's what-is-my-IP tool, shows your address plus three fields derived from the address by the network, not read from your device: the ASN (network operator identifier), an organization name (usually your ISP or cloud provider), and an approximate location estimated from registry and geolocation data — not GPS, and often a city or country off.

By AdminKit team, Netbase JSC · Updated

Key takeaways

  • Only the IP address is observed directly. The ASN, organization name and location are looked up for that address and describe the network, not your device.
  • The organization is whoever holds the ASN, which can be a parent company or wholesale network rather than the brand on your bill.
  • Location is an estimate for the address block, usually at city or region level and sometimes wrong by a country, especially on mobile networks.
  • A web-based lookup sees one connection, so it shows either your IPv4 or your IPv6 address, whichever your browser used for that request.
  • Private, CGNAT and other special-purpose addresses aren’t routed on the internet, so a lookup normally shows the public address they were translated to.

What does an IP lookup result actually contain?

A “what is my IP” result packs together one directly observed fact and several derived ones, and telling them apart is the key to reading it correctly. The IP address itself is observed directly — it’s literally the address the request arrived from. The ASN, organization name, and approximate location, by contrast, are all looked up separately once the address is known, which is why they can occasionally look inconsistent with each other (a mobile carrier’s location, for instance, is often a regional hub rather than any specific customer’s city) even though each field is accurate to what it actually measures.

AdminKit’s what is my IP tool shows these fields. The address comes from the connection itself, and the rest is the request metadata that Cloudflare, which serves the site, attaches to every request; its Workers documentation describes each property. AdminKit makes no other lookup and stores nothing.

Field shownWhere the value comes fromObserved or derived?
Your public IPThe address the request arrived fromObserved
ProtocolIPv6 if the address contains :, otherwise IPv4Observed
Network (ASN)Cloudflare’s asOrganization and asn propertiesDerived from routing and registry data
Approximate locationCloudflare’s city, region and two-letter countryEstimated
ConnectionHTTP version and TLS version of this requestObserved

Behind the page, the tool reads a small JSON response. Example output (illustrative, documentation address and ASN):

{
  "ip": "203.0.113.45",
  "isIPv6": false,
  "asn": 64500,
  "asOrganization": "Example Broadband",
  "city": "Hanoi",
  "region": "Hanoi",
  "country": "VN",
  "httpProtocol": "HTTP/2",
  "tlsVersion": "TLSv1.3",
  "cgnatHint": false
}

The page shows this as “Example Broadband (AS64500)” for the network and “Hanoi, Hanoi, VN” for the location. A field the network data doesn’t have is shown as “Unknown” rather than guessed.

What does the ASN tell you?

It tells you which network operates the address. An ASN (Autonomous System Number) identifies a specific network operator and its own routing policy — the identifier BGP, the protocol that routes traffic between networks across the internet, uses to distinguish one operator’s address space from another’s. Every IP address on the public internet falls within some organization’s announced block, and that organization is who actually controls routing for it: a residential ISP, a mobile carrier, a cloud or hosting provider, a university, or a large enterprise running its own network.

Looking up the ASN behind an address is often more useful than the IP alone when judging what kind of connection you’re looking at — a cloud-provider ASN behind a request looks very different from a residential-ISP ASN, even if neither IP individually reveals that at a glance. If you’re connected through a VPN or a corporate proxy, the ASN will be the VPN provider’s or your employer’s network, not your home ISP, because the lookup sees wherever your traffic leaves for the internet.

Why is the organization name not my ISP’s brand?

Because the name belongs to whoever holds the ASN, as registered with a regional internet registry (ARIN — see its guide to autonomous system numbers — RIPE NCC, APNIC, LACNIC or AFRINIC), not necessarily the consumer-facing company name on your bill. Cloudflare’s documentation describes asOrganization as “the organization which owns the ASN of the incoming request.” Large ISPs sometimes register address space and ASNs under a parent company, a wholesale network-infrastructure subsidiary, or an older corporate name retained from a merger.

Mobile carriers are a frequent source of this confusion: a carrier’s data traffic is often routed through infrastructure registered to a distinct network-operations entity, so a phone’s IP lookup can show an unfamiliar name even though the carrier itself hasn’t changed. None of this indicates a problem with your connection — it’s simply how registration works. For the full registration record of the address block, rather than the one-line summary, AdminKit’s WHOIS/RDAP tool returns the allocation detail. RDAP answers are structured JSON defined in RFC 9083, including the network’s start and end addresses, its name, and the registered entities (such as abuse and technical contacts) attached to it.

Why is the location wrong, and what is it based on?

The location is an estimate for the whole address block, so it is often a city, a region or occasionally a country away from you. Unlike a smartphone’s GPS, an IP-based location has nothing to do with satellites, WiFi scanning, or anything your device reports. Geolocation databases build their estimates from network data: registry records and location feeds that operators publish for their own blocks in the format defined by RFC 8805, one line per prefix with country, region and city, for example 192.0.2.0/24,VN,VN-HN,Hanoi,.

ISPs typically describe blocks at a regional or metro level, not per household, and mobile carriers often route an entire region’s traffic through a comparatively small number of gateway points, each serving a wide geographic area. MaxMind, a geolocation data provider, notes on its accuracy comparison page that “IP geolocation for cellular IPs is less accurate than broadband IPs due to the wider allocation area of cellular IPs,” and publishes accuracy figures per country and radius rather than a single number.

CauseWhat you seeIs anything wrong?
Block registered or described at regional levelNearby large city instead of your townNo
Mobile carrier gatewayCity hundreds of kilometres away, or the capitalNo
VPN or proxy serviceLocation of the exit point you chose or were givenNo, unless you didn’t set it up
Block recently moved between operators or regionsOld city or country until the data is refreshed; RFC 8805 §3.4 suggests consumers refresh feeds at least weeklyNo, the data lags
Corporate network with a central internet exitHead-office locationNo

A result showing a different city, a neighboring region, or in less common cases a different country than your actual physical location is a normal consequence of this approach, not a sign of a compromised account or anything else requiring action. The one row to look at twice is the VPN row: if the location matches a VPN exit and you don’t use one, check your browser extensions and network settings.

Why does the result show IPv4 or IPv6, but not both?

Because a web page sees exactly one connection, and that connection uses one protocol. The internet runs two separate addressing protocols at once today: IPv4 (RFC 791), the original and still most widely used, with a limited ~4.3 billion address space that has been fully allocated for years; and IPv6 (RFC 8200, also on the IETF Datatracker), designed with a vastly larger address space specifically to outlast IPv4 exhaustion.

A connection that has deployed both protocols at once is called “dual-stack.” On a dual-stack connection the client picks one protocol per connection; under the Happy Eyeballs algorithm in RFC 8305, it tries both while “preferring the use of IPv6.” So a lookup from a dual-stack network usually shows your IPv6 address, and seeing IPv4 doesn’t prove you have no IPv6. AdminKit’s tool says which protocol the request used, and when it was IPv4 it explains that a separate IPv6-only test is the reliable way to confirm IPv6. A network that hasn’t deployed IPv6 shows only IPv4; some newer mobile networks have flipped the other way and run IPv6 as primary internally while still supporting IPv4 connectivity through translation. Seeing only one of the two reflects your current network and this one request, not a fault in the lookup itself.

What you seeMost likely situation
IPv6 addressDual-stack or IPv6-only network; browser used IPv6
IPv4 addressIPv4-only network, or dual-stack and the browser used IPv4 this time
IPv4 address with the shared-IP hintLikely carrier-grade NAT or a mobile carrier

Why doesn’t my router’s address match the lookup?

Because the address on your devices, and often on your router, is from a range that isn’t routed on the public internet, and something translates it on the way out. Several ranges are reserved for exactly this, listed in the IANA IPv4 Special-Purpose Address Registry that RFC 6890 set up. Addresses in these ranges aren’t routed on the public internet, so a lookup normally shows the public address they were translated to instead:

RangePurposeDefined in
10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16Private networks (home, office)RFC 1918
100.64.0.0/10Shared Address Space for carrier-grade NATRFC 6598
169.254.0.0/16Link-local (no DHCP answer)RFC 3927
fc00::/7IPv6 unique local addressesRFC 4193
192.0.2.0/24, 2001:db8::/32Documentation examples onlyRFC 5737, RFC 3849

If your router’s WAN address is in 10.x, 192.168.x or 100.64.0.0/10 and differs from the lookup result, your ISP is translating it for you, often for many customers at once. AdminKit’s tool shows a “this IP may be shared” hint when the address it sees falls in 100.64.0.0/10 or when the network’s organization name matches a short list of known mobile carriers; both are hints, not certainties. To classify any single address against these ranges, AdminKit’s IP address info tool does it in your browser.

What doesn’t an IP lookup tell you?

A public IP lookup reads only what’s present in the web request itself — the connecting address and the metadata associated with it — and queries no tracking database, installs nothing, and reveals nothing about your device beyond what any server you connect to already sees on every request. It also doesn’t confirm whether the address is shared with other customers behind the same connection; if you’re trying to understand why an IP-based result (a blacklist hit, an unreachable forwarded port) might not be exclusively about your own traffic, that’s a separate, carrier-side NAT question covered in what CGNAT is and why it confuses sites. Nor does it tell you which DNS resolver your device uses; that needs a separate test.

And because a public IP can change at any time depending on your ISP’s allocation policy, a single lookup only describes the address you have right now — see dynamic IP vs CGNAT vs static for what that means if you need to track an address over time. Run AdminKit’s what is my IP tool to see your own current result read this way, or see the best free what-is-my-IP tools comparison for how that result compares to other free lookups like ifconfig.co. This guide is part of AdminKit’s DNS cluster of DNS and IP-lookup guides and tools.

This guide is general information, not a security audit of your specific network — see our disclaimer for what AdminKit's guidance does and does not commit to.

Frequently asked questions

What is an ASN, and why does my IP lookup result show one?

An ASN (Autonomous System Number) identifies a specific network operator's block of IP addresses and its routing policy on the internet — the number BGP, the protocol that routes traffic between networks, uses to tell one operator's address space apart from another's. Showing the ASN behind your IP tells you which network actually operates it: a residential ISP, a mobile carrier, or a cloud platform, which is often more informative than the IP address alone.

Why does the 'organization' or 'ISP' field sometimes show a company I don't recognize?

The organization name is the holder of the network's ASN, as registered with a regional internet registry, which isn't always the retail brand you actually pay. A residential ISP's address blocks are sometimes registered under a parent company or a wholesale network-infrastructure name rather than the consumer-facing brand, and mobile carriers in particular often route traffic through infrastructure registered to a different entity than the one on your phone bill.

Why does the location shown not match where I actually am?

Location in an IP lookup is an estimate for the address block an IP belongs to, built from network data such as registration records and the locations operators publish for their blocks — not from GPS, WiFi positioning, or anything your device reports. ISPs and especially mobile carriers frequently register one address block to a single regional hub that serves a much wider area, so a result can legitimately show a different city, region, or occasionally even country than your physical location, without indicating anything is wrong.

Why does my IP lookup show only an IPv4 address, or only IPv6, or both?

It depends on what your current connection actually has, and on which protocol your browser used for this one request. Many networks are 'dual-stack,' meaning your device has both an IPv4 and an IPv6 address at once; a page like AdminKit's what-is-my-IP tool sees only the address the request arrived over, so it shows one of the two and tells you which. A network that hasn't deployed IPv6 yet will only ever show IPv4; one running IPv6-only internally (increasingly common, especially on mobile) may show only IPv6. Neither case indicates a problem — it reflects what your ISP has actually deployed.

Does a 'what is my IP' check see anything beyond what's in the request itself?

No — a lookup like this reads only what's already present in the web request reaching the server: the connecting IP address and the network metadata (ASN, organization, approximate location, HTTP and TLS version) that Cloudflare's network attaches to each request it handles. AdminKit makes no separate lookup of its own, does not query a device or install anything, and stores nothing; the response is sent with Cache-Control: no-store.

Want AdminKit to watch this for you?

Free checks tell you the state today. Protective DNS and monitoring tell you when it changes.

Huy Nguyen (David), Founder and CEO of Netbase JSC

Talk to an expert

Huy Nguyen (David), Founder & CEO, Netbase JSC

Ask whether this fix applies to your setup, or get a second pair of eyes on your DNS and mail records.