How to Find Your Public IP Address (And Why It Matters)

Last updated: June 10, 2026

Every device that connects to the internet needs an IP address. IP addresses are how data travels across the internet. Web servers halfway around the world can return data to your laptop, phone, or smart TV. Without it, the internet simply does not work.

But most people never think about their IP address until something breaks. A VPN that is not masking their traffic. A firewall rule that needs their current address. A streaming service that thinks they are in the wrong country. A security incident where they need to verify what is connecting to their network.

This guide walks through exactly how to find your public IP address using several methods. It explains the difference between public and private IP addresses. It covers IPv4 and IPv6, since most connections now carry both. It covers the privacy and security implications you should understand. And it explains why “your IP” in 2026 is more nuanced than it used to be. CGNAT and services like Apple’s iCloud Private Relay both reshape the picture.

What Is a Public IP Address?

A public IP address is the address that identifies your network on the open internet. Your ISP assigns it to your router. A private IP address is assigned to devices on your local network (like 192.168.1.x). Private addresses only have meaning within that network. NAT bridges the two.

When people say “find my IP address,” they almost always mean their public IP address. This is the address that identifies their network on the open internet. It is different from the private IP address assigned to individual devices on your local network.

Public vs Private IP Addresses

Your home or office network runs behind a router. That router has two sides. A public-facing side connects to your ISP. A private-facing side connects to your devices: laptops, phones, printers, smart speakers. The public side gets a public IP address from your internet provider. The private side assigns private IP addresses to your devices using ranges reserved for local networks. For a deeper comparison of how these two address types work together, see our public vs. private IP addresses guide.

Private IP ranges are defined in RFC 1918 and include:

• 10.0.0.0 – 10.255.255.255 (a single /8 block — common in large enterprise networks)
• 172.16.0.0 – 172.31.255.255 (a /12 block — often used by mid-size organizations)
• 192.168.0.0 – 192.168.255.255 (a /16 block — the default for home and small business networks)

If your device’s IP starts with 192.168 or 10., that is a private address. It only has meaning inside your local network. The rest of the internet cannot reach it directly.

How NAT Bridges the Gap

The technology that connects these two worlds is called NAT (Network Address Translation). When your laptop requests a webpage, NAT translates the request. The translation maps your private address to the router’s public IP before sending it onto the internet. When the response comes back, NAT routes it to the correct device on your local network. This is why dozens of devices in your home can share a single public IP address. It is also why understanding the distinction matters when you troubleshoot connectivity or configure network ports for remote access. IP addresses identify devices at the network layer. Each device also has a unique MAC address that identifies it at the hardware level on the local network. For the broader picture of how IPs fit into the resolution chain, see our guide on how DNS works.

How to Find Your Public IP Address

Six methods cover every situation. A web-based lookup tool gives the most context. Search engines display your IP directly in results. Windows and macOS each have command-line approaches. Your router’s admin page is reliable when external services fail. Mobile devices require a browser check, since their built-in settings show only the private address.

Several reliable ways exist to check your IP address, depending on your situation and comfort level with technical tools.

Method 1: Use a Web-Based IP Lookup Tool

The simplest approach is to open a browser. Use a tool that reads your public IP from the incoming connection. You can check your IP instantly with our tool. It also displays your approximate location, ISP, and whether you are on IPv4 or IPv6.

This works because of how web servers see traffic. When your browser makes a request, the server sees the public IP your router is using. The tool reads that address and displays it back to you. No software to install, no commands to run.

Method 2: Type “What Is My IP” Into a Search Engine

Bing, Google, and DuckDuckGo all display your public IP directly at the top of the results page. Type what is my IP into the search box and the address appears instantly. No clicking required.

The catch is context. The search box shows the raw address and nothing else. It does not tell you your ISP, your approximate location, or whether the address is IPv4 or IPv6. It also cannot help you spot CGNAT, which requires comparing two values (covered below). For a quick glance, the search box works. For troubleshooting, a dedicated lookup tool gives you the detail you actually need.

Method 3: Command Line on Windows

To find your IP address on Windows without visiting a website, open Command Prompt or PowerShell and run:

