Skip to content

Free DNS security checker

Check your public DNS configuration and find issues worth fixing.

Asks public resolvers only. Nothing is sent to your nameservers. What happens to the domain you enter

Example report

example.com
  • 1 Medium
  • 2 Low
  • 1 Information
  • 3 passed
  • CNAME points at a name that does not existwww.example.comMedium

    www.example.com is a CNAME for shop.oldhost.example, which does not resolve.

    Next step

    Remove the CNAME record if the service is no longer used, or recreate the resource it points at.

    View fix guide

  • No CAA recordsexample.comLow

    No CAA records were found for example.com.

    Next step

    Add a CAA record naming the certificate authorities you use, for example example.com.

    View fix guide

  • DNSSEC is not enabledexample.comLow

    No DS record exists for example.com, so its DNS answers are not signed.

    Next step

    Enable DNSSEC at your DNS provider, then publish the DS record it gives you at your registrar.

    View fix guide

  • Domain has no address recordswww.example.comInformation

    www.example.com has no A or AAAA records.

    Next step

    No action is needed if the domain is not meant to serve a website.

    View fix guide

What the DNS security check looks at

  • Addresses

    Whether the domain and its www name resolve.

  • Nameservers

    How many nameservers serve the zone.

  • CAA and DNSSEC

    Which authorities may issue certificates, and whether the zone is signed.

  • Dangling records

    CNAME records that point at names that no longer exist.

A dangling name is worth removing, but the check does not show that anyone could take it over; that depends on the service it pointed at.

Understand the issue and your next step

Each finding explains what we found, why it matters and what you can change. Start with the issues that need attention, then open the evidence when you want the detail.

  1. Enter your domain
  2. Review the findings
  3. Follow the fix guides
Example finding

CNAME points at a name that does not existMedium

A CNAME record points at a target name that does not resolve.

www.example.com CNAME shop.oldhost.example (NXDOMAIN)

Common DNS issues you can put right

  • CNAME points at a name that does not existMedium

    A CNAME left behind after a service was retired points at a name that no longer exists. Remove the record, or point it at the service that now serves the name.

    Read the fix guide

  • No CAA recordsLow

    Without CAA records, any public certificate authority may issue certificates for your domain. List the authorities you use.

    Read the fix guide

  • Only one nameserverLow

    One nameserver is one point of failure for every name in the zone. Most DNS providers give you at least two; publish them all.

    Read the fix guide

  • DNSSEC is not enabledLow

    No DS record was found for the domain at its parent zone, so DNS answers for it are not signed.

    Read the fix guide

  • Domain has no address recordsInformation

    The domain has no A or AAAA records, so it does not serve a website at this name.

    Read the fix guide

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

  • Address records: the A and AAAA records for the domain and its www. name, or for a subdomain, that name only. A domain with none is reported for information, since it may be used only for email.
  • Nameserver redundancy: the NS records at the zone apex, which pass with two or more distinct nameservers.
  • CAA: the records at the domain, then at each parent up to the zone apex, where a certificate authority looks for them (RFC 8659).
  • DNSSEC: whether the parent zone publishes a DS record for the zone, and whether the resolver validated the answer.
  • Dangling CNAMEs: for each name checked, whether its CNAME chain ends in a name that does not exist.

Reading a result

DNS decides where your website, mail and other services are found, so a mistake in it reaches everything under the domain. This check reads the public answers anyone can see and judges five settings that are often wrong or left at their defaults.

A pass means the setting was found as expected. Most findings here are hardening recommendations: a missing CAA record or an unsigned zone is common and not a fault on its own, and the finding explains what adding it would change.

A dangling CNAME is different. It usually means a hosted service was removed but its DNS record was left behind, and it is raised to High when the target is on a platform where someone else may be able to claim the name. Deal with it first.

What it does not do

  • It reads public DNS through public resolvers and does not query your nameservers directly, so it sees what those resolvers return, not the configuration at your DNS provider.
  • It checks the domain and its www. name, or the one subdomain you enter. Other subdomains are not discovered or checked; the subdomain finder lists names from certificate logs.
  • The nameserver check counts distinct nameserver names. It does not test whether they are on separate networks.
  • The DNSSEC check looks for a DS record and the resolver's validation flag. It does not fetch keys or verify the chain of signatures itself.

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

How many nameservers should a domain have?
At least two. RFC 1034 expects every zone to be served by more than one nameserver, and most managed DNS providers give you two or more. Ideally they sit on separate networks; this check counts the names and does not test that.
Do I need DNSSEC and CAA records?
Neither is required, and many domains run without them, which is why their findings are low-severity hardening recommendations. CAA limits which certificate authorities may issue certificates for the domain; DNSSEC lets resolvers detect forged DNS answers.
Does this check change anything or contact my servers?
No. It makes ordinary DNS lookups through public resolvers and changes nothing. It does not connect to your web or mail servers.