Free, reads live DNS

Email deliverability audit

Enter your domain for an Email Setup Score across MX, SPF, DKIM, DMARC, TLS-RPT, MTA-STS and BIMI — with the exact DNS fixes.

DKIM has no discovery mechanism — if you know your selector, add it so we can confirm the key.

Email Setup Score: /100

for

Fix plan

Direct answer

What does an email deliverability audit check?

An email deliverability audit reads the DNS records a receiver checks before it trusts mail from a domain: MX, SPF, DKIM, DMARC, TLS-RPT, MTA-STS, and BIMI. A missing or broken record is a reason mail is rejected or filed as spam, before the words in the message are read. The score is the share of those records that are present and valid.

  • MX says where mail for the domain is received. It does not authorize sending.
  • SPF and DKIM authorize and sign outbound mail. DMARC ties them to the visible From address.
  • MTA-STS and TLS-RPT tell senders to use TLS and where to report TLS failures. They protect the connection, not the content.
  • BIMI shows a logo in supporting inboxes, and only after DMARC is at enforcement. A logo is not a deliverability fix.
  • DKIM has no public list of selectors. Add a selector such as google or selector1 if you know it, so the key can be confirmed.

Questions people ask

What is a good email setup score?

A domain that sends mail should have a valid SPF record under the 10-lookup limit, at least one DKIM key, and a DMARC record with a rua address. MX matters if the domain also receives mail. MTA-STS, TLS-RPT, and BIMI raise the score and are not required for basic delivery.

Why is DKIM marked as not checked?

DKIM keys live at a selector you choose, such as selector1._domainkey. There is no DNS query that lists every selector. Without a selector, the audit can only say the key was not looked up. Paste the selector from your mail provider to confirm the key.

Does this audit send a test email?

No. It only queries public DNS. Inbox placement also depends on complaints, volume, and the reputation of the sending IP, which a DNS read cannot see.

How is this different from the SPF checker?

The SPF checker walks the include chain and counts lookups. The audit includes that result and also reads DMARC, MX, and the transport records in one pass.

The records are only half of inbox placement.

Once SPF, DKIM, and DMARC pass, a cold domain still needs a slow sending history. iSend warms the domain and sends with the same authentication these tools just checked.