nslookup myip.opendns.com resolver1.opendns.com

This queries OpenDNS’s special hostname that returns your public IP. The result appears under the “Non-authoritative answer” section. Alternatively, in PowerShell:

(Invoke-WebRequest -Uri "https://api.ipify.org").Content

To see your private IP address (useful for local network troubleshooting), use:

ipconfig

Look for the “IPv4 Address” line under your active network adapter. Remember, this shows your local address, not your public one. The subnet mask displayed alongside the IP defines how the address is split. One portion identifies your network. The other identifies your specific device. Our subnet calculator works through the math.

Method 4: Command Line on macOS and Linux

On macOS or Linux, open Terminal and run:

curl ifconfig.me

Or for a bit more detail:

curl ipinfo.io

This returns your public IP along with city, region, ISP, and organization data in JSON format. For just the IP with no extras:

dig +short myip.opendns.com @resolver1.opendns.com

For your private IP on macOS:

ipconfig getifaddr en0

On Linux:

hostname -I

Method 5: Router Admin Page

Your router knows its own public IP. Log into the admin interface in your browser (typically at 192.168.1.1 or 192.168.0.1). Look for a “WAN” or “Internet” status page. The IP address listed there is your public address. This method is especially useful when you need to verify your IP without relying on any external service. It is also the most reliable way to detect CGNAT, which we cover in the section below.

Method 6: Mobile Devices

On iOS, go to Settings > Wi-Fi, tap the info icon next to your connected network. But this shows your private IP. For your public IP on mobile, the easiest route is a web-based tool. Open Safari or Chrome and visit an IP address lookup page.

On Android, the path is similar. Settings > Network & Internet > Wi-Fi > tap your network. Again, this shows the private address. Use a browser-based check for the public one.

You Probably Have Two Public IPs: IPv4 and IPv6

Most US connections now run dual-stack, carrying both an IPv4 and an IPv6 address simultaneously. Roughly half of global traffic to Google now arrives over IPv6, and the US sits above that average. When both are available, your browser prefers IPv6, so lookup tools often show the long hexadecimal address.

For years, “your public IP” meant one IPv4 address, like 203.0.113.42. That assumption no longer holds. IPv4 addresses ran out, and the internet has been migrating to IPv6 for over a decade. The migration crossed a major threshold recently. Google’s measurements show roughly half of its worldwide users now connect over IPv6, with the United States above 50%. Industry analysts projected IPv6 would overtake IPv4 as the majority of global traffic in early 2026.

In practice, most US home connections now run dual-stack. Your router holds an IPv4 address and an IPv6 address at the same time. Both are public. Both are real. Which one a website sees depends on which protocol your device chooses for that connection.

Why Your Lookup Tool Shows a Long Hexadecimal Address

When both protocols are available, modern devices prefer IPv6. The connection logic (nicknamed “Happy Eyeballs”) tries both and uses whichever responds well, with IPv6 favored. So an IP lookup tool may show you something like 2601:1c0:8a00:5b3::1a2f instead of a familiar dotted IPv4 address. Nothing is wrong. That is your public IPv6 address. Our IPv4 vs. IPv6 comparison covers how the two formats differ, and our IPv4-to-IPv6 converter shows how IPv4 addresses map into IPv6 notation.

To check each address separately from the command line, force the protocol:

curl -4 ifconfig.me   # your public IPv4 address
curl -6 ifconfig.me   # your public IPv6 address

If the -6 command fails, your connection does not have working IPv6. That is still common on older routers and some ISPs.

Two Things That Surprise People About IPv6

Your IPv6 address rotates by design. IPv6 privacy extensions (defined in RFC 8981) generate temporary addresses that change periodically, often daily. This prevents websites from tracking a device by its address over long periods. So if your IPv6 address looks different from yesterday, that is the privacy mechanism working, not a problem.

There is no NAT in standard IPv6. The address space is so large that every device can hold its own globally routable address. No translation layer needed. Your firewall, not NAT, is what blocks unsolicited inbound traffic on IPv6. For most users this changes nothing day to day. For anyone hosting services behind CGNAT, however, IPv6 can be the escape hatch — more on that next.

