This page shows the public IP address your device is using to reach this site, along with an approximate location and network owner derived from that address. This is the address websites, and anyone you connect to, see — not your device's private local network address.
The reverse DNS (PTR record) lookup tries to resolve a hostname associated with your IPv4 address specifically — IPv6 reverse lookups use a much longer, sparser record format that's rarely populated, so it's skipped. Most residential and mobile connections don't have a PTR record set, so "No PTR record found" is normal; ISPs, data centers, and servers usually do.
This information is read directly from the network request when it reaches our server — no third-party tracking or geolocation service is used, and nothing is stored. Your browser only ever connects over one protocol at a time, so the address for the other family (when shown) comes from a separate, public IPv4-only / IPv6-only lookup rather than from this server — that's also why only your active connection's family has location and ISP details attached.
How accurate is the location shown?
It's an approximate location derived from IP geolocation databases, typically accurate to city or region level — not a precise address, and can be off for VPNs, mobile networks, or corporate proxies.
Why does my IP look different from my ISP-assigned address?
If you're behind a VPN, proxy, or CGNAT, the IP shown is the address your traffic exits from, not necessarily the one assigned directly to your device.
What is reverse DNS used for?
It maps an IP address back to a hostname, which can reveal the hosting provider or ISP associated with that address — useful for diagnosing network or spam-filtering issues.