Tool guideEmail Tools

Email Deliverability Checker – Complete Guide to SPF, DKIM, DMARC, Reverse DNS, TLS and Blacklists

What decides whether receivers accept your mail, how the NetTools.tech Email Deliverability Checker tests each part with real DNS, SMTP, TLS and blacklist lookups, how to read PASS, WARNING, FAIL, NOT TESTED and UNKNOWN, and how to fix the common problems.

By NetTools.tech · · 8 min read

Invoices land in the spam folder, a customer's mail server answers with "550 rejected due to SPF PermError", or Gmail defers your newsletter with "this message does not meet IPv6 sending guidelines regarding PTR records". Each of these messages points to a different part of a domain's email configuration, and each part is published in a different place.

The Email Deliverability Checker reads all of those places in one run — SPF, DKIM, DMARC, MX, reverse DNS, SMTP, TLS, DNS blacklists, MTA-STS and TLS-RPT — and reports what it found, what it means and what to change.

What is email deliverability?

In simple terms

Deliverability is whether a receiving mail server accepts your message and where it puts it. Before looking at the content, the receiver asks a few technical questions: is the sending server allowed to send for this domain, is the message signed, what does the domain owner want done with failures, does the sending address have a consistent identity, and is that address on a blocklist. A wrong answer to any of them can mean the spam folder or a rejection.

Technical background

  • SPF (RFC 7208) is a TXT record listing the servers allowed to use the domain in the envelope sender. Evaluation is limited to 10 DNS-querying terms and 2 lookups that return nothing.
  • DKIM (RFC 6376) signs messages; the public key is a TXT record at <selector>._domainkey.<domain>.
  • DMARC (RFC 7489) at _dmarc.<domain> states the policy (none, quarantine, reject) for mail that fails both SPF and DKIM alignment, and where to send reports.
  • Reverse DNS: the PTR name of the sending IP must resolve forward to the same IP (forward-confirmed reverse DNS, FCrDNS).
  • MTA-STS (RFC 8461) and TLS-RPT (RFC 8460) protect and report on the encryption of mail arriving at the domain.

Why use the Email Deliverability Checker?

  • See every authentication and transport setting of a domain in one report instead of ten separate lookups.
  • Find out exactly why SPF returns PermError: the report counts real DNS lookups through nested includes and names the terms that cost the most.
  • Check the sending IP for reverse DNS and blocklist problems before a campaign or after a migration.
  • Get a concrete fix for each finding, written for the person who has to change the DNS record.
  • Export the result as CSV or JSON, or print it for a client or a change request.

Who should use it?

System administrators and DevOps engineers who run mail servers, developers who send transactional mail through a provider, agencies and consultants auditing a client domain, and business owners who want to know why their mail is not arriving.

How the Email Deliverability Checker works

The NetTools.tech server runs the checks and the page shows each section as soon as it finishes. Nothing is displayed for a section before the server has answered.

SPF is evaluated the way a receiver does it. The record is fetched, every include and redirect is followed, and each DNS-querying term is counted. Counting the word "include" in the record would be wrong: one include can hide five more. Loops, references to domains without an SPF record, invalid networks and lookups that return nothing are reported separately, and a DNS timeout is reported as a temporary failure rather than as a missing record.

DKIM keys are read for the selectors you enter: key type, key length, revoked keys and flags. DMARC, MTA-STS (the TXT record and the policy file over HTTPS, without following redirects) and TLS-RPT are parsed and validated tag by tag. MX records are listed with priorities and addresses.

For SMTP and TLS, the server connects to up to four of the domain's MX hosts on port 25, reads the greeting and the EHLO capabilities, starts TLS and inspects the certificate: validity period, host name, chain, protocol and cipher. Individual TLS versions are probed on the first reachable host. The session then ends with QUIT.

For each sending IP you supply, the PTR record is looked up and confirmed forward, and the address is queried on DNS blocklists. Each list reports its own result: listed, not listed, timeout, error, unavailable or unsupported.

