Independent DNS observations

Check MX records across available probe locations.

MX records define which mail servers accept email for a domain and in what priority order.

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 MX record check

MX records define which mail servers accept email for a domain and in what priority order.

When to use this lookup

Use this lookup after changing email providers or when some senders still route mail to an older server.

Example

example.com MX 10 mail.example.com
Answer shape
One or more preference-and-hostname pairs; lower preference values are attempted first.
Common failure
An MX target has no usable A or AAAA address, is published as a CNAME, or an old route remains cached.
Related checks
A record, AAAA record, TXT record

Troubleshooting checklist

  • Lower MX preference numbers are tried first.
  • The MX target must resolve to an address and should not be a CNAME.
  • Check SPF, DKIM and DMARC TXT records separately when delivery succeeds but authentication fails.