Claude IP check
Which IP claude.ai sees, whether that region is supported by Anthropic, and whether it looks like a datacenter or proxy.When a proxy routes by domain, the IP that opened this site may not be the one Claude sees. The Claude card below comes straight from claude.ai. Claude Code runs in a terminal, so check it separately: curl -sL ipjudge.org/en/cc | bash.
Claude readiness
A checklist, not a second score; region is a hard rule, the rest are common risk signals — Anthropic doesn’t publish its rules · howExits for Anthropic domains
Checking your network exit…
Start hereThe first suggested action appears when checks finish.Can you use these AI platforms?
By each company’s official regions + the exit you actually reach them fromNext step
Based on what your exit actually showsHow to fix
Most serious first · what happened → how to fix itWhen all checks finish, issues and fixes are listed here, most serious first.
Who sees which of your IPs
Grouped by exitShown when the checks finish.
IP details
The exit that opened this siteLooking up…
Browser and connection checks
13 checks · tap for details · run only between your browser and our probeShow all 13 checks
Proxies often route by domain: the IP that opened this site is not necessarily the one Claude or ChatGPT sees. The first two checks ask claude.ai and chatgpt.com directly.
Datacenter vs residential IP: what actually differs
IP type is one lead to check, not a published Anthropic rule — the official criteria are not public. Community reports show datacenter and cloud ranges being asked to verify more often, and consumer-ISP residential addresses less often. Switching to residential does not guarantee anything; it only removes IP type as a variable. Region still has to be on the supported list.
What the datacenter / residential difference actually is →FAQ
Where is Claude not available?
Per Anthropic’s official list (checked 30 September 2026), mainland China, Hong Kong and Macau are not supported; Taiwan, Japan, Singapore and the US are. Claude judges your region by the exit you connect from. See the country table.
The browser looks fine, so why does Claude keep asking me to verify?
Usually one of three things: a datacenter exit, an account hopping between exits, or a browser time zone / language that doesn’t match the exit. The “How to fix” list shows which applies to you.
Why check Claude Code separately?
Claude Code runs in a terminal and only honours variables like HTTPS_PROXY. Many proxy apps use “system proxy” mode, which browsers follow and terminals ignore — so Claude Code goes direct. Run curl -sL ipjudge.org/en/cc | bash. More on the Claude Code page.
Further reading
Related guides
These go deeper on the problems aboveWhich exit do Claude Code / Codex use?
A clean browser doesn’t mean a clean terminal. Run this in your terminal:
curl -sL ipjudge.org/en/cc | bash
Is the residential IP you bought really a home line?
The check looks at the IP itself, not the seller’s description: type, native or broadcast, blocklists and proxy flags, each with its evidence. For several IPs:
curl -s ipjudge.org/en/ip/THE_IP