Check Claude account risk

A browser environment fingerprint engine for scanning Claude runtime signals, regional profiles, and account environment risk

Claude environment check
Claude account risk
Runtime environment scan
Click to generate a Claude environment risk report
--
Waiting
Evaluated signals --
Waiting

Detected signals

29 items shown
System timezone
Waiting
--
Browser language
Waiting
--
Language variant
Waiting
--
Regional fonts
Waiting
--
Vendor fonts
Waiting
--
Browser region traits
Waiting
--
Device region traits
Waiting
--
Intl locale
Waiting
--
Date/number format
Waiting
--
Timezone offset
Waiting
--
Emoji rendering style
Waiting
--
IP country
Waiting
--
WebRTC egress
Waiting
--
Egress consistency
Waiting
--
WebRTC IPv6 egress
Waiting
--
IP vs system timezone
Waiting
--
IP address
Waiting
--
IP type (heuristic)
Waiting
--
Direct IPv6 egress
Waiting
--
claude.ai edge reachability
Waiting
--
Anthropic site reachability
Waiting
--
API endpoint reachability
Waiting
--
Anthropic endpoint summary
Waiting
--
IP location
Waiting
--
ASN
Waiting
--
Network organization
Waiting
--
Browser/app environment
Waiting
--
Device/system signals
Waiting
--
Operating system
Waiting
--

Network layer: on. During the check your browser queries ipwho.is for your public IP, gathers WebRTC candidates through STUN, and contacts Anthropic-related endpoints and an IPv6 probe directly; requests go directly to third parties and this site does not receive or store the results.

Detection Logic

How CheckCC works

CheckCC breaks the Claude runtime environment into verifiable browser signals: language, timezone, device, and localization settings.

01

Environment fingerprint

System timezone, UTC offset, browser language, Intl locale, and date/number formats.

02

Network profile

Optionally, the browser connects directly to a third-party IP geolocation service and an IPv6 lookup service for the IP country, ASN, network organization, and dual-stack egress. Server request headers are not read.

03

Risk scoring

Weighted regional conflicts across browser and network signals, with evaluation coverage shown separately.

Risk Signals

Which Claude risk signals does CheckCC inspect?

This site turns the network layer on by default: during a check, your browser connects directly to third-party IP geolocation, STUN, Anthropic-related endpoints, and an IPv6 lookup service, and those services see your IP. You can turn it off in the check settings to use browser signals only. A failed lookup does not inflate the score, and unevaluated signals are labeled and excluded from the total.

Regional profile consistency

1

Correlate browser language, Intl locale, system timezone, and localization settings to detect obvious regional conflicts.

Browser identity profile

2

Combine browser language, UA hints, and Intl configuration to check whether browser identity signals agree with each other.

Device environment fingerprint

3

Use fonts, emoji rendering, timezone offset, and other browser traits to check consistency with regional profiles. No hardware identifiers are read.

Application container detection

4

Identify WeChat, QQ, UC, Quark, and other Chinese browser or in-app WebView user-agent markers as weak regional signals.

Device brand signals

5

Detect HarmonyOS, Huawei, Honor, Xiaomi, OPPO, vivo, and similar device-brand clues as weak regional signals.

Network exit trust

6

Optionally checks the IP country, ASN, and network organization to sanity-check network egress. Server request headers are not read, and VPNs or proxies are not detected.

Claude endpoint reachability

7

Optionally contacts claude.ai's Cloudflare edge diagnostic path, www.anthropic.com, and api.anthropic.com directly from the browser. Only completion and latency are observed; response content is not read. The claude.ai app is protected by a cross-origin policy and cannot be probed directly.

Dual-stack egress check

8

Optionally reads the direct IPv6 exit from an IPv6-only lookup service and compares it with the HTTP exit in the same address family. A different family is not treated as a leak.

Egress type heuristic

9

Uses ASN and network organization names to label residential broadband, carrier, datacenter, or unknown egress. This is context only and never affects the score.

Key regions covered

Mainland China

High risk

Checks Simplified Chinese traits, UTC+8 timezone, Chinese fonts, and the optional network-exit country.

Hong Kong

Focused check

Auto detection identifies Hong Kong from Traditional Chinese, timezone, and browser-language traits and uses a separate profile; with the network layer on, Hong Kong IPs are checked separately.

Russia

High risk

Checks Russian language traits, Russia timezone, and the optional network-exit country.

Privacy

How does CheckCC protect your privacy?

