Privacy policy

This site has no accounts and does no advertising tracking. Lookups send the target to third parties. Sites your browser contacts directly can see that connection’s egress IP.

Updated · Egress Observatory

Egress monitoring and disconnect drills

Disconnect drills run only within the sampling window you start manually. Monitoring also requires an explicit start. Full IP, ASN, country and DNS records remain in your browser or the local collector you run, for at most 7 days and 10,080 samples. Exports contain full addresses. Page monitoring stops when the page closes; the local collector process must be stopped separately.

Data corrections

Only when you submit a correction are the entered IP, source, time and supporting evidence saved to persistent site storage, for up to 180 days. A private credential lets you view, supplement or delete the record. The site does not automatically submit to upstream providers. Administrators publish only explicitly selected, verified, redacted summaries. Keep the credential private; a public case ID cannot recover it.

Performance data and API usage

LCP, INP, CLS and other performance values remain in current-page memory and are exported only when you choose; they are not uploaded to analytics platforms. Developer API usage buckets are stored by key ID for up to 8 days, without queried IPs. Server key configuration stores digests only.

What this site sees

The host processes the request IP and necessary request metadata for rate limiting. Sampled logs and retention depend on the deployment.

What stays in this browser

Theme, language, the hide-IP setting and query history (the latest 10 successful records per category) stay in this browser. IP and health pages keep up to 100 local observations, removable from their history controls. Security checklist progress is also local. Queried addresses may appear in the browser own history. Clear them through site-data settings. Clearing local data does not remove third-party or hosting records.

Who receives a lookup

Requests depend on the features you open and the target you query.

Place and egress
ipwho.is · IP.SB · ipify
Reputation and usage
Net.Coffee · IPinfo · IP-API · IP2Location · IPPure · proxycheck.io · Scamalytics · DNSBL · Tor exit lists · IPregistry
Outbound links only
IPQualityScore and AbuseIPDB are checked on their own sites after you open the link; the worker only queries them automatically when the deployer configures API keys.
Global latency
Globalping
Domain and IP registration
RDAP(rdap.org / IANA)
Site icons
DuckDuckGo icons proxied through this site
Status endpoints
Providers’ public status pages
WebRTC STUN
Connects to Google and Cloudflare STUN by default. After the check, only public ICE candidates are sent back here for comparison; LAN addresses are omitted.
Direct probes
Egress, AI and site probes are made by your browser directly; the other side can see that connection’s egress IP.

What this site does not do

No login is required. WebRTC checks create data channels without requesting a camera or microphone. The consistency page requests location permission only when you choose to read location. Browser fingerprints are calculated and displayed on the page, not uploaded or saved to history. No cross-site advertising profile is created.

Local diagnostic records

Current-run observations use this tab session storage. Only an explicit save retains a diagnostic snapshot in the browser, up to 20 snapshots. Snapshots may include full egress IPs, sources and measurement times; review exports before sharing. Source-health records retain status and time without queried IPs. Clear data in the diagnostic history and source-health pages.

Authoritative DNS checks

When enabled and started by you, the authoritative service briefly records resolver IPs, query types and any ECS subnet to show the observed resolver path. Sessions expire after 2 minutes; expired records are periodically removed from memory and a restart clears them. They are not written to public share reports.

Share report

Creating a share link stores the submitted egress summary, quality score and its evidence coverage and policy version, plus run statuses, times and numeric summaries. Records expire after 30 days by default (7 or 90 days optional). Raw browser fingerprints, DNS resolver addresses and UDP egress addresses are excluded; real ISP IPs are not silently uploaded.

Related tools and guides