How to use the NetTools.tech Email Deliverability Checker

  1. Open the Email Deliverability Checker and enter the domain after the @ of your sender address, for example example.com.
  2. Optional: enter the sending IP addresses, such as 203.0.113.10 or 2001:db8::25. You find them in the first Received: header of a message you sent.
  3. Optional: enter the DKIM selectors, the s= value in the DKIM-Signature header, for example selector1.
  4. Press Run check. The summary and the ten sections fill in as results arrive.
  5. Open the sections marked FAIL or WARNING. Each check shows its findings, the DNS records found (with a copy button), what to do, and expandable technical details.
  6. Export the report as CSV or JSON, or print it.

The same report is available in the terminal with /deliverability example.com --ip 203.0.113.10 --selector selector1.

Understanding the results

StatusMeaningWhat to do
PASSThe check ran and found no problemNothing
WARNINGThe check ran and found something to improveRead the finding; plan the change
FAILThe check ran and found a problem that breaks or weakens emailFix it first
NOT TESTEDThe check needs input you did not giveAdd the sending IP or DKIM selector
UNKNOWNThe check was attempted but got no answerRun it again; it is not a result about your domain
SectionWhat a problem looks like
SPFNo record, two records, more than 10 lookups, +all, an include that points nowhere
DKIMNo key for the selector, a revoked key (p= empty), an RSA key under 1024 bits
DMARCNo record, p=none, no rua= address, sp=none under a strict policy
MX RecordsNo MX, an MX without an address, an MX on a private address
PTR / Reverse DNSNo PTR, or a PTR name that does not resolve back to the IP
SMTP ConnectivityNo greeting, a non-220 greeting, EHLO refused
SMTP TLS SecurityNo STARTTLS, an expired certificate, a certificate for another name
DNS BlacklistsA listing; the finding says how widely the list is used
MTA-STSA record without a valid policy file, MX hosts missing from the policy
TLS ReportingNo record, or a record without a valid rua= address

The overall status is Critical Issues when any check failed, Issues Found when there are only warnings, and Healthy when the checks that ran found nothing. The configuration score (0–100) is calculated from the sections that produced a result, using the weights listed under the gauge; it rates the checked configuration and is not a prediction of inbox placement.

Example: SPF over the lookup limit

An illustrative domain publishes this record:

v=spf1 include:_spf.mailprovider.example include:crm.example include:helpdesk.example include:newsletter.example a mx ~all

It contains four includes, so it looks like six lookups with a and mx. The report shows 13 of 10 lookups and FAIL, with this table:

Term in the recordLookups it costs
include:_spf.mailprovider.example5
include:newsletter.example3
include:crm.example2
include:helpdesk.example1
a1
mx1

The mail provider's include expands to four more includes. The fix is to remove the services that no longer send mail for the domain, and to replace a and mx with the ip4: address of the one server that actually sends. The SPF Generator builds the new record.

Common use cases

  • Auditing a domain before moving to a new mail provider, and again afterwards.
  • Finding the cause of an SPF PermError quoted in a bounce message.
  • Checking a new sending IP for reverse DNS and blocklist listings before the first campaign.
  • Verifying that a certificate renewal on the mail server went through.
  • Preparing the move from p=none to p=reject.

Troubleshooting

SPF fails although the record looks correct

Cause: the lookup limit is exceeded through nested includes, or the domain has two SPF records. Fix: read the lookup table in the SPF section; merge duplicate records into one.

DKIM shows FAIL for a selector that I know is in use

Cause: the selector is misspelled, or the key is published under a different domain (many services sign with their own domain until you set up a custom one). Fix: copy s= and d= from a real DKIM-Signature header with the Email Header Analyzer; check the domain given in d=.

Reverse DNS fails although I added a PTR record in my DNS zone

Cause: PTR records live in the zone of the IP address owner, not in your domain's zone. Fix: ask the hosting provider or ISP that assigned the address to set the PTR.

All SMTP checks are UNKNOWN

