What Is My Public IP?

Seeing the public IP your browser uses

Your public IP is the address the wider internet sees when your browser makes a request. On home networks it is often the router’s WAN address; on mobile data it may belong to a carrier pool shared by many subscribers.

This page detects that address and runs a standard lookup for approximate city, region, and organisation. If you use a VPN, the IP and location will reflect the VPN exit, which is exactly how the internet routes your traffic while the tunnel is up.

For private LAN addresses (192.168.x.x and similar), look at your device or router settings — those never appear as the public IP on a website.

Worked examples

• The Equator — is 40,075 km around — the yardstick that makes great-circle distances legible: New York to London is about 14% of it.
• One degree of latitude — is ≈ 111 km everywhere; one degree of longitude shrinks with cos(latitude), ≈ 55 km at 60°N — the reason flat approximations fail.
• Antipodal pairs — are always ≈ 20,015 km apart, the maximum possible surface distance, whoever and wherever you are.

Understanding IP addresses, geolocation and network details

An IP address identifies a network connection on the Internet, not a precise physical person or address. Public IP lookup services can associate an address with a country, region, city, autonomous-system number, ISP or organization using routing and geolocation databases. These fields are estimates and can be affected by VPNs, mobile networks, carrier-grade NAT, proxies and corporate gateways.

IP geolocation is different from browser GPS. A browser can request device location with permission and may achieve much finer accuracy, while an IP database usually identifies the approximate area associated with the network. For that reason, IP results should be treated as network context rather than proof of where a person is physically standing.

Network metadata also changes over time. ISPs reassign addresses, organizations change providers and geolocation databases update their records. When accuracy matters, compare multiple signals and check the date and source of the data instead of treating an IP lookup as a permanent address record.

Tips & common mistakes

Treat IP geolocation as an estimate of the network, not a precise physical address. VPNs, mobile carriers, proxies and corporate gateways can place an IP far from the actual device.

Use browser GPS when you need device-level location and permission is available; use IP lookup when you need public network context such as ISP, ASN or approximate region.

IP assignments and geolocation databases change. Record the lookup time and source when network location is used for analysis or troubleshooting.

Reading IP lookups without over-trusting them

An IP address names a network attachment on the Internet, not a street address or a person. Public lookup services map that address to country, region, city, ISP, ASN and organisation using routing tables and commercial geolocation databases. The result is network context: useful for abuse triage, fraud signals, content localisation and rough audience analysis, and dangerous when treated as proof of physical presence. VPNs, mobile carriers, carrier-grade NAT, corporate proxies and anycast edges routinely place the reported city hundreds of kilometres from the user.

The professional habit is triangulation and provenance. Compare the IP result against browser geolocation (when the user grants it), against a second database, and against the AS organisation's known footprint. Print the database vintage and the confidence band if the provider supplies one. Never store the raw IP longer than the investigation needs, and never present a city-level IP pin as if it were a GPS fix — the map and the language both matter.

How professionals use this

• Treat IP geolocation as network context, not physical proof of presence.
• Cross-check against a second source and against the AS organisation when the decision matters.
• Record the lookup time and database source; these datasets change.
• Prefer ASN and organisation fields for abuse and infrastructure questions; they age better than city pins.

Step-by-step masterclass

1. 1. Treat the result as network context — An IP lookup names an attachment point on the Internet, not a street address. State that distinction before acting on a city or region field.
2. 2. Cross-check when the decision matters — Compare against a second geolocation database and against the ASN organisation footprint; single-source city pins are weak evidence.
3. 3. Prefer ASN and organisation fields — They age better than city guesses and are usually more useful for abuse, infrastructure and fraud triage.
4. 4. Record time and source — Geolocation datasets change; a lookup without vintage is hard to audit later.
5. 5. Never present an IP pin as GPS — Language and map styling both matter — keep IP results visually distinct from device location.

IP geolocation coverage is densest in North America and Europe and thinner in parts of Africa, South Asia and rural networks. Mobile carriers and CGNAT pools often resolve to a single city for large regions, so the reported city can be hundreds of kilometres from the subscriber.

Related questions people ask

Quick glossary

Public IP

An Internet-routable address visible to external services.

ASN

Autonomous System Number identifying a network operator or routing organization.

IP geolocation

An estimate of the geographic area associated with an IP address.

Carrier-grade NAT

A network setup where many customer devices share public IPv4 addresses.

ASN

Autonomous System Number — the routing domain that announces the address space.

CGNAT

Carrier-grade NAT, where many subscribers share one public IP.

Honest limits & when to escalate

IP geolocation and network lookups have a hard competence boundary: they describe the network attachment, not the person or the precise street. City and region fields are database estimates that degrade under VPN, mobile, CGNAT and anycast. Treating an IP city pin as a GPS fix is the most common misuse.

Within that boundary the tools are useful for triage, localisation and rough audience analysis when the limitations are stated. Escalation for high-stakes identity or location claims is always offline verification, legal process or device-level consent — never an IP database alone.

• Legal or identity claims → due process and offline verification, not IP databases.
• Precise user location → browser GPS with consent, never IP alone.
• Abuse at scale → multiple telemetry sources and your own threat intel.
• Regulatory geoblocking → licensed geo databases with contractual SLAs.

Data & methodology note

Public IP metadata is supplied by the IP lookup service and represents an approximate network location; VPNs, proxies, mobile networks and reassignment can reduce geographic accuracy.

Category: IP & Network — IP geolocation and network details. This page is part of MapBench's ip & network tools. Related tools below and the Tools menu link every sibling instrument.

Continue with related tools

• IP Address Lookup — Approximate location, ISP and network details for a public IP.
• Find My Location — See your current position on the map with live coordinates and nearest address.