Short answer: What is an IP address? It is a network address used to route traffic between devices, routers, servers, apps, and networks. Websites use an IP address so responses know where to go, but an IP address is not the same as a personal identity or exact home address.
For most users, the important distinction is between the public IP address that internet services can see and the private local IP addresses used inside a home, office, or device network. VPNs, mobile carriers, CGNAT, IPv6, and router settings can all affect which address appears in a test.
Quick answer
- An IP address is a routing label. It tells networks where traffic should be sent.
- Public and private IPs are different. Websites usually see your public IP, not the local address of your phone, laptop, or printer.
- IPv4 and IPv6 are address versions. IPv4 is shorter and older; IPv6 has a much larger address space.
- IP lookup is not exact identity. It can suggest provider, ASN, country, or region, but not reliably name a person or exact street address.
- One check is a snapshot. Results can change after switching Wi-Fi, mobile data, VPN servers, routers, or browser settings.
IP address, explained
An IP address is an Internet Protocol address. It is part of the addressing system that lets devices and networks exchange packets. RFC 791 describes IPv4, and RFC 8200 describes IPv6.
Think of an IP address as a network routing identifier, not a name tag. A server needs an address to send data back to your connection. Your device, router, ISP, mobile carrier, workplace, VPN provider, or hosting company may all be involved in which address appears.
The phrase what is an IP address often gets simplified to "your internet address," but that can be misleading. A device can have several addresses at once: a local private IPv4 address, a public IPv4 address, one or more IPv6 addresses, and a VPN exit IP when a VPN is connected.
How IP addresses work in everyday browsing
When you open a website, your browser first resolves the domain name, then connects to an IP address. The server sends responses back through network routes. At home, the public IP usually belongs to your router or ISP connection, while phones, laptops, TVs, consoles, and printers use local addresses behind the router.
Routers often use Network Address Translation, or NAT, so multiple private devices can share one public IPv4 address. RFC 3022 describes traditional NAT behavior. This is why a website usually sees the router or VPN exit IP, not each device's private local address.
Mobile networks, apartment networks, and some ISPs may also use carrier-grade NAT. RFC 6598 defines shared address space often used in that context. CGNAT can affect gaming, self-hosting, cameras, and remote access because inbound connections may not reach your router directly.
Public, private, static, and dynamic IP addresses
| Type | What it means | Where you see it | What to remember |
|---|---|---|---|
| Public IP | Internet-facing address visible to websites and services | Router WAN, mobile carrier, VPN exit, server | Can indicate provider, ASN, and approximate location |
| Private IP | Local address used inside a home, office, or device network | 192.168.x.x, 10.x.x.x, 172.16-31.x.x | Defined for private IPv4 use in RFC 1918; not globally unique |
| Static IP | Address intended to stay stable over time | Business plans, servers, allowlists, remote access | Useful for predictability, but easier to correlate over time |
| Dynamic IP | Address that may change automatically | Most home, mobile, and consumer ISP connections | A changed IP does not erase accounts, cookies, or device signals |
| Shared or CGNAT IP | Public address or shared range used by many customers | Mobile carriers, some ISPs, VPN exits | Can complicate reputation, port forwarding, and troubleshooting |
Private and public addresses, NAT and CGNAT are compared in detail below. For the other distinctions, see Static vs Dynamic IP Addresses and How to Find Your Local IP Address.
In depthPrivate vs public IP addresses, NAT and CGNAT
Private vs public IP addresses at a glance
| Question | Private IP address | Public IP address |
|---|---|---|
| Where it works | Inside your home, office, school, hotspot, or other local network | Across the public internet |
| Who assigns it | Your router, DHCP server, device, or network administrator | Your ISP, mobile carrier, VPN provider, hosting provider, or organization |
| Common IPv4 examples | 192.168.1.23, 10.0.0.42, 172.16.5.20 | Any globally routed public IPv4 address not reserved for private or special use |
| Can websites see it? | Usually no, not as the normal page IP | Yes, unless traffic exits through a VPN, proxy, Tor, or another gateway |
| Can it be reused? | Yes. Millions of networks can reuse the same private ranges | No. Public addresses must be globally coordinated |
| Main troubleshooting use | Finding devices, router gateway, printers, cameras, DHCP problems, local sharing | Checking ISP route, VPN route, geolocation, ASN, DNS, account-access signals |
| Main safety issue | Local device exposure, weak router admin, insecure LAN services | Open ports, exposed services, reputation, geolocation, account-risk signals |
The easiest way to remember private vs public IP addresses is scope: private is local, public is internet-facing. The two may appear together in one connection because the router sits between your local network and the wider internet.
Some browser features, especially WebRTC, can expose local or network candidate signals in certain setups. That does not mean every website normally sees your private IP as the page IP, but it is a reason to check WebRTC behavior when comparing private vs public IP addresses, VPN behavior, and browser exposure.
What is a private IP address?
A private IP address is used inside a network that you or an organization controls. The classic IPv4 private-use ranges are defined by RFC 1918:
10.0.0.0/8— addresses from10.0.0.0to10.255.255.255172.16.0.0/12— addresses from172.16.0.0to172.31.255.255192.168.0.0/16— addresses from192.168.0.0to192.168.255.255
Your router may give your laptop 192.168.1.34, your phone 192.168.1.35, and your printer 192.168.1.50. Another home down the street can use the same numbers because those addresses are meaningful only inside each local network.
Private addresses are useful for local traffic: file sharing, printer discovery, router administration, smart-home devices, NAS access, cameras, and game consoles. They are not normally reachable from the public internet unless another mechanism is added, such as port forwarding, a VPN, a cloud relay, or remote-access software.
What is a public IP address?
A public IP address is globally routable. It is the address websites and internet services see for your connection unless you use a VPN, proxy, Tor, corporate gateway, or another exit network. Public IPs are coordinated so that the same address is not assigned to unrelated networks at the same time.
For a typical home connection, the public IPv4 address is assigned to the router's WAN side by the ISP. For mobile data, it may belong to the carrier network. For a VPN session, the public IP visible to websites is usually the VPN server's exit IP, not your home router's public IP.
A public IP can reveal broad network context such as ISP, ASN, approximate location, VPN or hosting signals, and reputation. It should not be treated as a personal identity by itself. Account logins, cookies, timestamps, provider records, browser signals, and user-granted location can add more context than the public IP alone.
How NAT connects private and public IPs
Network Address Translation, or NAT, lets many private devices share one public IPv4 address. In a home network, your laptop sends traffic from a private address to the router. The router rewrites the outbound traffic so it appears to come from the router's public address and a temporary port. When the reply comes back, the router maps it to the correct private device.
RFC 3022 describes traditional NAT behavior. In practical terms, NAT is why a website usually sees one public IP for the whole household even though several devices are online at the same time.
NAT helps with IPv4 address scarcity and local addressing, but do not mistake it for a security model by itself. A firewall, router updates, strong admin credentials, careful port-forwarding rules, and secure device configuration still matter.
7 key differences that matter in real life
- Visibility: websites see the public IP; local network tools see private IPs.
- Uniqueness: public IPs must be globally coordinated; private IPs are reused across many networks.
- Assignment: public IPs come from ISPs, carriers, VPNs, hosting providers, or organizations; private IPs usually come from local DHCP.
- Troubleshooting: private IPs help fix local printers, cameras, routers, and DHCP issues; public IPs help diagnose VPN route, geolocation, ASN, DNS, and account-access issues.
- Remote access: a private IP alone is not enough for internet access to a device; remote access needs a safe path such as a private VPN, properly secured gateway, or managed service.
- Privacy interpretation: hiding or changing the public IP does not erase local private addressing, account identity, cookies, browser fingerprinting, or provider records.
- IPv6 behavior: IPv6 may reduce the need for NAT, but it still needs sensible firewalling and careful router configuration.
IPv6 private, public, and local-style addresses
IPv6 does not map perfectly onto the old private-versus-public IPv4 model. A device can have several IPv6 addresses at once, with different scopes:
- Global unicast IPv6: routable on the public internet when firewall and routing allow it. This is the closest equivalent to a public IPv6 address.
- Unique local IPv6:
fc00::/7, commonly seen asfd00::/8for locally assigned unique local IPv6 addresses. This is local-style IPv6 space, not globally routed public internet space. - Link-local IPv6:
fe80::/10, used for communication on the local link. RFC 4291 defines core IPv6 addressing architecture, including address scopes. - Temporary IPv6 addresses: some systems use temporary addresses for outbound connections to reduce long-term correlation.
If your network uses IPv6, the public/private question becomes: which IPv6 address is visible to websites, which one is only local, and whether your router firewall handles inbound traffic as expected. Do not assume IPv6 is unsafe, and do not assume NAT is required for security.
CGNAT and shared public addresses
Carrier-grade NAT, or CGNAT, adds another layer. Your router may receive an address that is not a normal public IPv4 address, while your ISP shares a smaller pool of public IPv4 addresses across many customers. RFC 6598 defines 100.64.0.0/10 as shared address space often associated with this kind of provider-side NAT.
CGNAT is common on mobile networks and some home ISPs because IPv4 addresses are limited. It can break or complicate port forwarding, self-hosting, cameras, game servers, inbound VPN, and peer-to-peer connections. If your router WAN address is in 100.64.0.0/10, 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16, but MyIPScan shows a different public IP, your ISP may be adding another NAT layer.
How to check both safely
- Open What Is My IP. This shows the public IP visible to websites for this browser session.
- Open your device network settings to find the local/private IP. On Windows, use
ipconfig. On macOS, check Network settings or usenetworksetup -listallhardwareportsandipconfig getifaddrfor the active interface. On Linux, useip addr. - Check the router admin page from your trusted local network only. Look for LAN/DHCP clients to see private addresses and WAN/Internet status to see what the router received from the ISP.
- Compare the router WAN address with MyIPScan's public IP result. If they differ, a VPN, proxy, work tunnel, mobile carrier, or CGNAT layer may be involved.
- Run ASN Lookup and IP Geolocation Lookup for context on the visible public IP.
- If you use a VPN or unusual browser profile, run DNS Leak Test, WebRTC Leak Test, and IPv6 Leak Test.
Only test networks and devices you own or are authorized to manage. You do not need to probe unrelated IP addresses to understand private vs public IP addresses.
Common mistakes to avoid
- Do not share router admin pages on the public internet. Use safer remote access patterns, such as a private VPN to a trusted network, strong authentication, and updated firmware.
- Do not assume NAT means everything is safe. NAT can hide local addresses during normal outbound IPv4 traffic, but open ports, UPnP, weak passwords, vulnerable devices, and cloud relays can still create risk.
- Do not confuse a public IP with a person. Shared Wi-Fi, VPNs, mobile networks, CGNAT, offices, and households can put many people behind one visible address.
- Do not expect private IPs to be unique globally. Seeing
192.168.1.10tells you almost nothing about which home or office it came from. - Do not disable IPv6 as a first answer. Understand whether the address is global, unique local, link-local, or temporary, then fix routing, firewall, VPN, or DNS behavior.
When private vs public IP addresses matter most
- Port forwarding or remote access does not work. The router WAN address, public IP, firewall rules, and CGNAT status may matter more than the device's private IP.
- A printer, NAS, camera, or smart TV cannot be found locally. The private IP, gateway, subnet, and router device list are usually the first things to check.
- A game console or camera cannot be reached from outside. Public IP, CGNAT, port forwarding, and safer remote-access design matter.
- A VPN changes the public IP but not the local address. The VPN route can change what websites see while the router-assigned private IP stays the same.
- IPv6 is active. Devices may have global, unique local, link-local, and temporary IPv6 addresses, so scope and firewalling matter.
Questions about private and public IP addresses
What is the difference between a private IP and a public IP?
A private IP works inside a local network, such as a home, office, or Wi-Fi network. A public IP is the address visible to websites and internet services. Routers often use NAT so several private devices can share one public IPv4 address.
Can the internet connect directly to my private IP address?
Usually, no. Private IPv4 addresses are not routed across the public internet. Remote access normally needs a public IP, port forwarding, VPN, cloud relay, or another gateway, and those setups should be secured carefully.
How do I check my public IP and private IP?
Use What Is My IP to see the public IP visible to websites. Use your device network settings, ipconfig, ifconfig, ip addr, or your router DHCP list to find the private IP used inside your local network.
Is CGNAT the same as a private IP address?
Not exactly. CGNAT means your ISP may place your router behind another shared address layer, often using 100.64.0.0/10 shared address space. Your home devices can still use private addresses behind your router.
Does a VPN change my private IP address?
A VPN usually changes the public IP websites see by routing traffic through a VPN server. It usually does not change the local private IP assigned by your router, although the VPN app may add a separate tunnel interface address.
What are the private IP address ranges?
The three reserved private IPv4 ranges are: 10.0.0.0/8 (used by large networks), 172.16.0.0/12 (mid-size networks), and 192.168.0.0/16 (home routers). These addresses are not routable on the public internet by design.
Why does my device have both a private IP and a public IP?
Your router uses NAT (Network Address Translation) to share one public IP across multiple devices at home. Each device gets a private IP on the local network, while the router presents a single public IP to the internet.
Can two devices have the same private IP address?
Not on the same network — your router enforces uniqueness within your LAN. However, the same private IP range (like 192.168.1.x) is used by millions of separate home networks simultaneously since private IPs are not globally routed.
What is NAT and why does it matter?
NAT (Network Address Translation) lets a router translate between private IPs inside your home and the single public IP seen on the internet. It conserves IPv4 address space and provides a basic barrier between your devices and direct internet exposure.
How does IPv6 change the private vs public IP distinction?
IPv6 provides enough addresses for every device to have a globally unique public address, reducing the need for NAT. However, link-local addresses (fe80::/10) still function like private IPs for local network communication only.
IPv4 vs IPv6: two address versions
IPv4 addresses usually look like 203.0.113.7. IPv6 addresses look like 2001:db8::1 and use hexadecimal blocks that can be shortened. IPv6 exists because IPv4 address space is limited and the internet needed more globally routable addresses.
Many networks now use both. A laptop might have a private IPv4 address, a public or shared IPv4 path through the router, a link-local IPv6 address, a temporary IPv6 address, and a VPN exit IP at the same time. That is normal, but it can confuse IP, DNS, WebRTC, and geolocation checks.
For a dedicated comparison, read IPv4 vs IPv6. For allocation details, see How IP Addresses Are Assigned and the IANA IPv4 address space registry.
What an IP address can reveal
A public IP can often reveal the internet provider or network owner, ASN, rough country or region, and sometimes a nearby city. It can also show whether traffic appears to come from a VPN, data center, mobile network, hosting provider, school, company, or residential ISP.
That information can be useful for fraud checks, login security, content delivery, troubleshooting, abuse handling, and geolocation. It is also why IP addresses can be sensitive. A rare static IP or workplace network can be easier to correlate than a shared mobile or VPN exit address.
Still, IP geolocation is an estimate. It should not be treated as proof of an exact home address or physical seat. For more detail, read IP Geolocation Accuracy and Can Someone Track Me by My IP Address?.
What an IP address cannot prove by itself
- It cannot reveal your passwords.
- It cannot open your files.
- It cannot prove your exact home address from public lookup alone.
- It cannot prove which person used a shared device, home router, VPN exit, school network, or mobile carrier IP.
- It cannot remove the need to check cookies, logins, browser fingerprints, device identifiers, payment records, and provider logs.
An IP address is one signal. Stronger identification usually comes from combining IP logs with timestamps, account activity, browser signals, device information, billing records, or provider records.
Why an IP address matters for normal users
An IP address becomes practical when something looks wrong: a website shows the wrong city, an account flags a login, a game console cannot host a session, a VPN does not appear to change location, or a router device list shows an unfamiliar address. In those cases, the IP address helps narrow the problem, but it rarely answers the whole question by itself.
- Privacy checks: compare your public IP, DNS resolver, IPv6 route, and WebRTC candidates after changing VPN or browser settings.
- Account security: expect some platforms to react when the IP country, ASN, device, and login pattern change at the same time.
- Home troubleshooting: use local IP addresses to find printers, routers, cameras, consoles, TVs, and NAS devices on your own network.
- Remote access: check whether you have public IPv4, CGNAT, IPv6, a static address, or a dynamic address before exposing any service.
- Website support: provide your public IP, ASN, approximate location result, and timestamp when reporting false blocks or wrong region results.
Keep the scope clear. Checking your own IP address is normal troubleshooting. Scanning or probing networks you do not own or administer is different and should not be treated as ordinary IP lookup.
How to check your IP address safely
- Open What Is My IP to see the public IP visible from this browser session.
- Compare Wi-Fi and mobile data if you need to know whether the address changes by network.
- Use IP Geolocation Lookup and ASN Lookup to identify provider and location signals.
- Run DNS Leak Test, IPv6 Leak Test, and VPN Leak Test after changing VPN, DNS, browser, or router settings.
- Record results only for networks and devices you own or are authorized to troubleshoot.
If you use a VPN, websites usually see the VPN server's exit IP rather than your ISP-assigned public IP. That can reduce some network exposure, but it does not make you anonymous and does not remove account or browser tracking.
Common IP address mistakes
- Confusing public and private IPs:
192.168.1.20may identify a laptop inside your home, but it is reused on many networks and is not your public internet address. - Assuming a city lookup is exact: city-level geolocation can be stale, routed through another area, or influenced by mobile, VPN, proxy, and ISP architecture.
- Thinking dynamic IP equals privacy: a changing IP does not remove accounts, cookies, browser fingerprints, payment records, or device identifiers.
- Expecting a VPN to solve everything: a VPN changes the visible network route, but DNS, WebRTC, IPv6, accounts, and browser behavior still matter.
- Opening router admin or remote services directly: public IP reachability should be handled with strong authentication, firewalling, updates, and safer remote-access design.
IP address vs DNS, URL, and domain name
An IP address is not the same thing as a domain name or a full URL. A domain such as myipscan.net is a human-readable name. DNS helps translate that name to an address. A URL can include a protocol, domain, path, query string, and page location. The IP address is the network destination used to move packets.
This distinction matters for privacy. A public IP lookup may show the network path. DNS may show domain-level lookups. A URL path may reveal a specific page, but HTTPS usually protects that path from ordinary network observers. Browser cookies, accounts, and fingerprints can identify a session even when the visible IP changes.
When troubleshooting, avoid mixing these layers. If a website blocks your IP, check IP reputation, ASN, VPN, proxy, or carrier routing. If a domain fails to load, check DNS. If only one account behaves strangely, the cause may be account security, device recognition, or browser state rather than the IP address alone.
When your IP address matters most
- Login security: unusual IP, ASN, country, or device patterns may trigger account checks.
- VPN troubleshooting: IP, DNS, IPv6, and WebRTC results can show different network paths.
- Gaming and remote access: public IP, CGNAT, firewall rules, and router settings affect inbound connectivity.
- Email and server reputation: static IPs, shared IPs, blacklists, reverse DNS, and ASN reputation can affect deliverability.
- Privacy review: IP address signals combine with cookies, account logins, browser fingerprints, and device data.
What to do next
If your goal is basic awareness, check your public IP and compare it with your local IP. If your goal is privacy troubleshooting, check IP, DNS, IPv6, WebRTC, geolocation, and ASN signals together. If your goal is remote access or hosting, find out whether you have a public IP, CGNAT, static assignment, dynamic assignment, and sensible firewall controls.
The practical answer to what is an IP address is simple: it is a routing identifier. Treat it as useful and sensitive, but do not overread it as a complete identity, exact location, or security verdict.
Frequently asked questions
What is an IP address?
An IP address is a network address used to send traffic to and from a device, router, server, or network interface. It is a routing identifier, not a guaranteed personal identity.
Is my public IP the same as my local IP?
No. Your public IP is visible to internet services, while local private IP addresses are used inside a home, office, or device network. A router often translates between them.
Does an IP address show my exact home address?
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 IP address change?
Yes. Many home and mobile connections use dynamic public IPs that can change. Static IPs stay more consistent, while VPNs and proxies can show a different exit IP.
How do I check my IP address safely?
Use a browser-based IP check, compare Wi-Fi and mobile data if needed, and review DNS, IPv6, WebRTC, geolocation, and ASN results when troubleshooting privacy or routing.
Who assigns IP addresses?
IANA (Internet Assigned Numbers Authority) manages the global IP address space and delegates blocks to regional registries (ARIN, RIPE, APNIC, etc.), which in turn assign ranges to ISPs and organizations that assign individual addresses to users.
Can someone track my location using my IP address?
An IP address can reveal your approximate city and ISP, but not your exact street address. Law enforcement can request precise location data from an ISP, but websites themselves cannot pinpoint your home from an IP alone.
What is a dynamic IP address versus a static IP address?
A dynamic IP is assigned by your ISP automatically via DHCP and may change periodically. A static IP stays fixed and is used for servers, business accounts, or specific remote-access needs. Most home users have dynamic IPs.
Does using a VPN hide my IP address?
A VPN replaces your public IP with the VPN server IP for websites you visit. However, DNS leaks, WebRTC, and IPv6 can still reveal your real IP if the VPN is not configured correctly. Use a leak test to verify.
What is the difference between IPv4 and IPv6?
IPv4 uses 32-bit addresses (e.g. 203.0.113.7) with about 4.3 billion possible addresses. IPv6 uses 128-bit addresses (e.g. 2001:db8::1) with vastly more space. Most devices today support both simultaneously in dual-stack mode.
Use Safe Copy
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 network explanations, no privacy guarantees, no exact-location overclaims, no unsafe remote-access advice, and careful distinction between public IPs, private IPs, IPv4, IPv6, NAT, CGNAT, and geolocation signals.