First pass
Compare DNS answers before digging into the rest of the network.
Internet diagnostics
Start with DNS, then branch into speed, public IP, and regional checks when the path gets weird.
First pass
Compare DNS answers before digging into the rest of the network.
Next checks
Confirm browser-to-edge speed and the public address your traffic uses.
Primary launcher
One query fans out across every configured region.
Advanced query
`ANY` does not mean “return everything.” Many resolvers and authoritative servers intentionally minimize or reshape `ANY` responses, so results can be partial and inconsistent across regions.
Use it for exploratory comparison only, not as a reliable inventory of all record types.
Response
Run a lookup to populate the map and per-region results.
Map
Matching answers share a marker color. Click a map label to focus the table below on that region.
Table
Exact returned records for each region, including timing.
| Region | Status | Answer | Time |
|---|---|---|---|
| Choose a name, record type, and resolver to populate the global results view. | |||
Tools
Start with the live tools, then use the planned command-style checks as the roadmap fills in.
Troubleshooting paths
Plain starting points for the most common internet mysteries.
Learn
Short explanations that make each result easier to interpret in the moment.
DNS
Resolvers, caches, geolocation, and authoritative routing can all make two regions see different records.
Connectivity
A fast edge test with failing DNS points to naming or resolver behavior, not raw throughput.
Identity
VPNs, carrier NAT, office gateways, and cloud workspaces can change the address services see.
Articles
Practical notes to turn common failures into repeatable checks.