Online toolsResearch Lab · Paste and useResearch Lab ↗
JSON formatterJSONMermaid diagramsMermaidAI cost comparisonAI costsMarkdown to WeChatWeChatClaude checkClaude
Browser network checkHelp
NETWORK CHECK

Claude network & environment check

Inspect your browser’s exit and exposed signals to Claude.

Checks run only after you click Start

Start also runs the DNS check. Your browser contacts Claude / Cloudflare, IPQuery, the official status page and our DNS service; WebRTC probes Cloudflare STUN. These services see network addresses. DNS query records expire after 3 minutes; device fingerprints stay in this page.

Official service updates

Open status page ↗

Reads official announcements after starting, separately from local connectivity.

This browser → Claude

Awaiting target measurement
  1. 01 · ORIGIN

    Your browser

    Requests start when you click

    HTTP probes originate on this device
  2. 02 · TRANSIT

    Hops are not observable

    Routers / proxies / ISP

    This page cannot run traceroute
  3. 03 · TARGET EDGE

    claude.ai

    Source IP seen
    —
    IP region / edge
    — / —
    Edge protocol
    —
    Never replaced by this site’s exit
  4. 04 · APPLICATION

    Anthropic

    Internal route and account status unseen

    No login, chat or API call tested

Arrows show request direction, not a measured traceroute. The edge is a Cloudflare location, not an Anthropic server location. These unauthenticated probes do not establish the paths of logged-in pages, APIs or Claude Code.

Exposed signals & differences to review

Evidence-based interpretation

Claude exit region

Not established

Uses the region returned by claude.ai, never a fallback site or IP database. Check the official list for changes.

Web routing

Not established

Compares Claude with other measured sites. Domain routing, load balancing or dual-stack networking can explain differences.

Additional WebRTC exits

Awaiting main scan

STUN separately gathers browser candidates. A different public exit needs review; it does not prove Anthropic collected it or that a leak occurred.

DNS resolver exits

Included in Start check

Tests resolvers for our random domains, not the actual DNS path of claude.ai. Missing records can reflect test-service or network failure.

Device / exit timezone

Not established

Compares local settings with third-party geolocation of the Claude exit. Travel, settings, DST and database errors can explain differences; this is not an account-risk verdict.

Claude IP attributes

Not established

IPQuery labels describe the network. Negative or missing labels do not establish a residential IP, absence of abuse history or account safety.

What is visible, and what does it say about account restrictions?
Visible to the connection endpoint
Source IP, protocol and request headers. The diagram shows fields returned by the target, not its full logs or internal security signals.
Readable by page scripts
Timezone, language, screen and some device features. Local measurements do not prove Anthropic collected a particular field.
Separate probe observations
WebRTC candidates and test-domain resolvers. These are not data confirmed as sent to Anthropic by the Claude HTTP probe.

Anthropic describes using IP and other signals for regional checks and collecting device/connection information. Published suspension reasons also include policy or terms violations and registration from unsupported locations. Network checks cannot predict bans or inspect your account; use the official appeal process for restrictions.

Sources and region list checked: 2026-10-27

Request evidence by target

Measured in your browser
TargetObserved exit IPRegion / edgeHTTP elapsedResult
claude.ai ↗———Not run
GrowthYoung ↗———Not run
Cloudflare ↗———Not run
claude.com ↗———Not run
anthropic.com ↗———Not run

Elapsed time includes the HTTP request, not ping. An edge response does not prove login or model access; CORS failure does not prove Claude is down. Click a target to inspect its diagnostic endpoint manually. Local Claude Code proxy settings cannot be read by this page.

IP attribute details

IPQuery ↗
Region / city
—
ASN
—
ISP / organization
—
Hosting IP
Unknown
Mobile network
Unknown
VPN
Unknown
Proxy
Unknown
Tor
Unknown
IPQuery indicator
Unknown · Not a Claude score
Abuse / crawler records
Not supplied by this provider
Claude region list
Unknown

