Any query can be disabled above. Disabled or failed checks remain marked as Unconfirmed.
This check inspects the browser tab where this page is open. If Claude Code runs on a remote SSH server or container, this page cannot see that machine’s exit IP or logs.
Viewing Demo Data · Not your real environment
Reading device environment
Results appear as checks complete. Keep this page open.
Lower values mean fewer issues among the checks observed
Waiting to Scan
Click "Run Full Check" to automatically collect and explain your environment signals.
Not scored yet
Scoring coverage 0%
Some checks remain unknown; the index reflects observed items only
How Scoring Works
Checks are grouped: TUN and DNS capture use the highest group score, and unsupported-region IP exits add 50 points with regional access findings combined. A changed IP with the same fingerprint adds 5 points. Routing validation and hosting classification remain independent. The total is capped at 100. Different device and exit timezone offsets add 5 points, increased to 10 when a mainland-China timezone or exit region is involved; Chinese and regional signals add 5 points. Version, zoom and ordinary network changes are informational. Unknown and not-applicable checks are counted separately. This is not a ban probability.
Waiting to collect environment signals
Explains observable environment signals only
Current Network
Not Checked
PUBLIC IP ADDRESS
— . — . — . —
Exit Region
Waiting
ISP / ASN
Waiting
IP Timezone
Waiting
IP geolocation does not prove physical location
Signal Collection Status
0%Waiting
Basic Fields Collected0 / 14
Basic Fields Missing14 item(s)
WebRTC Public IP CheckDisabled
Dual-Stack ExitPending
Domain Split RoutingPending
Extended IP IntelligencePending
Local OS ProbeUnconfirmed
Session Trace ProbeNot Connected
Waiting to load rules
Scan not yet completed
Percentage reflects only how many of the 14 basic fields were collected—not account safety. OS and session trace statuses are listed separately.
Environment Diagnostic Details
Observed signals separated from assumptions
LIVE DIAGNOSTICS
Recommended Next Steps
Actionable steps based on observed signals
Diagnostic Scope & Official Portals
Data sources, coverage boundaries, and official links
ACTION PLAN
What This Page Cannot See
Unobservable data remains unconfirmed
Scope Boundary
Full Abuse Reputation
Single-source network type, proxy flags, and passive port records are integrated. DNS blocklists are checked per RIPE list; private honeypots remain out of scope, and "not listed" does not guarantee a clean IP.
Dedicated DNS & TLS Probes
IPv4, IPv6 and fixed domain probes are queried independently. Random-domain DNS tests are included; TLS fingerprints and routing in every application require separate verification.
Claude Code on Remote Servers
Results from this browser cannot represent a remote CLI. SSH servers, container proxies, or terminal environment variables may route traffic through different exits.
Internal Claude Account Records
Billing, identity verification, email, other device sessions, and request logs cannot be accessed by a web page. The optional helper reads only cookie/storage key metadata, never credential values.
This is an independent diagnostic tool with no access to Anthropic internal risk controls and cannot predict or guarantee account outcomes. It explains observable signals without outputting ban probabilities.
How Public IP Lookup Works & Scope Boundaries
Check the current browser HTTP reference exit IP, country geolocation, ISP, ASN, and 24-hour network stability.
Public IPv4 / IPv6
Geolocation & ASN
Browser History Comparison
Requests are strictly scoped to the endpoints listed for this module; failed lookups are never assumed to be clean.
FAQ
What does this module inspect?
Check the current browser HTTP reference exit IP, country geolocation, ISP, ASN, and 24-hour network stability.
Does an empty or failed result mean no risk?
No. Failures, missing records, rate limits, or ungranted permissions remain unconfirmed, and a single browser probe cannot represent all CLI or app routes.
Does this tool read Claude passwords or session token values?
Never. Network modules only query public IP endpoints and fixed trace probes; the trace module only inspects key names and cookie flags after explicit helper authorization.