CheckCC only analyzes technical signals needed for environment risk evaluation. It does not require Claude login and does not read sensitive account content.

Will my Claude account data be uploaded?

No. CheckCC does not require Claude login and does not read or store account names, passwords, cookies, or other sensitive data.

Are detection results saved?

No personal detection results are saved. The check is only used for the current environment risk evaluation and is not linked to your Claude account.

Does the website use analytics?

The current version does not load third-party analytics scripts and does not collect Claude account data or report content.

Which signals are analyzed?

CheckCC mainly analyzes browser environment, language, timezone, regional profile, and device fingerprint consistency. With the network layer on, the browser also queries a third-party IP geolocation service directly for the exit IP, country, ASN, and network organization, connects directly to STUN to collect WebRTC candidates, and requests claude.ai's edge diagnostic path, www.anthropic.com, api.anthropic.com, and an IPv6 lookup service. Endpoint probes do not read response content.

Claude environment and account risk FAQ

How do I use CheckCC?

Open the page and click "Check Claude environment now". You don't need to log in to Claude or install anything. The check runs in your browser and, within a few seconds, shows a 0–100 environment risk score, which signals matched, and how much of the check could be evaluated. To add the IP country, WebRTC egress, and Claude endpoint reachability, turn on the network layer in the check settings and run it again.

Is the result Anthropic's official decision?

No. CheckCC is an open-source heuristic tool. It estimates regional conflicts only from signals the browser can read, doesn't call any Anthropic API, and can't see your account's real status. A high score doesn't mean your account will be restricted, and a low score doesn't mean it's safe: the platform also weighs things the tool can't see, such as sign-in behavior and payment details.

Why do timezone and browser language affect the risk signals?

Timezone and language are the most visible regional clues a browser exposes. The system timezone, preferred browser language, and Intl locale usually point to the same region; if they clearly disagree with the country of your exit IP, that is a regional-conflict signal. CheckCC groups these signals so each group counts once, at its largest weight, instead of adding up the same evidence twice.

Why can a Claude account be restricted?

Common reasons include accessing or signing up from a country or region Anthropic doesn't support, using a payment method from a different region, switching network exits frequently, and violating the usage policy. Anthropic's list of supported regions and its usage policy are the authority here; CheckCC only covers the part of your environment that a browser can observe.

How does Claude's risk system evaluate an environment?

Anthropic doesn't publish its rules. Systems like this usually weigh several signals together, such as IP location, payment details, browser environment, and account behavior, rather than a single IP address. CheckCC can only check whether your browser environment is consistent, to help you spot obvious conflicts. It can't reproduce or predict the platform's decision.

Can a restricted account be recovered?

You can appeal through Anthropic's official support channels and provide the account details they ask for. Before appealing, CheckCC can show whether your current environment has obvious conflicts, so you can describe the situation accurately. Anthropic makes the decision; CheckCC can't lift a restriction or predict whether an appeal will succeed.

Will I get a refund after an account restriction?

That depends on your subscription status, payment channel, and Anthropic's policy at the time, so ask through official support. Subscriptions bought through the App Store or Google Play follow that store's refund process. CheckCC doesn't handle payments and can't see your subscription.

What should I check before creating a Claude account?

Make sure your country or region is on Anthropic's supported list, and use a phone number and payment method that match your own details. Before signing up, CheckCC can show whether your browser's timezone, language, and exit agree. Don't fake your timezone, language, or location to get around regional restrictions; doing so can itself violate the usage policy.

What should I check before applying for the Claude API?

The API is also only available in supported countries and regions, and billing details need to match the organization's location. CheckCC's network layer shows the country of your current exit IP and whether api.anthropic.com is reachable. Reachability only means the network gets through, not that the account or region is eligible.

Does Claude Code relate to account environment risk?

Claude Code uses the same Claude account or API quota, so the same regional requirements apply to the account and organization. CheckCC checks your browser, but Claude Code runs in a terminal, and its network exit can differ; for example, a system proxy may apply to some programs and not others. In that case the browser result doesn't describe Claude Code's exit.

Does CheckCC collect my data?

By default the check reads environment signals only inside your browser. Nothing is uploaded, and your Claude account, cookies, and chats are never read. With the network layer on, your browser contacts a third-party IP lookup service, a STUN server, and Anthropic endpoints directly, and those services see your public IP; this site's server doesn't receive, forward, or store the results. The code is open source, so you can review it or host it yourself.