CLAUDE

Claude AI IP Risk Check

Evaluate your current network for Claude sign-in and usage scenarios: regional compliance, VPN / proxy / Tor, datacenter / residential attributes, DNS / WebRTC / IPv6 leaks, browser consistency, and account security signals.

Official status unknown

Click start to generate the Claude risk report

This page does not auto-detect. After you click start, it will check IP intelligence, egress path, Claude reachability, and DNS/WebRTC leaks in sequence.

Regional compliancePending

After you click start, we'll check whether the egress country is within Claude.ai's supported range.

VPN / ProxyPending

After you click start, we'll query VPN, proxy, Tor, and residential proxy signals.

Network identityPending

After you click start, we'll identify residential, mobile, datacenter, cloud, or public infrastructure networks.

Path consistencyPending

After you click start, we'll compare the HTTP, browser IPv4, and IPv6 egress paths.

VPN & Proxy Deep Inspection

Pending

Commercial VPN Detection

Shared VPN egress has a complex history and is more likely to trigger extra verification during account sign-in.Query runs after you click start.

Proxy Service Detection

HTTP/SOCKS proxies and transparent proxies increase the likelihood of account verification.Query runs after you click start.

Residential Proxy Detection

A residential proxy is not home broadband — it's typically a sublet or pooled residential egress.Query runs after you click start.

Tor / Relay Detection

Anonymous relays and Tor exits are very high risk for Claude sign-in.Query runs after you click start.

IDC / Hosting Detection

Datacenters, cloud servers, and public CDN networks are better suited to API services than regular account sign-in.Query runs after you click start.

Abuse & Reputation History

Abuse history, DNSBL listings, or risk scores affect risk assessment for sign-in, billing, and session stability.Query runs after you click start.

Egress Path Consistency

HTTP egress

Pending

Browser IPv4

Pending

Browser IPv6

Pending

HTTP ↔ IPv4Pending

After you click start, we'll compare the server-side egress with browser IPv4.

IPv6 RoutingPending

After you click start, we'll check whether IPv6 egress is routed separately.

DNS EgressPending

After you click start, we'll run a DNS leak check.

WebRTC UDPPending

After you click start, we'll run a WebRTC leak check.

Timezone ↔ IPPending

After you click start, we'll compare the system timezone with the IP region.

Reachability & Device Consistency

claude.aiPending

api.anthropic.comPending

System timezone
Browser language: -
Platform / Browser: /
Cookie: Disabled
WebGL: -

Further Investigation

Claude Risk Policy Basis

Regional Compliance Is a Hard Prerequisite

The official supported-regions page lists countries/regions available for Claude.ai and the commercial API separately. Detection should first confirm whether the IP's located country is within Claude.ai's supported range.

When the IP is located in an unsupported region, it should be treated as high risk even without a VPN, proxy, or abuse record hit.
Cross-border IDC, broadcast IPs, or database location drift can make the account's region inconsistent with the actual usage environment.
This page judges country code, timezone, ASN, and egress path together, rather than relying on a single IP geolocation database.

Official supported regions

Policy Violations Can Trigger Restriction, Suspension, or Termination

Anthropic's transparency and safety documentation notes that when a user is found to violate the usage policy, terms of service, or supported-regions policy, enforcement actions such as warnings, suspension, or termination may follow.

This kind of enforcement typically looks beyond content alone, also weighing account, region, access environment, and security signals.
Shared proxies, unusual regional jumps, abuse history, or high-risk networks make account security review more likely to be triggered.
The VPN/Proxy/Tor detection, abuse history, and path consistency in this report are designed around exactly these risk signals.

Official transparency report

Enterprise VPN and Anonymous VPN Are Different Signals

Claude Enterprise's IP allowlisting documentation shows that organizations can submit CIDRs for offices, VPN egress points, and other approved access points, so organizational access comes only from trusted network locations.

An enterprise VPN is a controlled, auditable, registered egress; anonymous VPNs or proxy pools usually lack this context.
If a company enables an allowlist, unregistered IPs are denied access — missing a required CIDR can lock users out of the organization.
So a "VPN hit" doesn't necessarily mean a violation, but shared VPNs, proxy pools, and unstable origins significantly raise the risk.

Official IP allowlisting

Session Location Is Used for Account Security

Claude's active sessions page shows device, browser, IP-based approximate location, and last-updated time, helping users spot unfamiliar sessions and terminate suspicious logins.

An account that frequently shows up from unfamiliar countries, unfamiliar devices, or unusual browser combinations is more likely to be flagged for account security anomalies.
IP location, system timezone, browser language, and WebGL/UA fingerprint should stay as consistent as possible.
If an unrecognized location appears in active sessions, the official guidance is to terminate that session and consider changing your password.

Official session management

Claude AI IP Risk Check

Click start to generate the Claude risk report

VPN & Proxy Deep Inspection

Commercial VPN Detection

Proxy Service Detection

Residential Proxy Detection

Tor / Relay Detection

IDC / Hosting Detection

Abuse & Reputation History

Egress Path Consistency

Reachability & Device Consistency

Further Investigation

Claude Risk Policy Basis

Regional Compliance Is a Hard Prerequisite

Policy Violations Can Trigger Restriction, Suspension, or Termination

Enterprise VPN and Anonymous VPN Are Different Signals

Session Location Is Used for Account Security

Egress IP History