Is this IP's country on Anthropic's supported list for Claude?

EDGE: READY
More options
What are you checking?
EXAMPLE Checked static example Cache n/a NOT LIVE
IP

8.8.8.8

EXAMPLERUN A LIVE CHECK
ASN
AS15169 · Google LLCgoogle.com
LOCATION
US 5/5 AGREE
IPBot
🇺🇸 US · California, Mountain View
IPinfo
🇺🇸 US · AS15169
GeoLite2
🇺🇸 US
DB-IP
🇺🇸 US · California, Mountain View
Bright Data
🇺🇸 US · California, Mountain View
ROUTE
ANNOUNCED 8.8.8.0/24
IP TYPE
PUBLIC INTERNET INFRASTRUCTURE
ANONYMITY
No direct anonymity evidence observed
ABUSE
No abuse evidence in covered sources
IPJURY SCOREEXPERIMENTAL · NOT A PROBABILITY Not assessed IPJURY VERDICT EXAMPLE

Run a live check for an evidence verdict and experimental interpretation.

Why this result · full calculation

Run a live check. The example is not scored.

    Evidence confidence is not prediction accuracy. A provisional range spans policy outcomes for unanswered questions; it is not a probability interval.

    OPEN FULL EVIDENCE REPORT

    JURY READY

    Enter an address, or check your own connection · the example below is replaced in place

    FULL REPORT IDENTITY · SOURCE MATRIX · SIX-AXIS VERDICT · EVIDENCE RECORD
    01

    IDENTITY

    COORDINATES
    not loaded in static example
    ROUTING
    ROUTE ORIGIN OBSERVED
    PREFIX
    8.8.8.0/24
    TIMEZONE
    America/Los_Angeles
    REVERSE DNS
    not loaded in static example
    STACK
    IPv4
    RANGE
    8.8.8.0 – 8.8.8.255
    REGISTRY
    not loaded in static example
    02

    SOURCE MATRIX

    4 location sources agree at country level · — not covered · W/H withheld

    SIGNALIPBotIPinfoGeoLite2DB-IPIPtoASN
    COUNTRYUSUSUSUS—
    CITYCalifornia, Mountain View——California, Mountain View—
    ASNAS15169AS15169AS15169—AS15169
    PROXYNO————
    VPNW/H————
    TORNO————
    HOSTINGNO————
    ABUSENO————
    03

    SIX-AXIS VERDICT

    NETWORK ROLEHIGH
    Public internet infrastructure

    Service role · anycast context · operator identity

    ANONYMITYMEDIUM
    No direct anonymity evidence observed

    No proxy, VPN, or Tor finding in covered fields

    ABUSE EVIDENCEMEDIUM
    No abuse evidence in covered sources

    This means “not observed,” never “clean”

    GEO CONTEXTLOW
    US · single geolocation estimate

    Country-level context; physical location not proven

    ROUTINGHIGH
    Route origin observed · RPKI state withheld by licence

    Origin ASN · announced prefix · route-origin conflict

    COVERAGEMEDIUM
    6/7 jurors responded

    Named jurors · lineage families · abstentions visible

    04

    EVIDENCE RECORD

    JURORAXISCLAIMCONF.STATUS
    Network identityIPBot networknetwork roleAS15169 · Google LLCHIGHRESPONDED
    Operator and role profileIPBot classificationnetwork rolepublic infrastructureHIGHRESPONDED
    Anonymity signalsIPBot classificationanonymityno direct proxy/VPN/Tor evidenceMEDIUMRESPONDED
    Direct threat evidenceIPBot evidenceabuseno direct record in covered evidenceMEDIUMRESPONDED
    REPORT ipjury.com/check/8.8.8.8 EXPERIMENTAL INDEX
    TERMINAL curl ipjury.com/8.8.8.8 irm ipjury.com/8.8.8.8
    IPJURY.COM · EVIDENCE, NOT AN ENTERTAINMENT SCORE

    IPJury uses the IP2Location LITE database for IP geolocation. This product includes GeoLite Data created by MaxMind, available from https://www.maxmind.com. IP Geolocation by DB-IP. Full source credits: source register.

    05

    READING ANTHROPIC'S TWO COUNTRY LISTS

    Is the country this IP is located in on Anthropic’s supported list?

    IPJury takes the country its location sources agree on and compares it with Anthropic’s two published lists, one for commercial API access and one for Claude.ai, giving the retrieval date. A disputed or missing country, a country listed only with regional exceptions, or an expired copy of the list produces no reading rather than a guess.

    Evidence scope and register licence-review dates — not live lookup dates
    SourceRegister review
    Anthropic supported countries and regions (Claude API, Claude.ai)
    IP2Location LITE DB11 (via IPBot)

    Source availability depends on the current deployment and each returned record. These review dates do not establish when a particular IP was observed. Method axis-scope-2026-09-15 · Score ipjury-score-v3.

    Anthropic publishes where it offers Claude as two lists on one page: countries, regions and territories with commercial API access, and those with Claude.ai access. This check reads those lists against the country IPJury's location sources agree on for an address. It is a dated comparison of two records, not a test of whether a connection will be accepted.

    What the reading says, word for word

    For each list the reading is one sentence: a country is or is not on Anthropic's supported list for the Claude API or for Claude.ai, with the date the list was retrieved, followed by whether the location sources agree or rest on a single estimate. The two lists stay two claims. They are identical as retrieved on 2026-09-17, and if they ever differ the reading reports each separately rather than merging them into one answer.

    The country is the geolocation verdict of the ordinary IPJury record. It is not the registration country, not the country of the account, and not the country a payment card was issued in.

    When there is no reading

    A requested reading is always present, and it says why when it withholds a claim:

    • geolocation_disputed — the location sources name different countries. IPJury does not pick the majority for a list claim, because a wrong country would become a wrong statement about Anthropic's list.
    • no_country — no location source returned a country for the address.
    • partial_country — the country is listed with regional exceptions. Anthropic lists Ukraine "except Crimea, Donetsk, Kherson, Luhansk, and Zaporizhzhia regions"; a country-level location cannot settle which side of that line an address falls on.
    • policy_expired — IPJury's copy of the list has passed its review-by date and is not restated until it is reviewed again.
    • not_applicable and stale_record — a private or reserved address has no country, and a stale fallback record is too old to compare.

    What the list itself does not cover

    Anthropic's page also states that it may decline to serve entities whose majority ownership is attributable to nations other than those listed. That is a rule about ownership, and nothing about an IP address can show it. The same is true of account verification, age requirements, payment, device and behaviour signals. An address in a listed country is compatible with every one of those checks failing, and an address outside the list says nothing about who is using it.

    Using it well

    Treat the reading as a question to check, not a conclusion. If a hosted server, proxy or VPN exit is involved, the address's country and the user's country can differ, and a provider's terms may treat that difference as the user's responsibility. Read Anthropic's current page before relying on the list, and compare the reading with where the account holder actually is. The same reading is available from the API with service=claude.

    06

    A NUMBER NEEDS ITS EVIDENCE

    IPJury keeps network type, anonymity, abuse, location, routing and coverage separate. Its optional experimental index explains a published policy over those facts; it never replaces the named evidence verdict or conceals missing information.

    MYSTERY SCORE MODEL
    83/100

    What does 83 measure? Who supplied it? Is hosting being treated as abuse? Did one heuristic outweigh a direct record? A number cannot tell you that two of its sources flatly contradicted each other.

    • Cross-axis averaging
    • Hidden source lineage
    • Missing source treated as “false”
    • Disagreement averaged away
    • Platform outcome implied
    EVIDENCE + EXPLAINED INTERPRETATION
    BANDDISPUTED RULEsource-conflict ROLEhosting ANONYMITYno direct evidence ABUSEno record observed GEOcountry disputed ROUTINGorigin observed COVERAGE6/7 responded

    One rule read one axis and named the state. The axes it did not read stay beside it. “Disputed” and “too little coverage to say” are answers a single number cannot express.

    07

    THE FIVE RULES OF EVIDENCE

    [ READ FULL METHOD ]
    1. 01

      Vote only on the same axis

      A proxy flag, an abuse report, a hosting role, and a city estimate are not interchangeable votes.

    2. 02

      Direct evidence outranks a prior

      An exact-IP record is different from an inference based on the ASN, prefix, or network category.

    3. 03

      Deduplicate source lineage

      Three websites backed by one upstream database do not become three independent evidence families.

    4. 04

      Let jurors abstain

      Timeout, no IPv6 coverage, disabled license, or missing record is shown—not silently converted to “no.”

    5. 05

      Explain dissent

      CGNAT, anycast, reassignment, data age, and route context can all produce legitimate disagreement.

    09

    QUESTIONS THE SCORE CANNOT ANSWER

    Does a listed country mean Claude will accept my connection?

    No. The reading says only whether the country IPJury's location sources agree on appears on Anthropic's published list. Account checks, payment, device and behaviour are decided by Anthropic and are not visible to an IP lookup.

    Why are there two Claude readings instead of one?

    Anthropic publishes one list for commercial API access and another for Claude.ai. IPJury keeps them as separate products and never merges them, so a difference between the lists would stay visible.

    Why is there no reading for an address in Ukraine?

    Anthropic lists Ukraine except for named regions. A country-level location cannot tell which side of that line an address is on, so the reading is withheld with the reason partial_country instead of guessing.

    How current is IPJury's copy of Anthropic's list?

    Each reading carries the retrieval date and a review-by date. After the review-by date the reading is withheld until the list is reviewed again; Anthropic's own page is always the authority.

    IPJURY // RECORD

    Methodology