What's My IP, User Agent & Browser Info
See your public IP address, user agent, request headers and browser capabilities, instant lookup, no tracking.
Loading What's My IP, User Agent & Browser Info… If nothing happens, please enable JavaScript.
Frequently asked questions
What data does this tool send to your servers?
What is IP geolocation and how accurate is it?
Why does my IP look different here than on other 'what is my IP' sites?
What are HTTP request headers and why does my browser send them?
Is my IP address stored or logged anywhere?
How is this different from running 'curl ifconfig.me' or similar commands?
My IPv6 address changes frequently — is that normal?
Can websites track me across different sessions using my IP address?
What does 'behind CGNAT' mean and how does it affect me?
What is a VPN and how does it change what this tool shows?
About What's My IP, User Agent & Browser Info
Your public IP address is the numeric label assigned to your internet connection by your Internet Service Provider (ISP), and it is the address that every website, server, and online service sees when you connect to them. IPv4 addresses are 32-bit numbers written as four octets (e.g. 203.0.113.42), while IPv6 addresses are 128-bit numbers written in hexadecimal groups (e.g. 2001:db8::1). If your ISP supports IPv6, you may have both. Your IP address is used for routing traffic back to you, but it is also the basis for IP geolocation — a technique that maps addresses to approximate physical locations using databases of ISP allocation records. Geolocation is widely used for content regionalisation, fraud detection, and access control, but it is an approximation: it typically resolves to the city level at best and can be off by hundreds of kilometres, especially for mobile networks and VPNs.
Knowing your public IP is useful in a surprising range of everyday situations. Remote access users need it to configure port forwarding rules on their routers. Game server admins whitelist IPs for admin access. Security-conscious users check it to confirm a VPN is actually routing their traffic. Developers building geolocation-dependent features test what location their API sees. Network engineers verify that dual-stack IPv4/IPv6 connectivity is working as expected. IT support staff often ask 'what's your IP?' as a first troubleshooting step for remote access problems.
This tool reads the IP address directly from the HTTP request your browser makes to our server — no external lookup is needed for the raw IP itself. It also parses every HTTP header your browser includes in the request, shows your parsed User-Agent string, and runs a set of client-side JavaScript checks for browser capability detection (such as cookie support, JavaScript availability, and screen metrics). If an IPv6 address is available on your connection, the tool will show it in addition to your IPv4 address. We do not log, store, or share any of this information — the result is computed per-request and discarded after your browser receives it.
When reading your results, remember that the IP address shown is your public-facing address, not your private LAN address (which typically starts with 192.168, 10., or 172.16–31.). If you are behind a corporate proxy, carrier-grade NAT, or a shared Wi-Fi connection, multiple users may share the same public IP. The geolocation shown — if any — is an estimate based on your ISP's IP allocation and should not be treated as your precise location. HTTP headers like Accept-Language, Accept-Encoding, and DNT (Do Not Track) reveal your browser's preferences and are sent automatically on every request you make to any website.
The Number That Connects You to the World
The 32-bit IPv4 address space was designed in 1981 by Vint Cerf and Bob Kahn as part of the original TCP/IP specification, yielding approximately 4.3 billion unique addresses. At the time, this seemed more than sufficient — the entire internet consisted of a few hundred machines. By the early 1990s it was clear that 4.3 billion addresses would not be enough for a global internet, prompting the development of IPv6 with its 128-bit address space providing 340 undecillion addresses (3.4 × 10^38). The exhaustion of the central IANA IPv4 pool was officially declared on 3 February 2011, followed by regional registries exhausting their pools throughout the 2010s.
Network Address Translation (NAT), the technology that allows many devices to share a single public IP through a home router, was initially regarded as an ugly hack and a violation of the internet's end-to-end design principle. Its author, Paul Francis (then at NTT), later said in interviews that he expected NAT to be a two-year stopgap while IPv6 was deployed. Instead, NAT extended IPv4's life by decades and is now so ubiquitous that most internet users have never had a routable public IP address of their own. The side effect is that the internet's original peer-to-peer design — where any node could initiate a connection to any other node — has been substantially eroded.
IP geolocation databases are maintained by companies like MaxMind (GeoIP), IP2Location, and various cybersecurity vendors. They are built by correlating ISP registration records (WHOIS and ARIN/RIPE/APNIC allocations), BGP routing announcements, and active measurement data. The business is surprisingly lucrative: geolocation is used to enforce content licensing agreements (why a Netflix show is available in one country but not another), prevent payment fraud, serve localised advertising, and comply with sanctions regulations. The data is imperfect by nature because IP allocations frequently change and ISPs may serve customers far outside their registration geography.