What it does
DNS-OARC’s Check My DNS uses dynamically delegated names to inspect resolver behavior, with browser test suites and a separate local command-line client.
Check My DNS investigates the resolver path used by the client, rather than looking up the published records of an arbitrary domain. DNS-OARC’s current overview describes version 3 with grouped test suites and region selection between Stockholm and California. A separate local CLI lets an operator choose a resolver explicitly. The browser page requires JavaScript and scripts from jsDelivr; DNS-OARC member access is needed for raw test data on its analysis servers. The retained development-endpoint capture at cmdns.dev.dns-oarc.net carried a race/deadlock notice updated on September 17, 2026. That notice does not establish the current main service’s behavior or a fix there.
Strengths
- Browser test suites and selectable regions
- Separate CLI for an explicit resolver
Watch out for
- Browser requires JavaScript and external scripts
- Raw analysis-server data requires DNS-OARC member access
Sources
- Check My DNS (Oct 26, 2026)
- Check My DNS current browser requirements (Oct 26, 2026)
- DNS-OARC V3 suites, endpoints and raw-data access (Oct 26, 2026)