HealthyMail
example.com mail
example.com
clean
checked 5 h ago
Mail health monitoring
The records that keep mail deliverable, plus up to 8 sending addresses checked against the blocklists that get mail rejected.
Included on every plan.
PlansFreeProBusiness
| What breaks | hostnag |
|---|---|
| Mail stops being deliveredMX, SPF, DKIM, DMARC and blocklists, at the expiry cadence of your plan | Yes |
On the board
Sample plates of this type, drawn by the board itself.Acme Retail
02Sample dataNeeds attentionMail
acme-shop.example mail
acme-shop.example
DMARC policy is none: spoofed mail is…
checked 5 h ago
How it works
- 01
Start from the domain
The domain the records live on, not the mail server hostname, like example.com.
- 02
hostnag reads MX, SPF, DMARC and DKIM
DKIM is read per selector, up to ten of them, every time hostnag polls the domain.
- 03
Up to 8 sending addresses against 4 blocklists
The MX hosts' IPv4 addresses, up to 8 of them, are checked against 4 public lists, always with the runner's own resolver, never a customer's.
- 04
When a lookup does not answer
That area is left out of the report. It is never counted as clean.
What you'll be told
What you get told
[Warning] Mail setup for example.com has gaps
No SPF record. Anyone can send mail as this domain. No DMARC record. Receivers have no policy for mail that fails SPF and DKIM.
[Warning] SPF record changed for example.com
Now: v=spf1 include:_spf.new-provider.example ~all. Was: v=spf1 include:_spf.old-provider.example ~all.
Sample alerts, rendered by the same code that writes your email and Slack messages.
Settings
- History
- a strip of days, each Healthy, Needs attention or At risk by that day's worst finding, with the finding named in the app; on the monitor's History, the board's strip views and a status page
- Target
- a mail domain
- DKIM selectors
- up to 10, comma-separated
- Blocklists
- 4 public lists, checked with the runner's own resolver
- Interval
- 1440 min on Free, 60 on Pro, 15 on Business
Questions
Will you use my own DNS resolver for the blocklist lookups?
No, always the runner's own. A customer's resolver could be made to hide a listing.
Do you check every mail server, or just the domain?
The addresses behind the domain's MX records, up to 8 of them; a domain with more has the rest skipped.
Related
DNS monitoringThe records that point people and mail at your systems, watched for drift from the answer you told hostnag to expect.Domain monitoringEvery domain's registration watched for lapsing, a registry hold or a blocked renewal, plus whether its nameservers answer for it and agree, and whether its DNSSEC signatures are still fresh.
Read
SPF, DKIM and DMARC explained: how to read the records and the mistakes that get mail rejectedRead SPF, DKIM and DMARC records term by term, look them up with dig, and fix the mistakes that get legitimate mail rejected.How to check a mail server against blocklists (and why "not checkable" is not "clear")The four DNS blocklists that get mail refused, the dig command that checks an address, how to get delisted, and why an unanswered lookup is no pass.
Add a host. Hear about it first.
Start free