Four dimensions of the Grok environment score
| Dimension | Scored signals | Does not establish |
|---|---|---|
| Exit identity | Network type, role and evidence confidence | Exclusive residential status or platform acceptance |
| Geolocation agreement | Geolocation sources and ASN country consistency | Official xAI regional eligibility |
| Exit reputation | IP2Proxy and Spamhaus DROP records | Account suspension or successful access |
| Environment consistency | Dual-stack profiles, same-family WebRTC exits and timezone offset | The complete session route, DNS safety or physical location |
Score bands and missing evidence
85-100 means fewer deductions among observed signals, 70-84 calls for attention, and below 70 calls for review. These bands do not establish residential status, eligibility or suspension probability.
Missing dimensions are excluded and the remaining weights are normalized. A high score does not mean every check completed. Official regional eligibility, DNS and language are shown separately and are not scored.
This page reads the grok.com routing exit but does not measure the x.com exit. It cannot report their consistency. Public-resource responses do not establish login, chat, image generation or API credential validity.
Investigate Grok access using observed evidence
Check official status
Review status and sync time. For an incident, check its scope; unknown or stale data is not a healthy result. A healthy status alone does not establish a local network cause.
Separate region, connectivity and account notices
Check each product’s regional coverage, browser connection result and actual error. Network scores do not replace regional, subscription or account eligibility checks.
Compare network paths
Compare IPv4 and IPv6 WebRTC candidates against same-family exits. A different DNS resolver address may reflect recursive resolution and does not alone prove a leak.
Change one variable at a time
Record the error and test time. Try a clean browser session or another network separately. Prioritize causes that reproduce consistently; do not disable IPv6 or change timezone just to raise a score.
Evaluate IPv4 and IPv6 dual-stack paths separately
A single device may have IPv4 and IPv6 exits in completely different datacenters, regions, or networks. When one protocol stack works while the other is restricted, browsers may trigger unexpected fallback delays or connection drops.
Compare public exits, WebRTC candidates, and DNS paths across both address families to ensure routing consistency and prevent cross-stack drift from causing validation loops.
Network check results do not replace account verdicts
Sources and evidence limits
Sources below support the stated technical or policy boundary. Diagnostic comparisons in this guide remain observations, not account verdicts.
- xAI Service and Regional GuidelinesxAI · Official guidance
- Spamhaus Public Network Reputation DataThe Spamhaus Project · Data limitation