About MyWebDNS

A public DNS observatory built around transparent evidence.

MyWebDNS exists to make one diagnostic question easier: what answer did each configured resolver path return, and what context do you need to interpret it responsibly?

Project principles

Clarity wins over spectacle.

Location must be earned

A map marker comes from configured probe coordinates. A public resolver IP is not presented as if it has one fixed country.

States must stay distinct

No data, NXDOMAIN, timeout and failure each mean something different. The interface keeps that difference readable.

Evidence needs limits

Agreement among sampled probes is useful, but it is never described as proof of every network or end user.

System shape

A central service with deployable probe workers.

The .NET application coordinates browser requests, query validation, caching and result aggregation. Probe nodes can execute locally or connect as authenticated workers in explicitly configured environments.

This structure allows the deployment owner to add real regional observations without hard-coding invented resolver locations into the browser. Every enabled node still needs accurate operational metadata and a maintained resolver path.

Improve the network

Have a probe-hosting idea or a reproducible DNS issue?

Send the node location, hosting context and what you want to measure. For a bug, include the domain only if it is safe to share, the record type, approximate UTC time and the visible request ID when available.

Contact MyWebDNS