Short answer: What is a public IP address? It is the internet-facing IP address used by your connection when it communicates with online services. Depending on the network, it may belong to your home router, mobile carrier, workplace gateway, VPN exit server, cloud server, or hosting provider.
A public IP address helps internet traffic find its way back to your connection. It can also reveal useful but limited network signals, such as provider, ASN, rough location, and whether the route appears residential, mobile, data-center, or VPN-related. It should not be treated as a public lookup for your exact home address or personal identity.
Quick answer
- A public IP is internet-facing. It is the address online services usually see when your browser or app connects.
- It differs from a private IP. Private addresses work inside local networks; public addresses route across the internet.
- It may be static, dynamic, shared, or VPN-provided. The network type affects troubleshooting, reputation, and privacy expectations.
- It can reveal network signals, not exact identity. IP lookup can estimate provider and location, but it is not proof of a person or street address.
- One check is a snapshot. Your public IP can change after switching Wi-Fi, mobile data, VPN servers, routers, or ISP sessions.
7 things to know about public IP addresses
- A public IP is the address online services usually see. It is the internet-facing address for the route your browser, app, router, VPN exit server, mobile carrier, or hosting provider uses.
- Your provider normally assigns it. Home ISPs, mobile carriers, VPN providers, workplace networks, cloud platforms, and hosting companies control the public address pool used for your connection.
- It is different from a private or local IP. A private IP works inside a home, office, phone hotspot, or server network, while a public IP is used on the wider internet.
- It can reveal network-level clues. A public IP may suggest country, region, city, provider, ASN, connection type, or whether the route looks residential, mobile, hosting, proxy, or VPN-related.
- It cannot prove a person, exact home address, or full context by itself. IP geolocation is approximate, shared networks are common, and account, device, browser, and legal records may be needed for stronger attribution.
- VPNs, proxies, Tor, mobile networks, and CGNAT can change what appears public. The visible IP may belong to a VPN exit, proxy gateway, Tor exit relay, mobile carrier gateway, or shared ISP address rather than a single device.
- You can check it safely as an observable signal. Use MyIPScan tools to compare the visible public IP, provider, ASN, approximate location, DNS, WebRTC, IPv6, and VPN-related signals as a snapshot, not as a privacy verdict by itself.
What is a public IP address?
A public IP address is an Internet Protocol address that can be routed on the public internet. RFC 791 describes IPv4, while RFC 8200 describes IPv6. In normal browsing, the public IP is the address a website, API, or online service can usually log for the connection.
For a home user, the public IP commonly belongs to the router or ISP connection. For a phone, it may belong to the mobile carrier or a shared carrier gateway. For a VPN user, it may be the VPN server's exit IP. For a website owner, it may be the server or load balancer address.
The phrase what is a public IP address can sound simple, but the details matter. A single device can have a local private IP, a public route through a router, an IPv6 address, and a different VPN exit IP depending on the session.
How public IP addresses work
When your browser connects to a website, the website needs a return address for packets. On a home network, your laptop may use a private local address, while the router uses a public IP address for internet-facing traffic. The router tracks connections so replies return to the right device.
Many IPv4 home networks use Network Address Translation. RFC 3022 describes traditional NAT behavior. NAT lets multiple local devices share one public IPv4 address, but NAT should not be confused with security by itself. Firewall rules, router updates, and safe remote-access design still matter.
Some providers also use carrier-grade NAT or shared address space. RFC 6598 defines shared address space often used for that purpose. CGNAT can make inbound gaming, cameras, self-hosting, and remote access harder because the public address may be shared upstream.
Public vs private IP addresses
| Question | Public IP address | Private IP address |
|---|---|---|
| Scope | Routable on the internet | Used inside a local network |
| Common examples | 203.0.113.8, 2001:db8::1 | 192.168.1.20, 10.0.0.5 |
| Assigned by | ISP, mobile carrier, hosting provider, workplace, VPN, or cloud platform | Router, local network administrator, DHCP server, or device settings |
| Visible to websites | Usually yes, unless another route such as a VPN or proxy is used | Usually no as the page IP, though browser features can show local candidates in some setups |
| Main use | Internet routing, hosting, account checks, geolocation, reputation, and access rules | Home and office device communication, printers, routers, cameras, consoles, and local troubleshooting |
Private IPv4 ranges are defined in RFC 1918. For a deeper side-by-side guide, read Private vs Public IP Addresses.
Static, dynamic, shared, and VPN public IPs
Not every public IP behaves the same way. A static public IP is intended to stay stable. A dynamic public IP can change after a router reconnect, lease renewal, mobile network change, or ISP event. A shared public IP may represent many users behind a carrier, school, office, apartment network, or VPN exit.
| Type | Common use | Trade-off |
|---|---|---|
| Static public IP | Business access, allowlists, monitoring, VPN gateways, servers | Predictable, but easier to correlate over time |
| Dynamic public IP | Most home broadband and mobile connections | Simple, but less convenient for hosting or allowlists |
| Shared or CGNAT IP | Mobile carriers, some ISPs, apartments, VPN exits | Can inherit reputation or make inbound connections difficult |
| VPN exit IP | VPN-routed browser or app traffic | Websites see the VPN server IP, but accounts and browser signals still matter |
If you are troubleshooting whether your address changes, see Static vs Dynamic IP Addresses. If you are trying to understand assignment, see How IP Addresses Are Assigned.
What a public IP address can reveal
A public IP can often indicate the network owner, ASN, ISP or hosting provider, approximate country or region, and sometimes a nearby city. It can also suggest whether traffic appears to come from a residential ISP, mobile carrier, workplace, data center, VPN, proxy, or cloud platform.
Those signals are used for ordinary network operations: fraud checks, rate limits, abuse handling, geolocation, account security, content delivery, spam controls, and troubleshooting. The IANA IPv4 address space registry is one example of public address-space coordination, though ordinary location databases use additional commercial and network data.
IP geolocation is still an estimate. Country-level results are usually stronger than city-level results. VPNs, proxies, mobile networks, corporate gateways, satellite providers, stale databases, and ISP routing can all skew location results.
What a public IP address cannot prove by itself
- It cannot reveal your passwords.
- It cannot open your files.
- It cannot prove an exact street address from public lookup alone.
- It cannot prove which person used a shared home, school, office, mobile, VPN, or CGNAT address.
- It cannot remove the need to check account records, cookies, browser fingerprints, device identifiers, payment data, timestamps, or provider records.
A public IP address is one signal. Stronger attribution usually requires combining it with logs, account activity, device information, browser signals, billing records, or lawful provider records.
How to check your public IP safely
- Open What Is My IP to see the public IP visible from this browser session.
- Use IP Geolocation Lookup and ASN Lookup to review provider, ASN, and rough location signals.
- Compare Wi-Fi and mobile data if you want to know whether your public route changes by network.
- If you use a VPN, run VPN Leak Test, DNS Leak Test, WebRTC Leak Test, and IPv6 Leak Test.
- Only test networks, routers, and devices you own or are authorized to manage.
A browser-based IP check is a snapshot. Results can change after reconnecting a VPN, switching servers, changing DNS settings, restarting a router, or moving between Wi-Fi and cellular networks.
VPNs, proxies, Tor, and public IP exposure
A VPN usually changes the public IP address websites see from your ISP-assigned address to the VPN server's exit address. That can reduce some network exposure on public Wi-Fi or hide your ISP-facing address from websites, but it shifts trust to the VPN provider and does not make you anonymous.
Proxies can change the visible IP for a specific browser or app, depending on configuration. Tor Browser routes browser traffic through Tor relays and can show a Tor exit IP, but it is browser-scoped and may be slower or blocked by some services. Each tool changes one or more network signals; none removes account, cookie, device, payment, or behavior tracking by itself.
For a broader comparison, read Proxy vs VPN vs Tor and How to Hide Your IP Address.
When your public IP address matters most
- Login security: unusual IP country, ASN, VPN, proxy, or device patterns may trigger account checks.
- Remote access: public IP, CGNAT, firewall rules, and IPv6 support affect whether inbound connections can work.
- Gaming and cameras: NAT type, port forwarding, CGNAT, and router firewall rules can affect reachability.
- Email and servers: public IP reputation, reverse DNS, blacklists, and ASN reputation can affect deliverability.
- Privacy review: public IP is one network signal that combines with DNS, WebRTC, IPv6, accounts, cookies, and browser fingerprints.
How to troubleshoot confusing public IP results
Public IP results can look inconsistent when several network layers are active. Before assuming something is broken, compare the context: which device, which browser, which network, which VPN server, and whether IPv4 or IPv6 is being checked.
- The city is wrong: check whether the country and ISP are correct first. City-level IP geolocation is often approximate and may reflect provider routing rather than your precise location.
- The provider is unexpected: look for a VPN, corporate gateway, mobile carrier, satellite provider, security gateway, or shared building network.
- The IP changes often: dynamic ISP leases, mobile routing, router reconnects, and VPN server changes can all rotate the visible address.
- The address does not accept inbound connections: check for CGNAT, router firewall rules, IPv6-only service, blocked ports, or a provider plan that does not include a public inbound route.
- Different tools disagree: compare timestamps, IPv4 versus IPv6, browser cache, VPN state, and whether each tool is checking the same route.
For most users, the goal is not to force every result to match perfectly. The goal is to understand which public IP address a particular browser, app, or network path is using right now.
Common mistakes to avoid
- Do not assume public IP means exact location. Treat IP geolocation as an estimate, not proof of where someone is sitting.
- Do not treat dynamic IP as privacy. A changing address does not remove account, cookie, or browser tracking.
- Do not expose router admin, RDP, SSH, cameras, or NAS panels directly to the internet. Use safer remote-access design, strong authentication, updates, and firewall rules.
- Do not assume a VPN fixes every exposure signal. Check DNS, WebRTC, IPv6, browser state, and account behavior too.
- Do not scan or probe IPs you do not own or manage. Keep checks limited to your own network and authorized systems.
What to do next
If you only need to know the address websites can see, check your public IP and note the provider, ASN, and approximate location. If the result looks wrong, compare Wi-Fi, cellular, VPN on/off, DNS, WebRTC, and IPv6 results. If you need remote access or hosting, verify whether you have public IPv4, CGNAT, IPv6, dynamic assignment, static assignment, and appropriate firewall controls.
The practical answer to what is a public IP address is this: it is the internet-facing address for a connection path. Use it for routing and troubleshooting, but do not overread it as a full identity, exact location, or privacy verdict by itself.
Frequently asked questions
What is a public IP address?
A public IP address is the internet-facing address used by your router, device, VPN exit, mobile carrier, or server when it communicates with internet services.
Is a public IP address the same as a private IP address?
No. A public IP is reachable on the internet, while private IP addresses are local-scope addresses used inside homes, offices, and device networks.
Can a public IP address show my exact location?
Usually no. Public IP lookup can estimate a country, region, provider, ASN, or sometimes a nearby city, but it should not be treated as a public street-address lookup.
Can my public IP address change?
Yes. Many home and mobile connections use dynamic public IPs or shared carrier addresses. Static public IPs are more stable and are often used for business, hosting, or allowlists.
Does a VPN hide my public IP address?
A VPN usually changes the public IP address websites see to the VPN server's exit IP. It does not make you anonymous or remove account, cookie, browser, or device tracking.
Sources and methodology
MyIPScan tools and examples show observable browser and network signals. IP and geolocation results can be approximate, and VPN, DNS, WebRTC, IPv6, ASN, reputation, and browser checks are snapshots. A single result does not prove anonymity or every security condition. See the MyIPScan methodology and editorial policy.
This FAQ was updated using MyIPScan editorial guardrails: clear public/private IP explanations, no exact-location overclaims, no VPN anonymity guarantees, no unsafe remote-access advice, and careful distinction between public IPs, private IPs, NAT, CGNAT, IPv4, IPv6, geolocation, and browser signals.