Skip to content

Free DNS checker

Look up a domain's DNS records, from addresses and mail servers to nameservers, with their TTLs.

Asks public resolvers only. Nothing is judged and nothing is changed. What happens to the domain you enter

Example report

example.com

DNS records for example.com

TypeTTLValue
A300192.0.2.10
300192.0.2.11
AAAA3002001:db8::10
CNAMENo records
MX360010 mx1.example.net
360020 mx2.example.net
TXT3600"v=spf1 mx -all"
3600"example-site-verification=4f1c2a9e7b"
NS86400ns1.example.net
86400ns2.example.net
SOA3600ns1.example.net hostmaster.example.com
CAA36000 issue "letsencrypt.org"
DSNo records

Looked up through public resolvers (1.1.1.1). The resolver did not validate these answers with DNSSEC.

What the DNS lookup shows

  • Addresses

    A and AAAA records, and any CNAME alias the name points at.

  • Mail

    MX records by preference, and TXT records such as SPF.

  • The zone

    NS and SOA: the nameservers and the zone's primary server.

  • Certificates and DNSSEC

    CAA records, and the DS record from the parent zone.

Each record is shown with its TTL, as public resolvers answer for it. A lookup raises no findings; the DNS security checker judges the records.

Keep watch after you've fixed it

Ironfang Security rechecks a verified domain every week or every day and tells you what changed: new findings, fixes and certificates nearing expiry.

Free during the preview. Domain verification required.

  1. NewIssue detected
  2. FixedConfirmed by recheck
  3. ReopenedDetected again

How the check works

  • A and AAAA: the IPv4 and IPv6 addresses for the name you enter.
  • CNAME: whether the name is an alias for another name.
  • MX and TXT: the mail servers in order of preference, and text records such as SPF and verification tokens.
  • NS and SOA: the nameservers the name is delegated to, and the zone's primary nameserver and contact.
  • CAA and DS: the certificate authorities allowed to issue for the name, and the DNSSEC link from its parent zone.
  • The TTL of each record, the resolver that answered, and whether it validated the answers with DNSSEC.

Reading a result

The table shows what a resolver returns today for each record type at the name you entered. A row with no records means the name exists but has nothing of that type; a row saying the name does not exist means the resolver answered NXDOMAIN.

The TTL is the number of seconds a resolver may cache an answer. After you change a record, resolvers that cached the old one keep returning it until its TTL runs out, so a change can take that long to be seen everywhere.

This is a lookup, not a check: nothing is marked as passed or needing attention. The DNS security checker judges the same DNS for nameserver redundancy, CAA, DNSSEC and dangling CNAMEs.

What it does not do

  • It looks up the name you enter only, not its www. name or other subdomains.
  • It asks public resolvers, which can return a cached value for up to the TTL after a change. It does not query your nameservers directly and does not see internal DNS.
  • CAA and DS are looked up at this name only. Certificate authorities also look at parent names for CAA, and a subdomain inside a signed zone has no DS record of its own; the CAA and DNSSEC checkers follow those rules.
  • It covers nine record types. Others, such as SRV and PTR, are not looked up, and DMARC and DKIM records live at other names (_dmarc.<domain> and <selector>._domainkey.<domain>): the DMARC and DKIM checkers read those.

What happens to the domain you enter

The check runs from Ironfang Security's published scanner address with the same low-impact limits as a scan. Nothing you enter is stored or logged. A result is reused for five minutes, and a certificate log search for an hour, so a repeat check is quick and the domain is not checked again.

Guides

A few things worth knowing

Why does the result differ from what my DNS provider shows?
Usually caching. Public resolvers keep an answer for its TTL, so a record you changed recently can show its old value until that time runs out. If the new value never appears, check the NS records: they show which provider the domain is actually delegated to.
What is a TTL?
Time to live: how many seconds a resolver may cache a record before asking again. A short TTL makes changes appear sooner; a long one means fewer lookups reach your nameservers.
Why can I not see my DMARC or DKIM record?
They are published at other names: DMARC at _dmarc followed by your domain, and DKIM at a selector name under _domainkey. This tool looks up only the name you enter; the DMARC and DKIM checkers look in the right places.