devopscodepro
Language
Productized services
Infrastructure AuditRisks, costs and quick wins — mapped in two weeks.Cloud Migration & IaCTerraform, CI/CD and a zero-downtime cutover.Monitoring-as-a-ServiceAlerting, on-call and incident response.Fractional DevOpsA senior engineer in your team, part-time.
Not sure where to start? The audit answers that.Request a quote →
server-assisted · every other tool runs in your browserAll 29 tools →
Infrastructure AuditCloud Migration & IaCMonitoring-as-a-ServiceFractional DevOps
ContactLog in
Request a quote
Theme
Language
server-assisted

Email deliverability

SPF, DKIM, DMARC, MX and blacklist report with plain-language fixes.

we only read public DNS records — nothing is stored
Enter a domain above to run the check.
These tools show symptoms. A full infrastructure audit finds the causes — risks, cost leaks and single points of failure, mapped in two weeks.
Request a quote →

What gets checked, and why it decides delivery

Mail delivery is decided by three DNS records and the MX hosts behind them. The check reads your SPF, DKIM and DMARC records the way a receiving server does, resolves the MX hosts, and reports the combinations that quietly send mail to spam.

The common failure is not a missing record but a contradictory one: SPF that ends in ~all while DMARC demands alignment, a DKIM selector that no longer exists after a provider migration, or two SPF records where only one is legal.

I have SPF, DKIM and DMARC. Why does mail still land in spam?

Existing is not the same as aligned. DMARC passes only when the domain in the visible From header matches the domain that SPF or DKIM authenticated. Send through a provider that signs with its own domain and never align yours, and DMARC fails on every message despite all three records being present.

What does p=none actually do?

Nothing, on purpose. It asks receivers to report but not to act, which is the right first step: you collect reports until the legitimate senders are all passing, then move to quarantine and reject. A domain left on p=none for years has the paperwork without the protection.

How many SPF records should I have?

Exactly one. Two SPF records is a permanent error for every receiver, and it is the most common way a domain loses authentication after adding a new sending service. Merge the includes into a single record.

Why does the SPF lookup count matter?

SPF allows ten DNS lookups per evaluation. Each include costs at least one, and provider includes nest. Cross the limit and the result is permerror — treated as a failure, not as a pass, so the record you carefully built stops counting.

Can this see whether a specific message was delivered?

No. It reads the public configuration that decides how your mail is judged. Delivery of one message depends on reputation, content and the receiver's own policy, none of which is visible from outside.

Related tools: DNS health, DNS lookup and WHOIS lookup.