MyWebDNS

Independent DNS observations

Check SOA records across available probe locations.

The SOA record describes the primary authority and timing parameters for a DNS zone.

14 probes configured
  • EvidenceAnswer, TTL, probe status and latency
  • Record typesA through CAA, including PTR
  • LocationProbe-reported coordinates, never random markers

QUERY / DNS

Run a DNS check

DNS

Use a hostname for most records. PTR also accepts an IPv4 or IPv6 address.

Native browser record menu.

Lookup requests are protected against cross-site submission and rate limited.

Observation desk

DNS results

Every row is one sampled probe observation. Agreement describes matching answers among probes that returned data; it is not an uptime or country-wide propagation score.

Ready for a lookup

Enter a domain and choose a record type to populate the observation map and result table.

DNS record field guide

How to read a SOA record check

The SOA record describes the primary authority and timing parameters for a DNS zone.

When to use this lookup

Use the serial to confirm that secondary nameservers received a zone update and inspect the negative caching policy during NXDOMAIN troubleshooting.

Example

example.com SOA ns1.example.net hostmaster.example.net 2026082801 …
Answer shape
Primary nameserver, responsible mailbox, serial, refresh, retry, expire and negative-cache timing values.
Common failure
The serial was not increased, so secondary nameservers continue serving an older zone version.
Related checks
NS record

Troubleshooting checklist

  • Increase the serial whenever a traditional secondary must transfer a changed zone.
  • Compare SOA answers directly at each authoritative server when secondaries disagree.
  • Negative answers can remain cached according to SOA-derived timing.