Your public IP with ISP, ASN, country, reverse DNS, and a VPN/datacenter check — rendered on the server the moment the page loads.
Your public IP address is
216.73.216.69
You are connected over IPv4. If your network is dual-stack, your other-protocol address is not visible on this connection.
Your IP shows infrastructure indicators — see the VPN detector for details.
See the full analysis in the VPN detector →ASN and country data from the local routing snapshot (2026-07-14); nothing is sent to third parties to identify you.
Need this via API? Let us know — we're gauging demand.
The address at the top is your public IP — the source address on the packets this page request arrived with. Unlike most "what is my IP" sites, everything here is rendered server-side from that single request: no JavaScript beacons, no third-party lookup APIs called from your browser, and the page is marked non-cacheable so you never see another visitor's data.
The provider line shows the autonomous system that announces your address into the global BGP routing table. This is the network that actually carries your traffic — usually your ISP, but if you're on a VPN or corporate proxy it will name the hosting provider running that infrastructure instead. That difference is exactly how the anonymity check below it works: residential ISPs and datacenter operators occupy clearly distinct ASNs.
Reverse DNS (PTR) is the hostname your ISP assigned to your address, resolved
live. Consumer connections typically have generated names like
host-203-0-113-9.fiber.example-isp.net; a missing PTR record is normal and harmless.
The connection type combines the ASN classification with naming conventions in
the PTR record — "dsl", "cable", "ftth", or "mobile" in the hostname are strong hints about the
access technology.
Practical uses for knowing your public IP: configuring firewall allowlists and
sshd access rules, setting up port forwarding or dynamic DNS for self-hosted
services, verifying that your VPN actually changed your egress address (reload this page after
connecting — the ASN should flip from your ISP to the VPN's host), debugging geo-blocking
issues, and confirming whether your ISP has put you behind CGNAT, which breaks inbound
connections entirely.
IP-to-ASN and country data come from a local snapshot of RouteViews-derived routing data, refreshed with each deployment. City-level location, when shown, is approximate by nature — see the FAQ below for why.
Your public IP is the address the rest of the internet sees when your traffic leaves your network. It's assigned by your ISP to your router (or to a carrier-grade NAT gateway shared with other customers). Devices inside your home use private addresses like 192.168.x.x, which are translated to the public IP by NAT.
Your computer shows its local (private) address on your LAN — typically 192.168.x.x, 10.x.x.x, or 172.16-31.x.x. The public address shown here is what your router presents to the internet after NAT. If your ISP uses CGNAT (common on mobile and fiber), thousands of customers may even share one public IPv4 address.
No. IP geolocation identifies the country reliably and often the city of your ISP's aggregation point, but not your street address. The city shown can be tens of kilometers off, because databases map ISP infrastructure, not homes. Only your ISP can link an IP to a subscriber, and that requires legal process.
Your browser picks one protocol per connection (usually preferring IPv6 when available, per the Happy Eyeballs algorithm). The address shown is the one this request actually used. A dual-stack network has both, but a single HTTP request can only reveal one of them.
We look up which autonomous system (ASN) announces your IP in a local snapshot of the global BGP routing table and match it against a curated list of cloud/hosting providers, an open list of commercial VPN ranges, and the Tor Project's exit node list. Everything runs on our server against local data — your IP is not forwarded to third-party detection APIs.
Free tools for network engineers — no signup, no rate-limit walls.