Geolocation is approximate. “Not listed” does not guarantee safety; non-hosting is not proof of residential or native IP.

Official region list ↗ · 2026-10-27 checked; exit-region comparison only, not account eligibility.

WebRTC / UDP

Not run

Check for other network exits exposed by the browser

Candidate addressTypeProtocol
Not run

No candidates may reflect mDNS masking, blocked UDP or browser restrictions, not “no leak”. Different exits may be intentional routing. No camera or microphone permission is requested.

DNS resolver exits

First-party test · v1

Use four random test names to observe which resolvers query on behalf of this browser.

Runs with Start check above
Resolver egress IPASNOrganization / registrationQuery types
Use Start check above to see measured records

A different web exit does not prove a leak: public DNS, DoH and forwarding can explain differences. This samples browser requests, not all system DNS, and does not test hijacking. A / AAAA describe queries, not resolver transport.

Session records expire from server memory after 3 minutes. ASN attribution is cached for 1 hour; registration country is not physical location. Rate-limited attribution may arrive later. Team Cymru ↗

Device & regional signals

Computed in this page

These are browser-readable signals. Chinese language, fonts or timezone are not evidence of account risk or a person’s location.

Timezone
—
UTC offset
—
Claude exit timezone
—
Languages
—
Intl locale
—
CJK fonts (approximate)
—
Platform / screen
—
Cookies / session storage
—
WebGL renderer
Unknown
Canvas fingerprint
Unknown
WebGL parameter fingerprint
Unknown
Emoji rendering fingerprint
Unknown
User-Agent

Unknown

Exit history 0 / 20

Saved only when opted in, in this browser: at most 20 scans for 30 days. Fingerprints are not stored. Clearing cannot be undone.

No saved records. Results stay in the current page by default.

Check the network and browser environment used for Claude

Start with the measured exit to claude.ai, then review the edge, regional support, web/WebRTC exit differences and device settings. Probes originate in your browser. Transit hops, application internals and account status remain unobserved; no ban probability is provided.

Back to workspace ↑

How to use it

  1. Use Start check above to run network, WebRTC and DNS checks together. Stop scan cancels all of them. No sign-in or Claude API key is needed.
  2. Read the browser-to-Claude diagram and differences to review, then inspect raw evidence. DNS results update in the same run; our test-domain observations cannot establish the actual DNS path of claude.ai.
  3. Optionally reveal full IPs, copy or export JSON, and opt into up to 20 exit-history entries on this device. Clear history at any time.

Example

claude.ai → edge response → exit IP → third-party IP attributes
WebRTC → public candidates → compare with Claude exit
DNS → random test names → authoritative resolver-exit observations

This illustrates request direction and measurement scope, not a hop-by-hop traceroute. The edge is not an Anthropic server location. Missing target evidence stays unknown and is never replaced by another site’s exit.

Questions and limits

Does this predict whether Claude will ban an account?

No. IPQuery supplies third-party IP reputation, not Claude risk scores. Language, fonts, timezone and emoji fingerprints are informational, not ban evidence. Residential/native IP or abuse records are not inferred when the provider does not supply them.

What are the DNS and WebRTC limits?

Our authoritative DNS service observes recursive exits for four random names and expires session records after three minutes. This samples browser requests; different DNS and web exits do not prove leakage. WebRTC uses Cloudflare public STUN. No public candidate may reflect browser restrictions, not absence of leaks. Different exits may be intentional routing.

How are requests and privacy handled?

Checks require a click and can be stopped: up to five exit probes, one official-status request, one STUN probe, two IP lookups and one DNS session with four random names. IP lookups are spaced by at least 10 seconds and cached for 15 minutes; scans have a 60-second cooldown. Refused or rate-limited sources are paused without automatic retries. Device signals are not uploaded; IPs are hidden by default and exports follow that setting.

Network tests contact the listed providers after you start. Diagnostic results and optional history stay in your browser.