Skip to main content

Free DNS Security Checker for Your Domain

See the NS, SOA, CAA, MX, SPF and DMARC records that public resolvers return for your domain, the DS answer for it, and a suggested order for any changes.

Last updated 15 November 2026

Loading tool…

This DNS security checker asks public resolvers seven questions about one domain name and lays the answers out together: its name servers, SOA record, CAA records, mail exchangers and TXT records, the TXT records at its _dmarc name and the DS record for the name. A record map lists every NS, SOA, CAA, MX and TXT record returned in a form the tool reads, with filters by record type and by text, and the lookups table counts the others. DS records are counted in the DS lines, not listed. Below it, each line says what the answers showed, such as which certificate authorities the CAA records name, and, where it applies a rule, names the RFC and section the rule comes from. A short list then orders any suggested changes by what each depends on. Our server makes the lookups for you, so check only a domain you own or have permission to check. The tool does not validate DNSSEC signatures, and it cannot tell whether a record is right for your setup.

How to use this tool

  1. 1

    Enter the domain name

    Type the domain itself, without www, or paste an address from your browser: the tool keeps only the host name. An IP address, a name with no dot and an address with a user name or password are refused in the page, before anything is sent.

  2. 2

    Run the check

    Press Check DNS records. Our server makes seven lookups: NS, SOA, CAA, MX and TXT for the name and TXT for its _dmarc name through public resolvers, and one HTTPS request to a DNS-over-HTTPS resolver for the DS record. The whole check is stopped after 12 seconds.

  3. 3

    Read the lookups and the record map

    The first table shows what each lookup returned, or why it did not complete. The record map lists every NS, SOA, CAA, MX and TXT record returned in a form the tool reads, and the first table counts any others. Type part of a value into the filter box or untick a record type to narrow the list, and press Show every record to clear both.

  4. 4

    Read what the answers show

    Each line is marked Review or Note. Review marks something to look at, such as two SPF records or a single name server, and includes this page's own prompts. Note describes what was seen. No line is a pass mark.

  5. 5

    Plan the changes

    The last list orders any suggested changes by what each depends on, and says whether that order comes from a named document or is this page's own suggestion. Copy the plan as text, check each step against your own systems, and run the check again after a change.

What the DNS security checker asks, and what it cannot see

When you press Check DNS records, our server reads the name you typed and refuses it if it is an internal or special-use name. It then makes seven lookups, at most three at a time. Six are DNS questions put to a fixed list of public resolvers at 1.1.1.1, 1.0.0.1, 8.8.8.8 and 8.8.4.4: NS, SOA, CAA, MX and TXT for the name, and TXT for the name with _dmarc in front of it. The seventh is one HTTPS request to the DNS-over-HTTPS resolver at cloudflare-dns.com, asking for the DS record, made after our server has looked up that resolver's own address. Each DNS question stops after at most 2.5 seconds and the DS request after at most 4 seconds, and the whole check is stopped after 12 seconds. A DNS answer of more than 64 records, or of more than 32 KiB once our server has parsed it, is not read, and that lookup is listed as not completed. A check counts as seven requests against a limit on requests per visitor and in total, so it can be refused when too many have run recently. If a lookup reports that the name does not exist, the tool says so once and starts no further lookups. Our server sends nothing to your site. It asks public resolvers once for each record type. It does not see a private or split-horizon zone that answers differently inside your network. RFC 1034 section 3.6 says a record's TTL describes how long it can be cached before it should be discarded. A change made a short time ago may therefore not show yet. Apart from the TXT lookup at its _dmarc name, the lookups ask about exactly the name you enter: not its parent names, not other names beneath it, and not its A, AAAA, DNSKEY or DKIM records. The tool does not test mail delivery: use the email spam tester on this site. A result is a reading of public answers. It is not evidence of permission to test a domain, nor that a domain is safe or meets any standard.

CAA records: the certificate authorities a domain names

