IP Lookup

Your public IP is the address the internet sees for your connection — every site you visit sees it, and services use it for security checks, rate limits, and regional content. It matters practically when configuring firewalls or allowlists, debugging "works at home, fails at office" problems, or verifying a VPN is actually active.

IP geolocation maps addresses to the network's registration and routing data, not to your device's GPS. ISPs route traffic through regional hubs, so the reported city is often the provider's infrastructure location rather than yours. Accuracy is typically country-perfect, region-good, city-approximate — that's inherent to how IP allocation works, not a flaw in the lookup.

Not from the IP alone. A lookup reveals your provider and approximate area — the street-level identity behind an address is only accessible to the ISP itself, usually under legal process. The realistic risks of an exposed IP are targeted denial-of-service or scanning, which is why servers get hardened and gamers use VPNs.

IPv4 addresses (like 203.0.113.10) are 32-bit and effectively exhausted — most connections share them via NAT. IPv6 addresses (like 2001:db8::1) are 128-bit, plentiful, and increasingly the default on mobile networks. Many connections have both; which one a site sees depends on which protocol the connection preferred.

Restarting a home router often gets a new dynamic IP from your ISP; a VPN or proxy replaces your visible IP with theirs, hiding yours from the sites you visit. For servers the IP is static by design — you change it by adding or moving to a new address at your provider, then updating DNS.