Your IP address is visible at the network layer of any device you use. On a computer or phone, open Settings or run a terminal command. On a router, check the admin page or the device's network menu. For your public address, load a site like whatismyip.com or search "what is my IP." The number you see depends entirely on which layer you are asking about.
The answer to "where to find my IP address" splits into two distinct questions. Are you asking about the private address your device uses to talk to your router? Or the public address the internet sees? They are almost never the same number. Mixing them up is the most common reason people get confused. This guide separates the two, explains the machinery behind each, and shows you where to look on every major platform.
How IP addresses get assigned
Every device on a network needs an address so packets can find it. The mechanism that hands out those addresses is called DHCP, the Dynamic Host Configuration Protocol. When your phone joins Wi-Fi, it broadcasts a request. The router's DHCP server replies with a lease: an address, a subnet mask, a default gateway, and DNS servers. Leases typically last 24 hours on home networks and can be renewed. Your device usually keeps the same address for long stretches because the server remembers recent assignments, but nothing guarantees it.
The address you get this way is a private address, drawn from reserved ranges set aside by the Internet Assigned Numbers Authority. The three blocks are 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16. These numbers cannot route on the public internet. A router running network address translation, or NAT, rewrites the private source address on each outgoing packet to its own public address. It tracks the mapping in a translation table so return traffic can be sent back to the right device. This is why every device in your home can share one public IP.
The public address itself belongs to your internet service provider, not to you. The ISP allocates blocks from regional internet registries, and those registries receive them from IANA. When your router connects, the ISP assigns a public address by DHCP or, on some fiber and business connections, via PPPoE session setup. Most residential connections receive a dynamic public address that changes on reconnect or after a lease expires, though some ISPs keep it stable for months.
IPv4 addresses are 32 bits long, which yields roughly 4.3 billion unique addresses. That supply ran out at the registry level years ago, which is why carriers use carrier-grade NAT to share one public IPv4 address among many subscribers. IPv6 uses 128 bits, producing about 340 undecillion addresses. Most modern devices get a link-local IPv6 address automatically via stateless autoconfiguration, and many get a global one too. If you see a fe80:: address, that is link-local and only works on the local segment. A 2000::/3 address is a real public address.
The plain-language version: your device has a private address for talking to the router, the router has a public address for talking to the internet, and NAT is the translator between them.
What the numbers actually reveal
An IPv4 address is not a single number but a 32-bit value written as four octets. Each octet ranges from 0 to 255, so there are 256 possible values per position. The subnet mask tells you which bits identify the network and which identify the host. A home router commonly uses 255.255.255.0, meaning the first three octets are the network and the last octet is yours to use.
The private address space is smaller than it looks. The 192.168.x.x block holds about 65,000 addresses, but home routers typically hand out only from 192.168.1.2 through 192.168.1.254. The default gateway usually sits at .1 or .254. If you see 192.168.1.47, you can infer that 192.168.1 is your local subnet and 47 is your device's position on it.
Public addresses carry geographic information at the registry level, not the street level. An IP geolocation database maps blocks to countries with high confidence and to cities with much lower accuracy. Studies of geolocation accuracy have found city-level error distances commonly in the tens of miles, sometimes hundreds. Your public IP reveals your approximate region and your ISP, not your home address. Sites that claim precise location from an IP are usually reading a browser's location permission, not the IP itself.
Dynamic versus static matters for what you can rely on. A dynamic public address can change without warning, which breaks inbound connections to a home server unless you use dynamic DNS. A static address stays fixed and is typical on business plans. The distinction also affects privacy: a dynamic address makes long-term tracking harder, though not impossible.
Local IP lookup by platform
The local address is the one you find on the device itself. Each platform hides it in a slightly different place.
On Windows, open Settings and go to Network & Internet, then click your connection and look at the properties. The IPv4 address appears there. Alternatively, open Command Prompt and type ipconfig. The output lists every adapter, and the IPv4 Address line under your active adapter is your local address. The Default Gateway line is your router's address.
On macOS, open System Settings and go to Network. Select your active connection and the IP address appears in the detail pane. In Terminal, the command ipconfig getifaddr en0 returns the Wi-Fi address, and en1 usually covers Ethernet on laptops.
On iPhone and iPad, open Settings, tap Wi-Fi, and tap the info icon next to your network. The IP Address row shows the local address. On Android, open Settings, go to Network & Internet or Connections, tap Wi-Fi, and select your network. The address appears in the network details.
On Linux, the command ip addr show lists every interface with its address. The older ifconfig still works on many distributions. Look for the interface carrying your default route, usually wlan0 or eth0.
On a router, log in at the gateway address, typically 192.168.1.1 or 192.168.0.1. The administration page lists connected devices and their assigned addresses. This view is useful because it shows every device on the network at once.
Public IP lookup methods
For the address the internet sees, you need an external observer. The simplest method is to search "what is my IP" in any search engine, which returns your public address at the top of the results. Dedicated sites like whatismyip.com and ipinfo.io do the same and often show your ISP and approximate region. The mechanism is ordinary: the site sees the source address on the incoming connection, which after NAT is your public address.
The command line works too. On Windows, curl ifconfig.me returns the address. On macOS and Linux, the same command works, or you can use dig with a resolver service that echoes your address back. The output is plain text, one line.
When you use a VPN, the public address you see belongs to the VPN server, not your home connection. The local address stays the same. This is why a VPN changes what remote sites see but not what your router sees. If you want to confirm whether a VPN is active, compare your public address with and without it connected.
Mobile networks add a layer. On cellular data, your phone receives a carrier-grade NAT address that is itself private, and the carrier's public address is shared across many users. You cannot get a stable inbound connection on most cellular plans for this reason.
Comparison table: where each address lives
| Address type | Where it is assigned | Where to find it | Typical range or format |
|---|---|---|---|
| Local IPv4 | Router DHCP server | Device settings or ipconfig/ip addr | 192.168.x.x, 10.x.x.x, 172.16-31.x.x |
| Local IPv6 link-local | Device autoconfiguration | Device network details | fe80::/10 prefix |
| Public IPv4 | ISP | Search "what is my IP" or curl ifconfig.me | Any non-private 32-bit address |
| Global IPv6 | ISP or router | Device details or external site | 2000::/3 prefix |
| Router gateway | Router firmware | ipconfig or router admin page | Usually the .1 or .254 in your subnet |
| VPN-assigned public | VPN provider | External site while connected | Provider's address block |
Edge cases that change the answer
A few situations make the standard answers wrong or misleading.
Double NAT occurs when you have two routers in series, such as a router behind an ISP modem that also routes. Your device's gateway points to the inner router, whose own uplink address is private. The public address you see externally belongs to the outer device. Inbound connections fail unless you forward ports on both routers or put the inner one in bridge mode.
Carrier-grade NAT is common on cellular and some fixed wireless plans. You cannot open inbound ports at all, because the carrier does not give you a public address. Port forwarding guides that assume a home router will not work here.
VPN split tunneling can send some traffic through the tunnel and some around it. A browser-based check might show the VPN address while a terminal command shows your real one, depending on routing rules. Compare more than one method before concluding.
Virtual machines and containers have their own addresses. A VM on a bridged adapter appears as a separate device on the LAN with its own DHCP lease. A container on a Docker bridge network gets an address in a private range that exists only inside the host. Tools that check the host's address will not show the container's.
Proxy settings can route browser traffic differently from system traffic. A browser configured to use a proxy shows the proxy's address to websites, while curl without proxy settings shows your real public address.
IPv6 changes the privacy picture. Many devices generate temporary IPv6 addresses that rotate for privacy, so the address you see today may differ from tomorrow's. The stable address is derived from the interface identifier, but operating systems increasingly prefer temporary ones.
Common misconceptions
The biggest misconception is that your IP address identifies you personally. It identifies a connection point, and on shared networks that point covers many people. Law enforcement can sometimes trace an address to an ISP subscriber through legal process, but a website cannot. Treat the address as a rough regional marker, not a name tag.
A second misconception is that changing your IP makes you anonymous. Your ISP still sees your traffic and knows which subscriber held which address at what time. A VPN shifts trust from the ISP to the VPN provider but does not eliminate it. Browser fingerprinting, cookies, and account logins identify you regardless of address.
A third is that private addresses are secret. They are not. Every device on your Wi-Fi can typically see the subnet, and the router's admin page lists them. The private address is an organizational tool, not a security boundary.
A counterintuitive detail worth knowing: your public IP can be shared with strangers. Under carrier-grade NAT or a busy household, hundreds of people may present the same public address. This is why some sites rate-limit or block by IP and why one blocked user can affect others behind the same address. It also means an abuse report against an IP may not point to the person you think.
Practical steps and thresholds
Use these steps to answer the question for your own device and to verify what you find.
To find the local address on any device, open network settings and read the IP line, or run ipconfig on Windows, ip addr on Linux, or ipconfig getifaddr en0 on macOS. To find the public address, search "what is my IP" or run curl ifconfig.me in a terminal. To find the router's address, read the Default Gateway line from ipconfig or ip addr, then open that address in a browser. To confirm a VPN is working, compare the public address with the tunnel connected and disconnected; they should differ. To check whether you are behind carrier-grade NAT, compare the address on your router's WAN page with the public address an external site reports; if they differ, you are behind at least one NAT layer. To check for double NAT, look at the WAN address on your inner router; if it is a private address like 192.168.x.x or 10.x.x.x, a second router is in front.
Thresholds to keep in mind: a subnet mask of 255.255.255.0 means 254 usable host addresses. The private ranges are 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16. A fe80:: prefix is link-local and not routable. A 2000::/3 prefix is globally routable IPv6. DHCP leases on home routers commonly run 24 hours, so an address can change after a day offline.
Red-flag warnings: A public address that changes constantly can break remote access and dynamic DNS setups; check your ISP's policy before relying on it. Port forwarding instructions that assume a public address will fail behind carrier-grade NAT. Sites that claim to show your exact street address from an IP are almost always using browser location permissions instead. Comparing addresses across a VPN without checking split-tunnel rules can give contradictory results.
Limitations and what IP data cannot tell you
An IP address is a routing label, not an identity. It cannot reliably tell you a person's name, exact location, or device type. Geolocation at the city level is approximate and can be wrong by large margins, especially for mobile and VPN addresses. The address also says nothing about whether a connection is secure; that depends on encryption, not addressing.
Address assignment is dynamic in ways that defeat assumptions. A public address stable for months can change on a router reboot or an ISP renumbering. A local address can shift after a lease expires. Any setup that depends on a fixed address needs dynamic DNS or a static assignment, and neither is guaranteed on residential plans.
This article is general educational information about networking, not a security audit or a guarantee of anonymity. If you need to protect a specific system or assess exposure, consult a qualified network or security professional who can examine your actual configuration.