- Proxy endpoint
- —
- Location
- —
- Network
- —
- Connection time
- —
One-click IP reputation, proxy quality and browser leak checks
Compare risk providers, DNS, WebRTC and streaming checks to identify network issues.
Results appear individually. Slow checks have a 24-second budget; the request waits up to 45 seconds.
Proxy overview
Local environment checks
See what a website can read from this browser. The proxy entered above is not used.
International endpoint
Domestic endpoint
The details below refer to the exit seen by this site: Not tested
The overview and risk summary load automatically. Valid risk results for the same IP are reused for 10 minutes to reduce quota usage.
Field notes & system information
OS and browser details are reported values. The fingerprint uses this site's Canvas SHA-256, calculated locally. DNS shows resolver exits observed by our authoritative node and their countries. Anonymizer refers to provider VPN/Tor flags. Blacklist status uses explicit blacklist fields, not a zero report count. Untested does not mean safe.
Environment comparison
Network and environment comparison is not yet complete.
Using proxy & browser diagnostics
12CE Proxy Lens combines proxy quality and current-browser diagnostics. Enter a proxy to test its HTTP, HTTPS or SOCKS5 exit. Local environment checksshows this browser's connection to the site, which may use a different IP.
Which checks are available?
Proxy tests include IPQS, Scamalytics, AbuseIPDB and IP2Location risk data, plus TikTok, YouTube Premium, Prime Video, Reddit and ChatGPT access checks. Browser diagnostics include DNS exits, WebRTC, Canvas, WebGL, fonts, ClientRects, TLS, HTTP/2, QUIC and TCP. Availability depends on browser, node and upstream support.
Does a low score guarantee a safe IP?
No. Providers use different data and standards. A low score does not guarantee access, and a high IP2Location score may reflect proxy identification. Not listed means only that this source did not flag the IP. Failed or missing lookups are not low-risk results.
Do different DNS or WebRTC addresses prove a leak?
Not necessarily. Split routing, public DNS, Anycast and different address families can produce differences. DNS shows resolver exits querying our authoritative node; WebRTC shows browser candidates. Compare them with your intended configuration. Our node does not test IPv6; that says nothing about your own network's IPv6 support.
Does availability guarantee playback?
Access checks reflect this request and page features only, not account eligibility, subscription rights or playback. Challenges, regional policies, upstream restrictions and timeouts may affect results.
Where is test data sent?
Proxy details are submitted to our server to establish test connections; never put credentials in links. Overview providers receive the queried IP. DNS, WebRTC and exit comparisons contact their respective nodes. Local fingerprint and extension results are not uploaded or stored. Precise location requires separate permission. See Sources & privacy for details.