Account & Identity Verification Self-Check

Why Claude Suddenly Asks You to Verify

Anthropic doesn't proactively tell you which risk-control layer was triggered. But by observing patterns common to flagged accounts, Claude's risk controls can be split into three independent but overlapping layers of checks:

Key judgment: if the verification page carries a Cloudflare logo or asks for a phone verification code → check network trust and supported region first; if it's Anthropic's own re-login page → Layer 2; if it redirects to withpersona.com → Layer 3. These three types need different fixes — don't try to solve all of them with the same "switch IP" move.

Layer 1 · Network Trust

Anthropic hasn't disclosed its exact risk-control model. CleanIP can only estimate risk based on IP type, ASN, abuse history, proxy/VPN/Tor status, DNS/WebRTC leaks, and geo consistency. The table below is an empirical risk tiering for Claude usage scenarios, not an official Anthropic score:

Beyond IP type, Anthropic also watches 5 dynamic signals:

• Rapid cross-region jumps — the same account appears in Tokyo → San Francisco → Hong Kong within an hour, flagged as account compromise
• IPv4/IPv6 geo conflict — IPv4 shows the US while IPv6 shows Japan, and DNS shows Singapore — all three inconsistent
• DNS egress doesn't match IP egress — using local ISP DNS while traffic goes through a proxy, creating a contradictory resolution path Claude can see
• WebRTC real-IP leak — the browser exposes the local direct-connect address via UDP/STUN, mismatching the HTTP egress
• Dense new account registrations on the same IP range — if a shared egress is repeatedly used for registrations/logins by many people, it raises account security and abuse risk

Go to the Claude AI Detection Center to check all 5 items above in one place.

Layer 2 · Browser Environment Consistency

Even with a clean residential IP, inconsistency at the browser level can trigger risk controls on its own. Anthropic focuses on these 7 dimensions:

The most common pitfall: long-term inconsistency between system language, timezone, DNS/WebRTC, and IP egress makes the browser environment look like a hastily assembled session. Prioritize keeping the same region, same device, and same browser profile stable over time.

Layer 3 · Government ID Verification (Persona)

If the verification page redirects to withpersona.com, that's Anthropic's identity verification flow. Per the official guidance, it's used to prevent abuse, enforce the usage policy, and meet legal obligations.

Photo setup with the highest pass rate

1. Use soft, even natural light (near a window but not backlit); avoid overhead light glare
2. Lay the ID flat on a plain, pattern-free surface, with all four corners visible and no fingers covering it
3. Remove masks, sunglasses, and hats for the selfie, and look straight at the camera
4. A plain background is better — clutter increases face-match failure rates
5. Check the photos before submitting: is the text readable? Does the selfie match the ID? If you can't tell, Persona won't be able to either

On regional restrictions: Anthropic enforces access restrictions based on its officially supported regions, usage policy, terms of service, and applicable law. If the account's creation or usage location is outside a supported region, access may still be restricted or sent to appeal even after completing identity verification. Consider IP geolocation, phone number origin, billing region, and identity information together when judging.

Official Sources & This Article's Scope

This article only translates official public guidance into actionable self-check steps, combined with risk notes from CleanIP's network diagnostics. Claude's actual risk-control thresholds, internal models, and matching rules are not public, so every "high/medium/low" on this page should be read as a triage priority, not a guaranteed outcome.

15-Item Self-Check List

After a risk-control trigger, go through the items below in order — you can usually pinpoint the root cause within 10 minutes:

Playbook After a Trigger

Preventive Setup (Best Practices to Avoid Triggers)

Before creating a new account or settling into long-term stable use, complete these 5 things first — it significantly reduces extra verification caused by network and browser environment issues:

1. Prioritize a stable network — home broadband, a long-term fixed local ISP, or a trusted corporate network beats a public VPN, a shared proxy pool, or a frequently changing VPS egress.Check IPs with a risk score below 30
2. Confirm IPv4 / IPv6 path consistency — if dual-stack consistency can't be guaranteed, consider restricting IPv6; see IPv6 dual-stack risk
3. Keep DNS and HTTP egress consistent — avoid having DNS in one country and HTTP egress in another; use a trusted DoH when necessary and make sure your routing rules cover it.
4. Keep system timezone / language stable — don't switch language and timezone frequently along with your node; long-lived accounts value stability and consistency more.
5. Keep the browser environment simple and stable — use a dedicated Chrome profile and avoid installing many fingerprint/privacy-modifying extensions; more extensions means more anomalous signals.