Diagnostic cases

Fictional scenarios with the data and the tool that would reveal the problem.

SPF checker

An SPF record that stopped working after adding a provider

A small company sends from its own server, a CRM, a helpdesk and a newsletter tool. After adding the fourth include, mail to some providers started failing with "SPF permerror".

Symptom

Authentication-Results show spf=permerror; some receivers mark mail as spam.

What the tool shows

The SPF checker counts 12 DNS lookups once the includes are expanded: two of the providers' records include several more domains each.

What to do

Remove providers that no longer send, use dedicated subdomains for bulk tools, or ask providers for IP-based includes. Re-check until the count is 10 or less.

v=spf1 a mx include:_spf.crm.example.net include:helpdesk.example.org include:spf.newsletter.example.com include:_spf.google.com ~all
Open SPF checker
DMARC alignment simulator

SPF passes, DKIM passes, DMARC fails

A platform sends invoices on behalf of example.com. Reports show DMARC failures although both SPF and DKIM pass.

Symptom

Aggregate reports list the platform's IP with spf=pass, dkim=pass and disposition=quarantine.

What the tool shows

The alignment simulator shows SPF passing for bounce.platform.example.net and DKIM signed with d=platform.example.net: neither domain is example.com, so nothing aligns.

What to do

Enable the platform's custom DKIM signing with a selector on example.com (and, if offered, a custom Return-Path subdomain). DKIM alignment alone makes DMARC pass.

Open DMARC alignment simulator
Bounce reader

A recipient keeps bouncing after a typo

A support agent typed an address by hand. Every message to it comes back within seconds.

Symptom

Bounce with status 5.1.1 and "Recipient address rejected: User unknown".

What the tool shows

The bounce reader classifies it as a permanent failure for the final recipient; the diagnostic comes from the receiving server itself.

What to do

Stop sending, confirm the address through another channel and correct it. Do not retry the wrong address: repeated hard bounces hurt reputation.

Open Bounce reader
Email header analyzer

An email that takes forty minutes to arrive

Users complain that password reset emails arrive late. The application logs show immediate acceptance.

Symptom

Received headers show a 38-minute gap between the sending platform and the receiving provider.

What the tool shows

The header analyzer flags a slow hop: the receiving server deferred the connection (greylisting or rate limiting) and the sender retried later.

What to do

Keep a stable sending IP and HELO, warm up new IPs gradually, and separate transactional mail from bulk so it is not throttled with it.

Open Email header analyzer
MX lookup

Mail to a domain that never arrives

A customer insists their domain works, but every message to it is returned as unroutable.

Symptom

Bounce with 5.4.4 or "domain does not accept mail".

What the tool shows

The MX lookup shows a null MX (0 .) record: the domain explicitly declares it does not accept mail.

What to do

The customer needs to publish real MX records (or remove the null MX) at their DNS provider; nothing on the sending side can fix it.

Open MX lookup
Mailiqo

Follow every message without opening headers

In Mailiqo every message has its own history of statuses and events: deliveries, bounces and errors with their reason, all from the panel.

See what Mailiqo includes