Skip to main content
InboxkitSign up free

Free tool

DNS record validator

Validate the DNS records your sending domain needs. The validator tests SPF, DKIM, DMARC and MX against the rules receiving mail servers apply and marks each one Valid, Invalid or Not found, with the exact issue.

Need a pass or fail verdict on your email setup? Use this validator. Just want to see every record published on a domain, including A, TXT and NS? Use the email DNS checker.

Walkthrough

Watch: validate your DNS records in under a minute

A 40-second walkthrough. SPF, DKIM and DMARC each fail quietly: a domain with two SPF records, a missing DKIM key, a DMARC policy that does nothing. The validator checks all three plus MX and returns valid, invalid or not found with the exact problem. In the demo SPF fails on two records; merging them into one makes it pass.

How to use the DNS record validator

  1. Step 1

    Enter your sending domain

    Type the domain you send email from, such as yourdomain.com, in Domain to validate.

  2. Step 2

    Click Validate DNS Records

    The validator runs the SPF, DKIM and DMARC tests together, then checks MX.

  3. Step 3

    Read the four status tiles

    SPF, DKIM, DMARC and MX each show Valid, Invalid or Not found. The card under each tile lists the issues found.

  4. Step 4

    Fix and validate again

    Copy the suggested record if SPF or DMARC is missing, publish the fix at your DNS host, then click New Validation.

What this DNS validator tests

Each record is held to the rules email authentication depends on. A rule in the first column marks the record Invalid. A rule in the second column leaves it Valid but lists the issue so you can tighten it.

RecordInvalid whenWarning when
SPFMore than one SPF record on the domain. More than 10 DNS lookups. The record ends in +all.No all mechanism at the end. Longer than 255 characters. Uses the deprecated ptr mechanism.
DKIMNo public key: the p= tag is missing or empty. Looked up on 43 common selectors.Key looks shorter than 1024 bits. A 1024-bit key (2048 is suggested). Testing mode with t=y.
DMARCVersion is not v=DMARC1. The p= tag is missing or not none, quarantine or reject. A rua or ruf address without mailto:.p=none. pct below 100. No rua address for reports. No sp= subdomain policy. Strict alignment for both SPF and DKIM.
MXNot found when the domain has no MX records, so it cannot receive replies.None. MX passes when at least one record exists.

The validator does not list A, AAAA, TXT or NS records. To see every record published on the domain, use the DNS checker.

Common DNS validation failures and how to fix them

SPF: multiple SPF records found

A second sending tool was added as a new TXT record. Delete both and publish one record that includes every sender.

Fails

v=spf1 include:_spf.google.com ~all v=spf1 include:sendgrid.net ~all

Passes

v=spf1 include:_spf.google.com include:sendgrid.net ~all

SPF: more than 10 DNS lookups

Every include, a, mx and redirect costs a lookup, and so do the includes inside them. Remove services you no longer send from, and list your own servers as ip4: ranges, which cost none.

Fails

v=spf1 a mx include:_spf.google.com include:sendgrid.net include:mailgun.org include:servers.mcsv.net ... ~all

Passes

v=spf1 ip4:203.0.113.10 include:_spf.google.com include:sendgrid.net ~all

DMARC: report address without mailto:

Receivers ignore a rua or ruf address that is not a mailto: URI, so you never get reports.

Fails

v=DMARC1; p=quarantine; rua=dmarc@yourdomain.com

Passes

v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com

DKIM: not found

Either DKIM signing is not turned on at your email provider, or it uses a selector outside the 43 the validator tries. Generate the key in your provider's admin console, publish it at selector._domainkey.yourdomain.com, and look up a custom selector in the DKIM checker.

To rebuild a record from scratch, use the SPF generator, and follow the DMARC setup guide to move a valid p=none policy to quarantine once your reports show SPF and DKIM passing.

FAQ

Frequently asked questions

A DNS record validator tests your records against the rules receiving mail servers apply, instead of only showing what is published. This one validates the four records a sending domain needs, SPF, DKIM, DMARC and MX, and returns Valid, Invalid or Not found for each, with every issue it found listed under the record.

It fails SPF when the domain has more than one SPF record, when it needs more than 10 DNS lookups (counting include, a, mx, exists, ptr and redirect, plus the includes inside each included record), or when it ends in +all, which lets any server send as you. It also warns when there is no all mechanism at the end, when the record is longer than 255 characters, and when it uses the deprecated ptr mechanism.

The most common cause is two SPF records on one domain, which happens when a second sending tool is added as a new TXT record instead of being merged into the first. Receivers treat that as a permanent error. Merge them into one record, for example v=spf1 include:_spf.google.com include:sendgrid.net ~all. The next most common cause is going over the 10 DNS lookup limit with too many include: mechanisms.

A DKIM record fails when it has no public key, either because the p= tag is missing or because it is empty, which is how a revoked key is published. The validator also estimates key length from the published key: it warns when a key looks shorter than 1024 bits, suggests 2048 bits when it finds a 1024-bit key, and warns when the record is still in testing mode with t=y.

It tries 43 common selectors, including Google's google and dated selectors such as 20230601, selector1 and selector2 for Microsoft 365, k1 for Mailchimp, s1 and s2 for SendGrid, and mg and mailgun for Mailgun. It stops once it has found two keys and shows the first. If your provider uses a custom selector, look it up in the DKIM checker.

DMARC fails when the version is not v=DMARC1, when the p= policy tag is missing, when p= is not none, quarantine or reject, or when a rua or ruf report address is not written as mailto:address. A valid record can still get warnings: p=none (monitoring only), pct below 100, no rua address for reports, no sp= subdomain policy, or strict alignment for both SPF and DKIM.

The DNS checker is a lookup that lists the raw records on your domain, including A, AAAA, TXT and NS records, so you can see what is published. The DNS validator is a pass or fail test of the four email records, SPF, DKIM, DMARC and MX, against the rules above. Use the checker when you need to see a value, and the validator when you need to know whether your setup is correct.

Publish the change at your DNS host, then click New Validation and run the domain again. If the old result still shows, the previous record is cached until its TTL (time to live) runs out. Most changes are visible within minutes to a few hours, and they can take up to 48 hours.

No. A Valid result means your SPF, DKIM, DMARC and MX records are present and follow the rules, which is the baseline every inbox provider expects. Inbox placement also depends on domain and IP reputation, sending volume, list quality and the content of the email itself.

Get started

Need help configuring DNS records?

Inboxkit automatically configures all DNS records for maximum deliverability.