Your public IP is one of four signals every target reads together -- IP, timezone, locale, and fingerprint. Mismatches between them, not the IP alone, are what modern anti-bot systems flag. This page shows exactly what your browser broadcasts.
From the address alone, any site can derive your ISP or hosting provider (via ASN), a city-level location, whether the range is consumer or datacenter, and your history on shared reputation lists. None of this needs cookies or JavaScript -- it arrives with the TCP handshake. That’s why IP class is the first gate in every anti-bot stack, and why a datacenter address hits friction a household address never sees.
Sophisticated targets cross-check the layers this page shows you: a German IP with an America/Chicago timezone, an en-US-only locale, and a 4-year-old Windows UA is a walking contradiction. Alignment is the actual discipline -- pick the market, and let IP, clock, language, and fingerprint all tell that market’s story.
The address on this page is your public IP -- the one the internet sees, assigned by your ISP or proxy exit. Your device also holds a private IP (like 192.168.1.x) that exists only inside your local network and is never routable from outside. Home routers translate between the two with NAT, which is why every device in your house can share one public address. When you route through a proxy, the target sees the proxy’s public IP; your real public IP is hidden one hop back, and your private IP is never exposed at all -- unless a WebRTC leak surfaces it, which is exactly why that test matters.
An IPv4 address looks like 203.0.113.7; an IPv6 like 2001:db8::8a2e:370:7334. IPv4 space is exhausted, so carriers increasingly hand out IPv6 or share IPv4 behind carrier-grade NAT. For collection this matters two ways: some targets treat IPv6 ranges with more suspicion (they’re newer and easier to allocate in bulk), while others are IPv6-native and cheaper to reach that way. If this checker shows an IPv6 address where you expected IPv4, your network or proxy is dual-stack -- force the family explicitly in your client when a target cares.
Every IP belongs to an Autonomous System -- a network operator identified by an ASN like AS3320(Deutsche Telekom). Targets map your ASN to a category: residential ISP, mobile carrier, hosting/datacenter, or business. That category, more than the raw address, drives the trust decision -- a hosting ASN on what claims to be a home user is the single most common bot tell. This is the whole reason residential and mobile proxies command a premium: you’re paying for membership in an ASN that targets trust by default.
Three quick checks. Is the IP class what you expect?A “hosting” or “datacenter” label on what should be a home connection means a VPN or corporate gateway is in the path. Does the location match your reality? Geo-IP is city-accurate ~80% of the time and occasionally places you a region away -- normal, and exactly why sites cross-check other signals. Do the layers agree? IP country, timezone, and language should tell one coherent story; disagreement is the flag.
The IP itself is exact -- it’s the address the lookup server actually saw. The derived location is only as good as the geolocation database behind it, which is city-accurate roughly 80% of the time for fixed-line connections and considerably less for mobile and CGNAT. Browser facts (timezone, language, platform, screen) are read directly from your environment and are exact. So read the page in two registers: the IP and browser facts are ground truth; the geographic guess is a well-informed estimate that targets treat with the same healthy skepticism you should.
IP geolocation maps address ranges to locations using registry data, ISP disclosures, and inference -- not GPS. Carriers that route regionally, corporate VPNs, and freshly reassigned ranges all produce misses. This is a feature for privacy and a caveat for accuracy: never treat a single geo-IP reading as ground truth for anything that matters, and understand that the targets you collect from face the same uncertainty about you.
Sites layer several location signals and weight them by reliability. The IP is the primary source -- mapped to a country and city through geolocation databases. On top sit browser signals: the timezone your clock reports, the languages in your Accept-Languageheader, and, if you grant it, the Geolocation API’s GPS-grade coordinates. Sophisticated targets compare these and trust the agreementmore than any single value. This is why a proxy alone is a partial disguise: change the IP but leave a mismatched timezone and language, and you’ve traded one tell for another. Full location consistency means aligning every layer to the story the IP tells.
Three channels can contradict your apparent IP even behind a proxy: WebRTC ICE candidates exposing a local or VPN address, DNS resolving through your ISP instead of the tunnel, and IPv6 escaping an IPv4-only proxy. Each has a dedicated test in our tools list -- run all three before trusting any identity setup for real work.
This tool answers “what’s my IP and does my browser agree with it,” but a complete identity audit needs three more passes. A WebRTC leak testconfirms no local or real-ISP address escapes through the browser’s peer-connection APIs. A DNS leak testconfirms your lookups resolve through the proxy tunnel, not your ISP’s resolver -- a common giveaway. A fingerprint testshows the canvas, WebGL, and font signals that identify your browser regardless of IP. Run all four together and you have the full picture; run only this one and you’ve checked the front door while leaving windows open.
Load it twice: once direct, once through your proxy profile or proxied browser. Through a KnoxProxy residential exit you should see the target country’s IP, a plausible consumer ASN (Telekom, Comcast, Vodafone -- not “XYZ Hosting”), and, in a well-configured antidetect profile, a timezone matching the exit. Anything else is a configuration bug this page just saved you from discovering in production.
Bookmark this page as the first stop when a collection job misbehaves. Before blaming a target, load it through the same proxy configuration your job uses and confirm the exit is what you configured. Nine times in ten, a “the site is blocking me” ticket is really a “my egress IP isn’t what I think it is” bug -- and thirty seconds here settles it before you spend an afternoon debugging the wrong layer.
Experienced operators use this page at three moments:
Verify the proxy config produces the country and ASN you intended.
Confirm the exit matches the fingerprint’s story before an antidetect profile touches a real account.
Rule out egress-IP surprises before blaming the target.
Making this a reflexive first check -- not an afterthought -- turns a class of confusing, time-wasting bugs into a thirty-second confirmation. It’s the cheapest insurance in the whole collection workflow, and it costs nothing.
People assume a VPN or proxy makes them invisible; this page shows why that’s only half true. Your exit IP changes, yes -- but the readout above reveals everything still leaking through: a timezone that didn’t move, a browser language that gives away your real market, a screen resolution and platform that fingerprint your device regardless of IP. For casual privacy that’s fine. For serious collection or multi-account work, the gap between “my IP changed” and “I look like a consistent local user” is exactly the gap that gets accounts flagged -- and it’s visible right here, for free, before it costs you anything.
The gap between “my IP changed”and “I look like a consistent local user” is exactly the gap that gets accounts flagged.
Nothing: the readout is computed in your browser using a couple of lightweight, anonymous lookups. No storage, no fingerprint database, no account required -- the tool exists to be useful, and to demonstrate the transparency we think network tooling owes its users.
It’s worth restating plainly, because most “what is my IP” sites do the opposite: this tool builds no profile of you. The IP and network lookups are anonymous requests, the browser facts are read and displayed locally, and nothing is stored, logged, or sold. We built it as a genuinely useful utility and as a small proof of the posture we take everywhere -- transparent about what’s collected, honest about what’s inferred, and uninterested in quietly fingerprinting the people who visit. If a free tool won’t respect your data, it’s not free; you’re the product. This one isn’t built that way, and it never will be.
Your IP address is the number your ISP or network assigns your device so the internet can route data back to you. The IP checker above shows it instantly -- no download, account, or signup needed.
Geo-IP is inference, not GPS -- it's city-accurate about 80% of the time and can place you a region away, especially on mobile or VPN connections. It's a caveat for accuracy and a reason targets cross-check other signals.
Under GDPR, an IP can be personal data in context. This tool stores nothing and logs no addresses; the readout is computed in your browser with lightweight, anonymous lookups.
Not through the normal request path -- they see the proxy exit. But WebRTC, DNS, and IPv6 leaks can expose your real address; run those dedicated tests before trusting any setup.
Route your browser or job through a proxy exit in the country you want, then reload. A KnoxProxy residential exit will show that country's IP and a consumer ASN.
The one-line takeaway: your public IP is only the headline of your online identity, and this page shows the whole first paragraph -- timezone, locale, platform, screen, and the ASN behind the address. Read those layers together the way targets do, run the companion leak and fingerprint tests for the parts a single readout can’t cover, and make this your reflexive first check before and during any proxy job. Thirty seconds here regularly saves an afternoon of debugging the wrong layer, and it’s free every time. Bookmark it, share it with your team, and treat it as the standard opening move whenever an exit IP is involved -- the habit pays for itself the first time it catches a misrouted job before it wastes a morning.
Residential, mobile, ISP, and datacenter exits in 195 countries -- free trial, no credit card.