🌍 DNS Propagation Monitor by MojaLAB

About the DNS Propagation Monitor

The DNS Propagation Monitor by MojaLAB helps you check how a DNS record change spreads across the world. It queries multiple resolvers in different regions and visualizes response time, status, and the returned records on a minimal Google Map.

How it works

1. Start a check by entering a domain, choosing the record type (A, AAAA, MX, TXT, NS, CNAME) and a timeout.
2. The page acquires a temporary guest session from our API to authorize the request.
3. Resolvers across regions are queried in parallel; their responses are aggregated and displayed on the map.
4. The info panel shows success rate, average response time and a list of unique records observed.

What the marker colors mean

• Green: fast response (< 200 ms)
• Blue: normal (200–500 ms)
• Purple: slow (> 500 ms)
• Orange: timeout
• Red: error

Privacy & Security

Your browser obtains a temporary guest session from api.mojalab.com and uses secure HTTPS requests. No private keys are exposed on this page, and Google Maps uses a restricted API key. We apply rate limits to protect the service.

Troubleshooting

• 401 Unauthorized: the session may have expired; a refresh will renew it automatically.
• Slow or missing results: increase the timeout or try again later; some resolvers can be temporarily overloaded.

How DNS works (quick primer)

The Domain Name System (DNS) translates human-readable hostnames (like example.com) into IP addresses used by computers. When you look up a record, your resolver performs or reuses a chain of queries to find the authoritative source and caches the answer for faster future responses.

Recursive resolver

Typically operated by your ISP or a public provider (e.g., Google, Cloudflare). It receives your query and does the work to find the answer.

Root → TLD → Authoritative

The resolver may contact the root servers, then the TLD (like .com) servers, and finally the authoritative nameservers for the zone.

Record types

A maps to IPv4; AAAA to IPv6; MX indicates mail servers; TXT stores arbitrary text (e.g., SPF); NS lists authoritative servers; CNAME aliases one name to another.

TTL (Time To Live)

Controls how long an answer may be cached. Lower TTL means changes propagate faster but increase query load.

Propagation

Different resolvers refresh their caches at different times depending on TTL and policies, so updates appear globally with some delay.