A CAA record lets the holder of a domain name specify the certificate authorities authorised to issue certificates for it. RFC 8659, the standards-track document that defines the record, says a compliant authority must check for a relevant CAA record set before it issues a certificate. Where one exists, the authority must not issue unless the request is consistent with it or an exception in its own certificate policy or practices statement applies. Used as a CAA record checker, the tool lists the issuer domain names in the issue and issuewild properties. Section 4.2 describes issue as a request that issuers grant authorisation to the holder of the named issuer domain, or a party acting under that holder's explicit authority. It says a property that gives no issuer domain name requests that no certificates be issued. Section 4.3 limits issuewild to certificates that specify a wildcard domain name. The tool reads each value with the grammar in section 4.2 and reports a value that does not match it, which the RFC treats the same as one that names no issuer. It matches tag names without regard to letter case, as section 4.1 does, and reports a record whose issuer critical flag is set on a tag it does not read. When no CAA record comes back, that is not the whole answer. Section 3 has an authority search from the name in the certificate request up through each parent name, stopping before the root, until it finds a record set. This tool asks at the one name you entered, so it cannot say whether a parent name holds a set. Section 5.1 strongly recommends, but does not require, the use of DNSSEC to authenticate CAA records. RFC 8659 also says relying parties must not use CAA records as part of certificate validation. The record is a control an authority applies before it issues a certificate.

MX, SPF and DMARC records read side by side

For MX, the tool reports the mail exchangers returned, or one of two other cases. RFC 7505 defines the null MX, a single MX record with preference 0 and a dot as its exchange, as the way a domain indicates that it does not accept email, and says such a domain must not advertise any other MX record. With no MX record at all, RFC 7505 says senders will attempt to deliver mail to the hosts at the addresses in the domain's A or AAAA records, which this tool does not look up. For SPF, the tool counts the TXT records that RFC 7208 section 4.5 would select: those that begin with v=spf1 followed by a space or the end of the record. It compares those characters without regard to letter case, because section 12 says the literal strings of the grammar are case-insensitive. Section 4.5 gives the result none when no record is selected and permerror when more than one is. The tool does not evaluate what a record authorises. For DMARC, the tool asks for TXT records at the _dmarc name and follows RFC 9989, whose header says it obsoletes RFC 7489. It counts a record that begins with the version tag, with DMARC1 in capitals as section 4.8 writes it, and reports the p tag of a single record: none, quarantine or reject, or that the tag is missing, repeated or has another value. Following the DKIM tag-value syntax that section 4.7 says DMARC records follow, it does not read spaces or tabs around a tag name or a value as part of it. Section 4.10 says that if multiple DMARC records are returned for one name they are all discarded. Section 4.10.1 has a receiver go on to parent names when the name has no valid record. This tool does not, so for a subdomain check the parent domain too. The DMARC checker on this site reads every tag of a pasted record. Where MX records come back with no SPF record, the tool shows the two together as its own prompt.

The DS record, and why this is not a DNSSEC test

If you came looking for a DNSSEC checker or a DNSSEC test, expect an observation here, not a verdict. RFC 4034 section 5 says a DS record refers to a DNSKEY record by storing its key tag, its algorithm number and a digest of it. It says the DS record appears only on the parent side of a delegation, and gives the example that the DS record for example.com is stored in the com zone and not in the example.com zone. The tool asks one DNS-over-HTTPS resolver for the DS record of the name you entered. It starts that lookup first, so every result has asked it. The DS row reads one of four ways in fixed words: the resolver returned DS records for this name, the resolver returned no DS record for this name, the resolver's answer could not settle it, or the lookup did not complete, which leaves no DS observation. When the answer settles the question, the tool also reports whether the resolver marked its answer authenticated. That mark is the AD field of the resolver's JSON answer, which Cloudflare's documentation describes as meaning that every record in the answer was verified with DNSSEC. RFC 4035 section 4.9.3 says a security-aware stub resolver must not place any reliance on signature validation allegedly performed on its behalf, except when it obtained the data from a trusted security-aware recursive name server via a secure channel. Read the mark as that resolver's own statement. The tool validates no signature and fetches no DNSKEY record. Because a DS record sits only at a delegation, a name that is not a delegation point, such as a host name inside your zone, has no DS record of its own. An absent DS record for such a name says nothing about its zone, and the tool says so when no SOA record came back. RFC 4033 section 2 calls a signed, delegated zone with no DS record in its parent zone an island of security, which has no authentication chain from its parent. The tool cannot see which of these describes your zone.

Ordering DNS changes by what each one depends on

