What is my IP address?

Your IP address, location and provider — then the anonymity check: whether you read as a proxy or VPN, whether WebRTC leaks your real address, and what your TLS handshake and packets say about your OS.

  • Server
  • IP intelligence
  • Browser fingerprint
  • WebRTC
  • TLS / JA3
  • Latency
  • Protocol
  • UDP / QUIC
  • WebSocket

What this page actually checks

Every site you open learns more about you than your IP address. It sees which operating system your packets look like they came from, how your browser negotiates encryption, what your clock says, and — if WebRTC is left open — the address behind your proxy. Anti-bot systems compare those signals against each other. One that contradicts the rest is what gets an account flagged, a checkout blocked or a scraper served a CAPTCHA.

This page runs the same reads. It shows your address and where it places you, then the things a proxy user rarely gets to see: the OS your TCP packets betray, your TLS fingerprint, whether UDP traffic reaches the network at all, and whether any of it disagrees.

How to read the result

Exit IP and location

The address a site sees, plus the country, city and network it belongs to. If you are on a proxy this should be the proxy's address — if your own shows up instead, the proxy is not carrying your browser traffic.

Proxy or VPN detected

Commercial IP databases keep lists of ranges known to belong to hosting providers, VPN services and public proxies. Being on such a list is not fatal on its own, but it is the first thing a fraud filter looks at — and datacenter addresses are on those lists by definition.

OS (browser says) vs OS (packets say)

Your browser announces an operating system in its User-Agent. The way your TCP packets are shaped — TTL, window size, MSS, the order of TCP options — betrays another one, and that one cannot be edited from JavaScript. A Windows browser arriving in Linux-shaped packets means something sits between you and the site. This is the single most damaging mismatch on the page.

WebRTC

WebRTC asks your device for its own addresses so browsers can connect directly for calls. It routinely bypasses an HTTP proxy, which is why a proxied browser can still hand over its real IP. If the WebRTC address differs from the exit IP, your proxy is leaking.

TLS and JA3

The way your client offers cipher suites and extensions during the TLS handshake forms a fingerprint — JA3, and its newer form JA4. Real browsers have well-known fingerprints; automation libraries have their own. A fingerprint that does not match the browser you claim to be is a strong bot signal.

Clock and timezone

Your IP places you in one timezone; your operating system's clock says another. Legitimate travellers rarely produce this mismatch and VPN users produce it constantly, so it is a cheap and popular check. Matching your device timezone to your exit location removes it.

Latency, HTTP/2, HTTP/3 and UDP

Round-trip time hints at how far your traffic really travels. Whether HTTP/3 and WebTransport connect at all says whether UDP reaches the network: most HTTP and SOCKS5 proxies tunnel TCP only, so a browser behind one usually falls back to HTTP/2 — that is normal, not a fault.

Browser fingerprint

Screen size, CPU cores, memory, GPU model, the canvas hash and the automation flag. None of this depends on your IP, all of it is readable from any page, and together it identifies a browser profile across sessions — which is what antidetect browsers exist to manage.

If the verdict is bad

Most findings come down to two things: an address with a bad reputation, or signals that contradict each other. Both are fixable.

WebRTC is leaking

Disable WebRTC in your browser, use an extension that blocks it, or use a browser profile that routes it through the same proxy. In an antidetect browser this is a setting, not a plugin.

The OS doesn't match

Either align your browser profile with the proxy's real OS, or use a proxy whose OS fingerprint can be set to match your profile. Our ISP and datacenter proxies support this directly.

The timezone doesn't match

Set your device or browser profile to the timezone of your exit IP. Antidetect browsers do it per profile; on a plain browser it is a system setting.

The IP is flagged

Datacenter ranges are flagged by design. If the target site is strict, a residential or ISP address — a real one, issued to a household or by a tier-1 provider — is what passes where a datacenter IP will not.

FAQ

Frequently asked

About this checker and what it reports

It is free and needs no account. Open the page and the check runs on its own.

The last check for an address is kept for 30 days so it can be reopened at proxya.co/tools/ip-checker/<that address> — that is what the Copy report button hands you. Anyone who knows the address can read that page, and the report includes browser details such as your user agent and screen size. After 30 days it is deleted.

IP reputation databases classify whole ranges. Mobile carriers using CGNAT, corporate networks and some ISPs get flagged the same way hosting providers do. If the rest of the report agrees with itself, a single proxy flag rarely matters.

WebRTC is a browser feature for real-time audio and video. To connect two peers directly it collects your device's own addresses — and it does that outside your HTTP proxy. That is why a browser on a proxy can still reveal the address underneath.

It doesn't read your system. It reads the shape of your TCP packets — time-to-live, window size, maximum segment size, the order of TCP options — which differs between operating systems and is set by the OS kernel, not by the browser. That is why it cannot be spoofed from JavaScript and why it disagrees with a faked User-Agent.

Almost certainly not. HTTP/3 runs over UDP, and HTTP and SOCKS5-TCP proxies tunnel TCP only. Chromium also tends to switch QUIC off when a proxy is configured. Falling back to HTTP/2 is the expected behaviour.

This page tests the connection you are browsing on right now. The proxy checker takes a list of proxies you paste in and tests each one from our servers, reporting whether it answers, how fast, and where it exits.