Signal — Network & Device Diagnostics

Network

IP Public IP & Location

Public IP—

IP version—

IPv4 reachable—

IPv6 reachable—

ISP / Organisation—

Country—

Region / Province—

City—

Time zone (from IP)—

Time zone (browser)—

GPS location

Statusnot requested

~ Connection & Status

Online / Offline—

Connection type—

Effective type—

Estimated downlink—

Estimated RTT—

Data saver—

WebRTC / local IP

WebRTC support—

Local IP(s) found—

Local/private IPs are discovered via WebRTC ICE candidates gathered against a public STUN server — the same technique any web page could use. Modern Chromium browsers hide the real LAN IP behind an mDNS name (e.g. *.local) by default for privacy; that appears here as-is rather than resolved.

! VPN / Proxy Signals

—

Best-effort only. A browser cannot reliably detect a VPN or proxy — these are weak, sometimes-wrong heuristics (hosting/ASN name matches, timezone vs. IP-geolocation mismatches), not a verdict. Treat this as a hint, never a fact.

UA Browser Identity

User-Agent

Language—

All languages—

Platform—

Cookies enabled—

Do Not Track—

DNS DNS Resolution Demo

Browsers never expose the system's actual configured DNS resolver to JavaScript. This performs live lookups via a public DNS-over-HTTPS resolver (Cloudflare) instead, to demonstrate resolution behaviour and timing — it is not reading your OS/router DNS settings.

Device & Performance

DEV Device

Device type—

Operating system—

Browser—

Screen resolution—

Viewport size—

Color depth—

Pixel ratio—

Touch support—

CPU cores (hardwareConcurrency)—

Device memory—

Battery status—

T Performance

Page load time—

DOM content loaded—

Time to first byte—

DNS lookup (this doc)—

TCP connect (this doc)—

Live clock

Current timestamp—

Local time—

UTC time—

Connectivity Tests

PING Latency Tests

running on load…

Target	Status	Avg	Min	Max	Attempts	Last success

Cross-origin requests to these domains cannot be read by this page (CORS blocks access to status codes and response bodies for third-party origins that don't explicitly allow it). Each test instead sends a real network request in no-cors mode and times how long the browser takes to get a response back — enough to measure reachability and latency, not enough to see an HTTP status code. A target that never responds (blocked, offline, DNS failure) reports unreachable; everything else reports a timed, best-effort reachable. If this file was opened directly from disk (a file:// URL), some browsers restrict outgoing requests further — serving the file over HTTP(S) avoids that.