The last part of the result turns the observations into a short ordered list. A step appears only when its observation was made, and each step says what it depends on and where its place in the order comes from. For mail, the order comes from RFC 9989 section 5.1, which sets out a domain owner's actions in sequence: publish an SPF record and configure DKIM signing for an aligned domain, set up a mailbox for aggregate reports, and then publish a DMARC record. Section 5.1.4 says domain owners usually start with p=none and a rua tag. Section 5.1.6 says legitimate mail streams that fail must be addressed before any attempt to publish an enforcement policy. Section 5.1.7 says that, depending on how often the domain sends mail, it may take many months of reading aggregate reports before an owner is sure that all of its mail is properly authenticated. So the tool lists an SPF step before a DMARC step, and the step about moving beyond p=none last of the mail steps. For DNSSEC, RFC 4035 section 2.4 says a DS record should point to a DNSKEY record that is present in the child zone, and that DS records which do not meet its conditions are not useful for validation. The tool reads that as signing the zone first and having the DS record published second, and says the reading is its own. The other placements are this page's own suggestion and are labelled that way: a second name server first, because the name servers answer for every other record, and CAA after the mail steps, because no document cited here sets an order between them. Before publishing CAA records, list every certificate authority that issues certificates for the name and the names beneath it. The plan can be copied as text. It is built from one set of public answers, so check each step against your own systems before you change a record.

Sources

Worked example

An invented example, not taken from any domain: the owner of a small business checks the domain that its website and email use.

NS
Two records
SOA
One record
CAA
No record
MX
One mail host
TXT
Two begin with v=spf1
TXT at _dmarc
No record
DS
No DS record returned

One line is marked Review: the two SPF records, with what RFC 7208 says about selecting more than one. The other lines are Notes. The suggested order has four steps: combine the SPF records into one, publish a DMARC record that starts at p=none, decide whether to publish CAA records, and, if DNSSEC is wanted, sign the zone before a DS record is published.

The owner lists the systems that send mail for the domain, merges the two SPF records into one and runs the check again. They set up DKIM signing and a mailbox for reports before publishing the DMARC record, and leave CAA until their host has told them which certificate authorities issue certificates for the site.

Who uses this tool

Owners taking over a domain

See the name servers, mail records and CAA records a domain publishes before changing its host or its email provider.

Teams setting up email authentication

Check that one SPF record is returned and whether a DMARC record exists before working through the order RFC 9989 sets out.

Developers changing certificate provider

Read the CAA records at the name to see which certificate authorities they name before moving to another one.

Staff answering a security questionnaire

Look up what the domain publishes for CAA, SPF and DMARC, and the DS answer, before answering a question about them.

Frequently asked questions

What does the DNS security checker send, and where?

Our server makes seven lookups for the name you enter: six DNS questions to public resolvers at 1.1.1.1, 1.0.0.1, 8.8.8.8 and 8.8.4.4, and one HTTPS request to the DNS-over-HTTPS resolver at cloudflare-dns.com for the DS record, after looking up that resolver's own address. It sends nothing to your site. Each DNS question stops after at most 2.5 seconds, the DS request after at most 4 seconds and the whole check after 12 seconds. Check only a domain you own or have permission to check.

Is this a DNSSEC checker?

It reports one thing about DNSSEC: whether a resolver returned DS records for the name, returned none or gave an answer that could not settle it, and whether that resolver marked its answer authenticated. It does not validate signatures or fetch DNSKEY records. RFC 4035 section 4.9.3 says a security-aware stub resolver must not rely on validation performed on its behalf unless the data came from a trusted security-aware recursive name server via a secure channel. Treat the result as an observation.

Why is no CAA record shown when one is published?

The tool asks for CAA records at exactly the name you enter. RFC 8659 section 3 has a certificate authority look at the requested name and then at each parent name until it finds a record set. A set published at a parent domain is therefore not shown when you enter a subdomain. Enter the name the record is published at. RFC 1034 section 3.6 also says a record's TTL describes how long it can be cached. A new record may therefore not show at once.

What does it mean when two SPF records are found?

RFC 7208 section 3.2 says a domain name must not have multiple records that would cause an SPF check to select more than one, and section 4.5 says the check then produces the result permerror. The tool counts a TXT record as an SPF record when it begins with v=spf1 followed by a space or the end of the record, in any letter case. Its suggested step is to merge what each record authorises into one record.

Does the checker test whether my email is delivered?

No. It reads the MX, SPF and DMARC records the resolvers return, and it does not connect to a mail server or send a message. To test delivery, send a message through the email spam tester on this site. To read every tag of a DMARC record, paste the record into the DMARC checker. This tool reports only how many DMARC records were returned at the _dmarc name and what the p tag of a single record says.

What is recorded when I run a check?

The domain name goes to our server in one request, and the resolvers receive it in each question. The tool does not log the name, send it to analytics or put it in the page address. For the request limit, a shared store counts requests by the address they come from (one IPv4 address, or an IPv6 /64 block) over a one-minute window, and one check counts as seven requests. On completion, the page sends one analytics event naming this tool and the page, and nothing you typed.

Related tools and services