Cause: no MX host answered the NetTools.tech server. That usually points to the test network or to a firewall that only admits known senders. Fix: test from another network; the SMTP Test shows the full session for one host.

A blocklist shows "Provider unavailable"

Cause: the list did not answer, or it requires registration that this server does not have. Fix: nothing on your side; the status for that list is not known. MultiRBL Check shows each list in detail.

Common mistakes

  • Adding a second SPF record for a new service instead of extending the existing one.
  • Publishing p=reject before reading DMARC reports, which blocks legitimate senders that are not yet aligned.
  • Treating a PASS on DKIM as proof that messages are signed.
  • Entering the MX server's address as the sending IP when mail actually leaves through a provider's relay.
  • Changing the MTA-STS policy file without changing the id= in the TXT record, so senders keep the old policy.

Limitations

  • The checker validates published configuration. Whether real messages pass SPF and DKIM alignment is only visible in message headers and DMARC reports.
  • SMTP and TLS results describe the MX hosts, which receive mail, as seen from one location. They do not test your outgoing mail.
  • DKIM selectors and sending IP addresses cannot be discovered; without them those checks are not run.
  • SPF macros depend on the sending IP and are counted but not expanded.
  • At most 5 sending IPs, 5 selectors and 4 MX hosts per run.

Security & privacy

Only public domains and public IP addresses are accepted; private, loopback, link-local and reserved ranges are refused. SMTP connections go only to the MX hosts of the domain entered, only on port 25, and stop after EHLO and STARTTLS — no message is sent and no credentials are requested. Each MX address is validated before connecting and then used directly, which prevents DNS rebinding; the MTA-STS policy is fetched through the SSRF-protected client. The domain, addresses and selectors you enter are not stored.

Summary

Deliverability problems almost always trace back to one of ten published settings. Run the Email Deliverability Checker with your domain, a sending IP and a DKIM selector, fix the FAIL results first, and read UNKNOWN and NOT TESTED as gaps in the picture rather than as good news.

Frequently asked questions

How is the configuration score calculated?

Each section has a weight: SPF 20, DMARC 20, DKIM 15, MX 10, reverse DNS 10, blacklists 10, SMTP 5, TLS 5, MTA-STS 3 and TLS-RPT 2. PASS earns it in full, WARNING half, FAIL nothing. Sections that were not tested or gave no answer are left out. It rates the checked configuration and does not predict inbox placement.

Why are reverse DNS and blacklists shown as NOT TESTED?

Both need the IP address your mail is sent from. That address is not published in DNS, and MX servers, which receive mail, are often different machines, so the checker does not guess. Enter the address from the first Received header of a message you sent.

What is the SPF limit of 10 DNS lookups?

A receiver stops evaluating SPF after ten terms that need a DNS query: include, a, mx, ptr, exists and redirect, counted through every nested include. Beyond that it returns PermError and SPF fails for all mail. The report shows how many lookups each term costs.

Why does DKIM need a selector?

A domain can publish any number of DKIM keys under names chosen by each mail service, and DNS has no way to list them. The selector is the s= value in the DKIM-Signature header of a message sent by that service.

DKIM shows PASS. Are my messages signed correctly?

PASS means a valid public key is published for that selector. Whether messages are signed with the matching private key and verify at the receiver is only visible in the headers of a delivered message.

What is the difference between UNKNOWN and FAIL?

FAIL means the check ran and found a problem. UNKNOWN means the check was attempted but got no answer, for example a DNS timeout, a blocked port or a blocklist that did not respond. UNKNOWN is never counted as a pass, and it is not evidence of a fault.

The SMTP check could not connect. Is my mail server down?

Not necessarily. The test runs from one location, the NetTools.tech server. Hosting networks and some mail servers block port 25 from unknown addresses. Confirm from a second network before changing anything.

Does the checker send a test email?

No. The SMTP session to each MX host ends after the greeting, EHLO and STARTTLS. No sender, recipient or message is transmitted, and nothing arrives in any mailbox.