IP Address Lookup — Find Your Public IP & Location

IPv4 addresses use a 32-bit format represented as four decimal numbers separated by dots (e.g., 192.168.1.1), providing approximately 4.3 billion unique addresses. With the explosion of internet-connected devices, this pool was exhausted, driving the development of IPv6. IPv6 uses a 128-bit format represented as eight groups of four hexadecimal digits separated by colons, providing 340 undecillion addresses — effectively unlimited. Most modern devices and ISPs support both protocols simultaneously (dual-stack). When you use this IP Address Lookup tool, it reports both your IPv4 and IPv6 addresses if your network supports IPv6. If you only see an IPv4 address, your ISP or router has not yet enabled IPv6 connectivity.

Every device on the internet has a public IP address that is globally routable and unique — this is what websites see when you connect to them. Within your home or office network, devices are assigned private IP addresses (ranges: 10.0.0.0 to 10.255.255.255, 172.16.0.0 to 172.31.255.255, and 192.168.0.0 to 192.168.255.255) that are not routable on the public internet. A router with NAT (Network Address Translation) maps all these private addresses to a single public IP. This tool reports your public IP — the address that external services see. If you are behind a corporate firewall or load balancer, the IP shown may be the firewall external address. VPN services replace your real public IP with the VPN server IP in all external communications.

A PTR record (Pointer Record) maps an IP address to a domain name — the reverse of a standard A record lookup. This is also called rDNS (reverse DNS) or hostname lookup. PTR records are maintained by the IP address block owner (usually the ISP or hosting provider). Reverse DNS is important for email server reputation: spam filters often check whether a sending mail server IP has a valid PTR record matching its forward DNS, and reject email from IP addresses without this. This tool shows the PTR record (hostname) for your IP address where available. If no PTR record exists, a blank result is shown — common for residential ISP connections.

Many services — including cloud platforms like AWS, database servers, and corporate VPNs — use IP allowlists to restrict access to authorised IPs only. When setting up server access, you need to know your current public IP to add it to the allowlist. Because residential and office IP addresses can change (dynamic IPs assigned by ISPs via DHCP), you may need to update the allowlist after your IP changes. Some ISPs offer static IP plans that keep your address consistent — useful if you frequently need allowlist access. Use this tool to quickly check your current public IP before submitting a support request. For development environments, it also helps verify that your requests are coming from the expected IP range.

VPNs (Virtual Private Networks) are widely used to mask the real public IP address for privacy, to bypass geo-restrictions, and to securely access corporate resources. After connecting to a VPN, verify that the IP has changed to the VPN server IP and not leaked your real address (a WebRTC leak can expose your real IP even when VPN is active). This tool instant IP display makes it easy to confirm VPN effectiveness — connect to the VPN, reload this page, and check that the IP shown is the VPN server IP rather than your ISP IP. For network troubleshooting, knowing your public IP helps diagnose connectivity issues, verify DNS propagation, and confirm that remote access configurations are correct.