What Is My IP Address? How to Find It and What It Shows
Abhay Khant
Jan 1, 1970 • 5 min read
What Is My IP Address? How to Find It and What It Shows
- Your public IP is the return address servers see when your devices connect
- Private addresses like 192.168.x.x never leave your router; only the public one travels
- An IP reveals approximate location and provider, never a street address
- Websites can also see protocol details: we captured TLS 1.3 and HTTP/2 on a live trace
What an IP address actually is
An IP address is the numeric label that identifies a device on a network using the Internet Protocol. Version 4, specified in [RFC 791](https://datatracker.ietf.org/doc/html/rfc791), writes it as four numbers from 0 to 255, such as 203.0.113.42. Version 6, defined in [RFC 8200](https://datatracker.ietf.org/doc/html/rfc8200), expands the space into eight hexadecimal groups because four billion v4 addresses ran out years ago. Every packet crossing the internet carries these labels so replies know where to come back.
The distinction that matters most for everyday questions: your laptop usually holds a private address inside your local network while your router holds the public one visible to websites. When you search what is my IP, the useful answer is the public one.
Public versus private, precisely
[RFC 1918](https://datatracker.ietf.org/doc/html/rfc1918) reserved three ranges for private networks: 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16. Millions of homes reuse those same numbers simultaneously because they are unroutable from outside; your router translates between them and the public internet with NAT, the mechanism [the same RFC](https://datatracker.ietf.org/doc/html/rfc1918) anticipated when reserving those ranges. The [IANA special-purpose registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml) catalogs these plus other non-routable blocks such as 127.0.0.1 loopback.
| Clue | Meaning |
|---|---|
| Starts with 10., 172.16-31., or 192.168. | Private; internal to your network |
| Starts with 127. | Loopback; this machine itself |
| Anything else | Publicly routable; what websites see |
What a website really sees: a live trace
To ground this in reality rather than description, we requested a diagnostic trace from [Cloudflare's edge endpoint](https://www.cloudflare.com/cdn-cgi/trace) during research for this guide. The response carried exactly the fields any web server observes about visitors:
ip=2409:40c1:..., an IPv6 address; we truncated the tail deliberately before quoting itloc=IN, country derived from geolocation databasescolo=BOM, the edge data center serving us, Mumbaitls=TLSv1.3andhttp=http/2, protocol capabilities of our connection
The [same endpoint](https://www.cloudflare.com/cdn-cgi/trace) answers plain text for anyone curious about their own connection. Note what appeared without being asked: the network's protocol versions and coarse location ride along automatically. Also notice the address was IPv6 even though most people still assume four-dot numbers; mobile carriers hand out v6 natively under the [IPv6 specification](https://datatracker.ietf.org/doc/html/rfc8200), and dual-stack connections expose whichever family the route prefers. The IP address lookup tool shows the equivalent view for any address you paste in, returning provider and geography context.
What an IP does and does not reveal
A public IP maps to an organization, typically an ISP or mobile carrier, and to a geographic region accurate at city or regional granularity under favorable conditions. It does not name a person or resolve to a house; the hop from region to customer sits inside provider records protected by legal process almost everywhere. Websites combine IPs with cookies, logins, and browser fingerprints to build better pictures than the IP alone provides, which is the honest framing: the address is one signal among several, weak alone, meaningful aggregated.
Two modern wrinkles change old assumptions. Carrier-grade NAT means many households share single public addresses, so logs attributing activity to one IP may cover dozens of strangers. And rotating residential assignments mean yesterday's address may belong to someone else today, which is why abuse reports lean on timestamps matched against provider records.
VPNs, proxies, and the address you present
Routing traffic through a VPN replaces the public address websites see with the tunnel exit's address, moving your apparent location to wherever that server lives. Proxies behave similarly at application layers. Neither makes you untraceable; providers keep connection records, and fingerprinting correlates sessions across address changes. For the narrower goal of not broadcasting home-region context to every site visited, tunnels work as advertised, provided DNS requests follow the same path, a failure mode our [DNS leak guide](/blog/dns-leak-test-guide/) explains alongside its test.
Checking your own setup
- Look up the public address plus provider and geography context with the IP lookup tool
- Compare addresses with the VPN off and on; if both show identical values, traffic is bypassing the tunnel
- Confirm private ranges on local devices stay out of server logs by design
One label, limited secrets
Your IP address is the internet's return label: essential for every connection, revealing about network and rough geography, silent about identity and precise place. Knowing how to find it, why phones show six-group v6 strings, and what tunnels change turns a mysterious number into ordinary plumbing you can inspect whenever debugging requires it.