When “Your IP” Isn’t Really Yours: CGNAT and iCloud Private Relay

Two technologies changed what “your public IP” means. CGNAT (Carrier-Grade NAT) lets ISPs share one IPv4 address across hundreds of customers — Starlink, T-Mobile Home Internet, and most mobile carriers use it by default. Apple’s iCloud Private Relay masks Safari traffic for iCloud+ subscribers through two relay servers.

The classic explanation of public IPs assumes one router maps to one unique public IP. In 2026, that is not always true. Two developments fundamentally changed what shows up when you look up your public IP.

CGNAT: Many Users Share One Public IP

CGNAT stands for Carrier-Grade Network Address Translation. It is a layer of NAT that runs at the ISP level. Your home router does NAT between your private devices and one public IP. CGNAT adds another layer. It does NAT between many customers and one shared public IPv4 address. This means hundreds (sometimes thousands) of subscribers can sit behind the same address.

CGNAT exists because IPv4 addresses ran out years ago. ISPs deploy it to stretch their existing IPv4 pool. The technology is widespread:

• Mobile carriers use CGNAT almost universally. Your phone’s “public IP” is almost certainly shared with thousands of other customers on the same carrier.
• Satellite and 5G home internet providers put residential customers behind CGNAT by default. Starlink, T-Mobile Home Internet, and AT&T Internet Air all do this, and none of them offers a static public IP on standard residential plans.
• Fixed-line ISPs are the largest CGNAT segment overall. The CGNAT market reached $1.29 billion in ISP revenue in 2025. CGNAT is no longer exotic; it is the default for many providers.

How to detect CGNAT: Compare two values. The WAN IP shown in your router’s admin page. And the result from a web-based IP lookup tool. If they match, you have a real public IP. If they differ, you are behind CGNAT. The router will often show something in the 100.64.0.0/10 range, which is reserved specifically for CGNAT use.

What it means for you: Port forwarding, hosting servers, and many remote access scenarios become difficult or impossible behind CGNAT. The “public IP” you see is shared, so inbound connections cannot reach you directly. If you need true inbound connectivity, four options exist. Ask your ISP for a public IPv4 address (Starlink and others offer this on business plans). Switch to IPv6 if your services support it, since CGNAT only applies to IPv4. Use a mesh VPN like Tailscale, which punches through CGNAT for remote access. Or use a tunneling service such as Cloudflare Tunnel to publish services outbound.

Apple iCloud Private Relay: IP Masking for Safari Users

Apple’s iCloud Private Relay is a privacy service bundled with iCloud+ subscriptions. It is available on iPhone, iPad, Mac, and Apple Vision Pro. When enabled, Private Relay routes Safari traffic through two separate relays before it reaches the destination website:

1. Ingress relay (Apple): Sees your real IP address but encrypts the DNS query and destination URL. It cannot see which website you visit.
2. Egress relay (third-party partner): Decrypts only the destination information and forwards the request. It assigns a different IP based on your general region, but it never sees your real IP.

No single entity can match your real IP to your browsing destination. Websites see only the egress relay’s IP, which corresponds to your approximate region rather than your specific location.

Private Relay has some important limits. It only protects Safari traffic, not Chrome, Firefox, or apps. It is not available in all countries. And it gives an approximate regional IP, not a country-of-choice selection like a traditional VPN. But millions of iCloud+ subscribers have it turned on by default. For them, the IP that websites and lookup tools see is no longer the real address.

Why Your IP Address Matters

Five practical situations make finding your IP useful. VPN verification confirms a VPN is actually working. Remote access requires it for firewall allow-lists. Network troubleshooting uses it to communicate with ISP support. Geo-restriction debugging reveals what country streaming services think you are in. Security auditing distinguishes your traffic from unauthorized access.

Knowing how to find your IP address is not just trivia. Practical situations exist where you actually need it.

VPN verification. After connecting to a VPN, you should verify that your visible IP has actually changed. VPN connections can silently fail, leak through DNS requests, or drop without warning. Checking your public IP confirms the VPN is working. A DNS lookup can reveal whether your DNS queries are also being routed through the VPN. Or whether they are leaking to your ISP’s resolvers.

