Real-Time Network Identity & Geolocation

IP Dashboard & Geolocation Map

Inspect your public WAN IP, probe local private LAN interfaces via WebRTC ICE candidates, and view your exact ISP Point of Presence on an interactive OpenStreetMap.

Public Internet Gateway

Public WAN IP Address

Detecting Public WAN IP...
Client Host Discovery

Private LAN IP (WebRTC Probe)

Probing STUN/ICE...
Probing...
Probing local host candidates via browser RTCPeerConnection...
Browser Security Context: Modern web standards prevent random websites from probing your physical internal LAN (e.g. 192.168.1.x) without media permissions. If your browser returned an .local UUID, Chrome/Firefox is actively shielding your network fingerprint via RFC 8828 mDNS anonymization.

ISP Point of Presence (PoP) Map

Rendered via Leaflet.js & OpenStreetMap

Zero Cost • Free API
Determining WAN coordinates...
Companion Network Probes:

What is IP Geolocation Accuracy? Why Coordinates Don't Show Your Street Address

Users frequently wonder why an IP lookup service places their marker several miles or even cities away from their physical residential location. Unlike GPS on smartphones, which computes position using satellite trilateration down to a 3-meter accuracy radius, IP geolocation relies on tabular BGP routing databases and Internet Service Provider (ISP) network topology.

ISP Point of Presence (PoP)

Your residential modem routes all traffic to your ISP's nearest aggregation router (Broadband Network Gateway or BNG). The public IP belongs to this facility, placing your pin at the data center rather than your house.

Carrier-Grade NAT (CGNAT)

Cellular LTE/5G carriers and modern fiber ISPs pool thousands of subscribers behind a single shared public IPv4 address block (RFC 6598: 100.64.0.0/10), so multiple cities may share the same WAN endpoint.

BGP Anycast Routing

CDNs and modern VPNs announce the exact same IP address from hundreds of data centers globally. A lookup for a Cloudflare or Google DNS IP (1.1.1.1 or 8.8.8.8) maps to whichever Anycast node is topologically closest to the querying client.

Private vs. Public IP Ranges: RFC 1918 & Reserved Network Allocations

Addresses reserved by the Internet Engineering Task Force (IETF) and IANA for internal subnets and diagnostics.

RFC StandardIP Range / CIDR BlockUsable Host CapacityIntended Application & ScopeRoutable on Internet?
RFC 1918 (Class A)10.0.0.0/816,777,214 hostsLarge enterprises, AWS/GCP VPCs, corporate VPNsNo (Filtered by ISPs)
RFC 1918 (Class B)172.16.0.0/121,048,574 hostsMid-sized data centers, Docker default bridge networksNo (Filtered by ISPs)
RFC 1918 (Class C)192.168.0.0/1665,534 hosts (256 x /24)Home Wi-Fi routers, SOHO switches, local IoT subnetsNo (Filtered by ISPs)
RFC 6598 (CGNAT)100.64.0.0/104,194,302 hostsISP-level carrier network address translationNo (Transit internal)
RFC 3927 (Link-Local)169.254.0.0/1665,534 hostsAPIPA auto-configuration when DHCP server is offlineNo (Broadcast only)
RFC 1122 (Loopback)127.0.0.0/816,777,214 hostsInternal host loopback interface (localhost)No (Host internal)
Public WAN IPAll other IPv4 / IPv63.7 Billion IPv4 / 2^128 IPv6Globally accessible servers, websites, edge gatewaysYES (Globally Routable)

How WebRTC Discovers Local Network IPs & The RFC 8828 Privacy Standard

When WebRTC (Web Real-Time Communication) was introduced to browsers in 2011, it allowed two peers to establish low-latency video and audio streams directly without passing through a relay server. To do this, the browser gathers Interactive Connectivity Establishment (ICE) candidates by binding to every physical network interface (Ethernet, Wi-Fi, VPN adapters).

Historically, this created a major privacy vulnerability known as the WebRTC Local IP Leak: any website could silently run a background JavaScript snippet without requesting microphone or camera permissions, harvesting the user's internal LAN subnet (192.168.1.45) and tracking them across incognito sessions or VPN connections.

To eliminate this leak, the IETF ratified RFC 8828 (WebRTC IP Address Handling Requirements). Modern browsers (Chrome 75+, Firefox 68+, Safari 13+) now generate randomized Multicast DNS (mDNS) UUID hostnames—such as 7cf24e69-12f8-4b71-9b16.local—shielding the true underlying IP from untrusted scripts while preserving peer-to-peer connectivity on local subnets.