Egress routing and expected rules
Inspect browser-observed egress by website, DNS and CDN source. Compare this run with expected countries, addresses or groups; different exits alone do not prove correct routing.
Using and interpreting this tool
Confirm the target and measurement point, then start the checks you need. Results retain sources, observation times and missing-data reasons. Traffic-intensive checks require a separate start.
After changing one setting, start a fresh run and compare A/B snapshots in history. Unknown, unconfigured and inapplicable do not mean passed.
Related tools and guides
Live measurements run in your browser after JavaScript loads. This introduction contains no visitor detection results.