DNS Lookup

See every DNS record for a domain, and find out why its website or email isn't working.

Checked from our server. We don't store what you enter.

· Asked from our server through Cloudflare and Google DNS.

Enter a domain to see its DNS records

You get every record, plus checks for the website, email and SSL settings with what to fix.

How to use DNS Lookup

  1. Type a domain, a web address, an email address or an IP address, and press Look up.
  2. Read the checks first: they say whether the website, email and SSL records are set up right, and what to fix.
  3. Below them, every record is listed with its TTL: how long resolvers may keep it before asking again.
  4. Pick one record type to check just that, like MX for email or TXT for SPF and verification codes.
  5. Copy the report to send to your host or email provider.

How it works

Your browser can’t ask DNS servers directly, so the lookup runs on our server. It asks two public resolvers, Cloudflare (1.1.1.1) and Google (8.8.8.8), every question at the same time, shows Cloudflare’s answers and compares them with Google’s. Only the name you typed goes to them, never your IP address, and nothing is stored.

You can type a bare domain, a full web address (the domain is taken from it), an email address (its domain, with a focus on email records) or an IP address (a reverse lookup). International names like šuma.rs work too.

What the checks look for

Check What it tells you
Website address Whether the name has an A, AAAA or CNAME record, so a website on it can load. Private addresses (192.168.x.x) are flagged. Cloudflare addresses mean the orange-cloud proxy is on.
Email servers Whether MX records exist and which provider they point to (Google Workspace, Microsoft 365 and others).
SPF Exactly one TXT record starting with v=spf1, ending with ~all or -all. Two SPF records, or +all, break it.
DMARC A policy at _dmarc.yourdomain. p=none only reports; p=quarantine or p=reject protects you.
SSL certificates CAA records that limit who may issue certificates. If Let’s Encrypt isn’t allowed, free SSL setup fails.
Name servers Where the DNS is hosted, and whether there is more than one name server.
Resolvers disagree Cloudflare and Google see different answers: a recent change is still spreading.

Record types

Type What it does
A, AAAA The IPv4 or IPv6 address of the website.
CNAME Makes one name an alias for another (www to example.com).
MX Where email for the domain is delivered. Lowest number first.
NS The name servers that hold the domain’s records.
TXT Free text: SPF, site verification codes, DKIM keys.
SOA Settings of the whole zone, including its serial number.
CAA Which certificate authorities may issue SSL certificates.
PTR The name behind an IP address (reverse DNS).

After you change a record

Every record has a TTL, shown next to it: how long resolvers may keep it. Until the old record’s TTL runs out, some visitors still get the old answer. If Cloudflare and Google disagree, that’s what is happening; wait for the TTL and look up again.

If both show the old value long after the TTL, the change didn’t save, or you edited DNS at a provider your domain doesn’t use. The NS check shows which provider is really in charge.

Your own computer caches DNS too. To clear it:

  • Windows: open Command Prompt and run ipconfig /flushdns.
  • Mac: open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.
  • Chrome: open chrome://net-internals/#dns and press Clear host cache.

DKIM

DKIM keys live at a name only your email provider knows, like google._domainkey.example.com. To check one, look up that full name with TXT, or use the SPF, DKIM & DMARC Checker: it tries common selectors, reads the key size and follows every SPF include.

Questions

How do I check the DNS records of a domain?

Type the domain here and press Look up. The tool asks Cloudflare and Google DNS for the A, AAAA, CNAME, MX, NS, TXT, SOA and CAA records and the DMARC policy, lists them, and checks whether the website and email records make sense.

Why is my website not loading after changing DNS?

Resolvers keep the old answer until its TTL runs out, so a change can take from minutes to a day to reach everyone. The lookup compares Cloudflare and Google: if they disagree, the change is still spreading. If both show the old value, the change didn't save at your DNS provider, or your registrar still uses other name servers.

How long does a DNS change take?

A changed record reaches everyone once the old record's TTL has passed, often 5 minutes to an hour. Changing name servers at your registrar takes longer, up to 48 hours, because resolvers may keep the old name servers that long.

What is an MX record?

An MX record tells other mail servers where to deliver email for a domain. Without one, email to that domain bounces. The number in front is the priority: the lowest number is tried first.

How do I check my SPF and DMARC records?

Look up your domain with All common records. The checks show your SPF record (a TXT record starting with v=spf1) and the DMARC policy at _dmarc.yourdomain, and warn about common mistakes like two SPF records, +all or a missing DMARC record. For a deeper check, including SPF lookup counts and DKIM keys, use the SPF, DKIM & DMARC Checker.

What is a reverse DNS lookup?

It finds the name behind an IP address, using a PTR record. Enter an IP address to run one. Mail servers often check that a sending server has reverse DNS, so it matters if you run your own mail server.

Updated October 19, 2026 · Works in current Chrome, Edge, Firefox and Safari · Uses a QuickFixBase server check