DNS Lookup

Your query goes from our server to the Cloudflare (1.1.1.1) public resolver over DNS-over-HTTPS. If Cloudflare does not answer, it goes to Google (8.8.8.8) instead. The "Answered by" line shows which one replied.

• All common looks up A, AAAA, CNAME, MX, TXT, NS, SOA and CAA at once. SRV and PTR have to be picked on their own.
• TTL is how many seconds resolvers may keep the answer in cache.
• Labels: TXT records that start with v=spf1 are marked SPF, with how the record ends (for example -all is fail). TXT records on _dmarc.yourdomain are marked DMARC with their p= policy. An MX of "0 ." is marked Null MX: the domain accepts no email.
• MX records are sorted by preference, lowest (tried first) at the top.

To check how a domain handles email:

• Look up MX on the domain to see which servers receive its mail, in the order senders try them
• Look up TXT on the domain and find the line marked SPF, which lists who may send as the domain
• Look up TXT on _dmarc.yourdomain for the DMARC policy

A result like "No MX records (OK)" means the domain exists but has no MX record of its own.

Resolvers keep an answer until its TTL runs out. If the old record had a TTL of 3600, it can take up to an hour to go away. Lower the TTL well before a planned change.

The name does not exist in DNS at all. Check the spelling, and whether the domain is registered and delegated to name servers.

A reverse lookup. Enter an IP address and it returns the host name set for that address, if any. Mail servers often check it.

No. The tool only asks the two public resolvers, so it cannot target a name server or pull a whole zone.