Remote access and firewall rules. Setting up remote access to a home server, NAS, or security camera system requires your public IP. The address is required to configure port forwarding and firewall allow-lists. Many firewalls require you to whitelist specific IPs for SSH, RDP, or web admin access.

Troubleshooting network issues. When your internet acts strange (slow speeds, intermittent drops, unexpected blocks), knowing your public IP helps. You can give your ISP’s support team a precise reference. It also lets you cross-reference against any IP-based blocks or blacklists. Our guide on how to troubleshoot network connectivity covers a systematic approach. You can also perform a reverse DNS lookup on your IP to see what hostname your ISP has assigned. This helps diagnose email deliverability problems. See our companion guide on what reverse DNS is for the full context.

Geo-restriction debugging. Streaming services and some websites use your IP address to determine your country and region. If you see the wrong content library or get blocked from a service, check your IP. The lookup tells you what location those services think you are in.

Security auditing. If you spot unfamiliar activity in your server or application logs, compare the source IP against your known public IP. This distinguishes your own traffic from potential unauthorized access. For unknown IPs you find in logs, a WHOIS or RDAP lookup reveals the network operator. And a DNS blacklist check shows whether your own IP has been flagged for delivery problems.

Can Someone Find Your Location from Your IP Address?

Public IP geolocation can reveal your approximate city and ISP. It cannot reveal your exact street address, name, or apartment number. Only your ISP holds the records linking an IP to a physical address. In most jurisdictions, releasing that data requires a court order or law enforcement subpoena.

This is one of the most common concerns people have. The answer is more nuanced than a simple yes or no.

What your IP address reveals: Publicly available geolocation databases can match your IP to your city or metropolitan area. They also identify your ISP’s name and sometimes the postal code region. Accuracy varies. In dense urban areas it might narrow to a neighborhood-sized region. In rural areas it might only identify the nearest city where your ISP has infrastructure.

What your IP address does NOT reveal: Your street address, apartment number, name, or any other personally identifying information. IP geolocation databases map IP ranges to approximate areas based on where ISPs allocate address blocks. They do not contain subscriber records.

The ISP factor: Your ISP does keep records connecting your IP address to your account and your billing address. However, ISPs are legally required to protect this information. In most jurisdictions, releasing subscriber data requires a court order or valid law enforcement subpoena. A random person on the internet cannot call up your ISP and ask who owns a particular IP.

So the realistic threat level is low for most people. Your IP reveals roughly where you are, but not precisely who or where you are. Combining an IP address with other data points can build a more complete picture. Examples include social media posts, account registrations, and forum activity. This is one reason privacy-conscious users choose to mask their IP with a VPN, Private Relay, or similar service.

Why Does My IP Address Change?

Most residential connections use dynamic IPs. Your ISP assigns an IP from a pool with a time-limited DHCP lease. Router restarts, ISP maintenance, extended disconnections, and ISP policy can all trigger an address change. Static IPs cost extra and exist for users who need a predictable address.

If you checked your IP on different occasions and noticed different results, you are seeing dynamic IP assignment in action.

Dynamic vs static IPs. Most residential internet plans use dynamic IPs. Your ISP has a pool of available addresses and assigns one to your router when it connects. This assignment has a DHCP lease: a time limit, often 24 hours to several days. When the lease expires, your router requests a renewal. Sometimes it gets the same address back; sometimes a different one. Whether you receive an IPv4 or IPv6 address (or both) depends on your ISP and equipment. Our IPv4 vs. IPv6 comparison explains the differences.

Static IPs are permanently assigned to your connection and do not change. Businesses typically pay extra for static IPs. They need a predictable address for hosting servers, running email infrastructure, or maintaining VPN endpoints.

Common triggers for IP changes:

