Routing rules must cover the X side too
A common setup sends Grok's own domain through a proxy while X domains stay on the direct route. The page then loads, but sign-in stalls or loops. Check both sides when reviewing proxy and domain-split rules.
Grok Check: Dual-Domain Routing & IP Risk
Check Grok's public paths across grok.com and x.com, compare IPv4/IPv6 exits, and review region, ASN, and proxy signals when access, 403, or verification behaves differently.
Locate region
- Parse IP
- Locate region
- Match ASN
- Check proxy / VPN / Tor
- Check risk lists
- Summarize AI access
Grok access diagnosis
Live checkChecking
Checking
- Public endpoint reachability
- Checking
- Measured from this browser
- Access conditions reference
- Checking
- Reference based on public information
- Exit network type
- Checking
- Current exit profile
- Risk note
- Checking
- Based on exit network signals
Current exit IPCheckingCollecting network profile…
AI Availability
Live check on this networkChecking
Checking
Checking
Checking
Checking
How to read this check
Grok Needs Two Domain Paths at Once
Grok is tied to the X account system, and page loading and sign-in can travel through different domains. Grok works only when both sides are reachable.
The exit region decides reachability
Grok requires an exit that can reach its public resources. The region, ASN, and network type of the current exit directly affect the result — the opposite direction from services designed for direct domestic access.
Data-center exits attract more verification
Data-center and proxy attributes raise the chance of human-verification prompts. When verification repeats, review network type and proxy risk first, then account state. A network check cannot predict account decisions.