Proxy detection test
Websites don't need your real IP to spot a proxy. They compare it with everything else your browser gives away. This test runs the checks they use, from time zone and language to WebRTC and automation flags, and shows the fingerprint any site can read.
The fingerprint is read and hashed in your browser and never leaves it. Our server only answers with the IP and headers your request arrives with and who owns that IP. Nothing is stored.
What each check looks for
Time zone vs IP location
Browser language
Proxy headers
WebRTC IP leak
Network type
Automation and platform
How to pass a proxy detection check
- Start with the right IP type. Data center IPs fail the network check before anything else is read. Use ISP, residential or mobile IPs for sites that score risk.
- Match time zone and language to the proxy. Pick a proxy in the country you appear from, then set the browser or profile time zone and language to fit it.
- Close the WebRTC leak. Let the anti-detect browser replace the WebRTC address with the proxy IP, or restrict WebRTC with an extension.
- Don't half-spoof the browser. Changing only the User-Agent while the platform, screen and GPU say otherwise is easier to catch than not changing it at all.
- Keep one identity per account. Give each profile its own sticky IP and fingerprint, and don't switch between them mid-session.
Frequently asked questions
Not from the connection itself: a good proxy forwards your traffic like any other client. Sites infer it from evidence around the connection: an IP owned by a hosting company, a time zone or language that doesn't fit the IP's country, headers a proxy added, a WebRTC address that differs from the proxy IP, or a browser that admits to automation. This test runs those same checks.