• Router restart: Powering off your router releases the DHCP lease. When it reconnects, the ISP may assign a new address from the pool.
• ISP maintenance: Backend infrastructure changes or network reconfigurations can reassign IP blocks.
• Extended disconnection: If your router is offline long enough for the lease to expire, expect a new IP on reconnection.
• ISP policy: Some ISPs rotate addresses more aggressively than others. Cable providers tend to change IPs less frequently than DSL or cellular providers.
• IPv6 privacy extensions: Your IPv6 address rotates automatically by design, often daily, to limit tracking. This is separate from DHCP lease behavior and is normal.

If you need your IP to stay the same, contact your ISP about a static IP plan. Alternatively, use a dynamic DNS (DDNS) service. The service maps a hostname to your current IP and updates it automatically when the address changes.

How to Hide or Change Your IP Address

Four approaches mask or change your public IP. A VPN routes traffic through a server in another location. A proxy forwards traffic without encryption. Tor uses multiple volunteer relays for strong anonymity. Switching from Wi-Fi to mobile data gives you a different ISP-assigned IP without any extra software.

Legitimate reasons exist to mask your public IP: privacy, bypassing geographic restrictions, or securing your connection on public Wi-Fi. Here are the main approaches.

VPN (Virtual Private Network). A VPN routes your traffic through a server in another location. Websites see the VPN server’s IP instead of yours. This is the most common and practical solution for everyday use. Choose a reputable, paid VPN provider. Free VPNs often monetize your data, which defeats the purpose. After connecting, verify the change by running an IP address check.

Cloudflare WARP / 1.1.1.1. Cloudflare’s free WARP service offers a lighter-weight alternative. It encrypts traffic between your device and Cloudflare’s network and provides a degree of IP masking. It is not a full anonymity tool like a paid VPN. But for everyday privacy on public Wi-Fi, it is a reasonable free option. Available on iOS, Android, Windows, macOS, and Linux.

Apple iCloud Private Relay. Already covered above. If you are an iCloud+ subscriber on an Apple device, this is the simplest IP-masking option for Safari browsing. It is enabled in Settings > [your name] > iCloud > Private Relay.

Proxy servers. A proxy acts as an intermediary, forwarding your requests through a different IP. Unlike a VPN, most proxies do not encrypt your traffic. They are less suitable for security-sensitive tasks. They are useful for quick IP changes when encryption is not a concern. Examples include web scraping or testing how a website appears from a different region.

Tor (The Onion Router). Tor bounces your traffic through multiple volunteer-operated relays worldwide. It is very difficult to trace back to your original IP. It is the strongest option for anonymity. But it comes with significant speed penalties, and some websites block Tor exit nodes. The Electronic Frontier Foundation provides detailed guidance on when and how to use Tor effectively.

Mobile data. Switching from Wi-Fi to cellular data gives you a different public IP assigned by your mobile carrier. This is not a privacy solution. But it is a quick way to get a new IP if you are troubleshooting an IP-based block. Note that mobile carrier IPs are almost always CGNAT-shared, as discussed above.

Related Tools & Resources

NetworkCheckr offers complementary tools for IP address workflows. The My IP Address tool returns your public IP with geolocation and ISP detail. Companion guides cover public vs. private IPs, IPv4 vs IPv6, reverse DNS, WHOIS lookup, and DNS blacklist checks.

• My IP Address — check your public IP, approximate location, and ISP.
• Reverse DNS Lookup — check the PTR record assigned to any IP.
• WHOIS Lookup — identify the network operator behind any IP block.
• DNS Lookup — query A, AAAA, MX, and other DNS records.
• IP Blacklist Check — confirm your IP is not on a major DNSBL.
• IPv4-to-IPv6 Converter — see how IPv4 addresses map into IPv6 notation.
• Public vs Private IP Addresses — the companion explainer for IP scope.
• IPv4 vs IPv6 — learn the differences and why IPv6 matters for IPv4 exhaustion.
• How DNS Works — foundational guide to how IP lookups happen behind the scenes.
• All NetworkCheckr Tools — the full set of free networking utilities.

Frequently Asked Questions

Eight questions cover the practical edge cases. Public vs private IP. Finding your IP on Windows. Whether IP reveals home address. Why IPs change on router restart. What CGNAT is and how to detect it. Whether sharing an IP is safe. Why lookup tools show IPv6. And how to find an IP without using a website.