Skip to content
Clinic open · free diagnosis, no appointment needed2,000+ domains monitored

DNS record lookup

Every record on one page, read live through two independent resolvers so a stale cache cannot quietly give you the wrong answer.

Judged against RFC 1035, read over DNS-over-HTTPS

Reads live DNS through two independent resolvers. Free, instant, no signup.

Symptoms

You changed a record and cannot tell whether it took. Your provider's panel shows one thing and a colleague sees another. Mail is behaving as though a record you deleted is still there, which, for as long as its TTL has left to run, it is.

Diagnosis

DNS is a cache with a publishing system attached. What you edit is the authoritative copy; what the world acts on is whatever resolvers have stored, until the TTL expires. Any disagreement between two resolvers means a change is still spreading.

This tool asks two independent public resolvers and shows what each record actually contains, including the TTL, so you can tell "not published" from "not propagated yet".

Cure

  1. Before a migration, lower the TTL on the records you plan to change and wait for the old TTL to pass.
  2. After a change, wait out the TTL before concluding anything is broken.
  3. If the records look right but mail is wrong, the problem is the content, not the publishing. Run the full checkup.

Questions people actually ask

Why do two lookup tools show different results?

Usually propagation: a record changed recently and resolvers still hold the old answer until its TTL expires. This tool reads through two independent public resolvers and tells you when they disagree rather than picking one.

What is TTL?

How long a resolver may cache the answer, in seconds. It is also how long your change takes to reach everyone after you make it, lower the TTL a day before a migration, not during one.

Why is my TXT record split into pieces?

A DNS text string tops out at 255 bytes, so longer records are published as several quoted strings and joined back together by whoever reads them. That is normal; what is not normal is a DNS panel joining them with a space.

Which records matter for email?

MX for receiving, TXT for SPF, DMARC and DKIM, and A records for the hosts your MX names. This tool shows the raw values; the full checkup tells you whether they are correct.

Related tests

Every fix on this site is yours to implement. If you would rather someone did it, I take this work directly.