$ ip --detect
What Is My IP? — See Your Public IP Address Now
See your public IPs (IPv4 and IPv6) instantly, the provider whois with ASN and reverse DNS, and what your browser reveals about you. Nothing is logged.
- nothing is stored
- free
- no sign-up
How detecting your IP works
There is no magic and no tracking: every request on the internet carries, by definition, the source IP address — that is how the response knows the way back. This page queries two routes at the same time: your browser directly asks a public echo service (ipify) which address reached it — once forcing IPv4, once accepting IPv6 —, and in parallel our server reports the IP seen on the connection to the site. Under normal conditions the paths match; when they diverge, that also tells a story (corporate proxy, CGNAT, selective VPN). The number shown is your public IP: the address of your connection as a whole (usually the router’s or the provider’s), not the internal IP of each device in the house. If you are using a VPN or a proxy, the address displayed will be the intermediary server’s — which, by the way, is a quick way to check whether the VPN is actually on.
Whois, ASN and reverse DNS: who answers for the address
Every public IP belongs to a block registered in someone’s name — a provider, a company, a university. The whois panel shows that owner (organization and ASN, the autonomous system number that announces the block on the internet’s routes), the reverse DNS (the hostname the provider associated with your address, queried over secure DNS) and the approximate region of the registration. For the raw, complete record, the RDAP link opens the official query at the regional registry — for Brazilian IPs, data that comes from Registro.br/LACNIC. It is the same investigation a security team runs when analyzing a suspicious access in the logs.
IPv4 ran out — and the transition to IPv6
IPv4, created in the 1980s, addresses the internet with 32 bits: about 4.3 billion combinations, which seemed infinite and were formally exhausted in the 2010s. The answer came on two fronts. The first was palliative: techniques like NAT and CGNAT — very common in Brazil — make several customers of a provider share the same public IPv4. The second is the definitive solution: IPv6, with 128 bits and room for 340 undecillion addresses, enough to give billions of IPs to every human being. Since the switch is gradual, networks operate in dual stack, keeping both versions at the same time — which is why you may show up with an IPv6 here and an IPv4 on another service, depending on the path the connection took.
What your browser says about you
Beyond the IP, every browser hands a series of details to any website: the user agent (browser and system), language, timezone, screen resolution, pixel ratio, CPU cores and more. In isolation, they are harmless; combined, they form a kind of fingerprint that can distinguish your browser among millions of others — even without cookies. That is how part of online advertising recognizes visitors who cleared their history. The grid above shows exactly what your browser is handing over right now, read locally.
For those who build or test software, this view is a debugging bench: checking the real user agent when investigating a bug that only happens in one browser, validating the timezone in date and time issues, confirming resolution and pixel ratio in visual QA, or quickly checking whether the corporate proxy or the VPN is up before accessing an IP-restricted environment.
Privacy in this tool
Our server only echoes the connection’s IP for comparison — nothing is logged, stored or shared, and the response goes out with the Cache-Control: no-store header, which prevents any intermediate cache from keeping it. The public IP (ipify), provider (ipwho.is) and reverse DNS (Cloudflare) lookups go from your browser straight to those public services, with no intermediation from us — CodeCrush neither sees nor stores those responses. The browser grid data is read locally and does not leave the page. Close the tab and it is gone — there is no history to erase here.
## faq
Frequently asked questions
What is the difference between IPv4 and IPv6?
IPv4 is the classic format: four blocks of numbers from 0 to 255 separated by dots (e.g. 203.0.113.42). With 32 bits, it offers about 4.3 billion addresses — which have already run out. IPv6 came to solve that: eight hexadecimal groups separated by colons (e.g. 2001:db8::8a2e:370:7334), with 128 bits and a practically inexhaustible space of 340 undecillion addresses. Today the two versions coexist in "dual stack", and the label shown above tells you which one your connection used to get here.
Is my IP fixed or does it change?
On most residential connections, it changes. The provider assigns the address dynamically (via DHCP) and may swap it when the router restarts, when the connection drops or periodically. Many providers — very commonly in Brazil — also use CGNAT, a technique where several households share the same public IPv4; in that case, the address shown here belongs to the provider’s equipment, not exclusively to you. A fixed IP is usually a separate paid service, common in business plans and required to host servers at home.
What can someone find out with my IP?
Less than it seems. With the IP, it is possible to know which internet provider you use and an approximate location — usually the city or region where the provider registered that block of addresses, which can be tens or hundreds of kilometers away from you. What can NOT be discovered: your name, your exact home address, your ID numbers or your browsing history. The link between an IP and a customer exists only in the provider’s records, which in Brazil can only be revealed under a court order, as established by the Marco Civil da Internet (the Brazilian Internet Civil Framework).
What is the difference between a public IP and a private IP?
The public IP is the address of your connection on the internet — what websites see and what this page displays. The private IP is the address of each device inside your local network, assigned by your router in reserved ranges such as 192.168.x.x, 10.x.x.x and 172.16.x.x to 172.31.x.x. All the devices in the house (laptop, phone, TV) share a single public IP through NAT — which is why websites see the same address for all of them. To see the private IP, check your operating system’s network settings; for security reasons, the browser does not expose it to web pages.
How can I browse with a different IP?
The concept is always the same: route your traffic out to the internet through another server, so websites see that server’s address instead of yours. A VPN creates an encrypted tunnel between you and that server; a proxy merely relays the requests (not always with encryption); the Tor network chains several layers of servers to make tracking harder. Switching networks also changes your IP — going from Wi-Fi to 4G/5G, for example. One important point: whoever operates the VPN or proxy gets to see your traffic, so the trustworthiness of the service matters more than the technology itself.
How do I run a whois or traceroute on my IP?
The page already shows the essentials of whois (provider, ASN, reverse DNS and the block’s region) and a link to the full official record via RDAP, the modern successor to whois. To go further, use the terminal: "whois YOUR-IP" shows the raw record with abuse contacts; "traceroute YOUR-IP" (on Windows, "tracert") reveals the route, hop by hop, between your machine and the destination; and "dig -x YOUR-IP +short" queries the reverse DNS. The tool displays these three commands already filled in with your address, ready to copy — traceroute is a system network tool and cannot be run from inside a web page.
Does this website store my IP?
No. Our server merely echoes the connection address back, with the response marked as Cache-Control: no-store — nothing is written to a database or application log, or passed on to third parties. The public IP lookups (ipify), provider/whois lookups (ipwho.is) and reverse DNS lookups (Cloudflare’s DNS-over-HTTPS) go from your own browser straight to those public services, without passing through our servers — each with its own privacy policy. The browser grid data is read locally and never leaves the page.
## other tools