The Email Health check grades your mail domain in four sections (DNS, Blacklist, Web Server, Mail Server), marks each check as Passed, Warning or Error, and lists the worst result per section in a Problems summary. The Mail Server section includes the Exim version check of the shared rule "Software version currency". The Email Health check runs on demand and in scheduled reports.
How it tests
The sections run in this order; on the page each section appears as soon as it is complete.
- DNS: the delegation and nameserver checks of the DNS Check tool, followed by the email records:
- SPF, evaluated by the same code as the SPF Record Checker (its warnings only; see Limits).
- DMARC.
- DKIM at the 7 default selectors (
default,google,selector1,selector2,k1,dkim,mail). - MTA-STS (TXT record and
https://mta-sts.<domain>/.well-known/mta-sts.txt, timeout 5 s), TLS-RPT and BIMI. - Blacklist: every IPv4 address of every MX host of your domain against 49 IP blacklists, and your domain against 9 domain blacklists, with the same lists as the Email Blacklist Check.
- Web Server: an HTTP HEAD request to
http://<domain>andhttps://<domain>(timeout 8 s, redirects followed); a TLS handshake on port 443 with certificate verification, reading the days until the certificate expires. - Mail Server, for each MX host. The MX records and the PTR check are DNS lookups and run for any domain. Everything else connects to your mail servers, on port 25 (timeout 8 s), greeting them as
nettests.net. Connecting to a mail server is an active probe, so like the vulnerability scans these checks run only for a site you have verified while signed in (in a scheduled report: a verified site of the report's account), never for a domain anyone can type in: - Connect time.
- PTR record of the MX address, and whether the PTR name resolves back to that address.
- Greeting banner: does it name a fully qualified domain name (FQDN)? Any Exim version in it is judged by the Software version currency rule.
- STARTTLS offered and negotiated; the certificate is not verified.
- Open relay test, only with the option "I control this whole server" ticked (off by default; a scheduled report saved before the option existed runs with it off) and only on mail servers within your domain itself:
MAIL FROM:<probe@example.net>,RCPT TO:<probe@example.org>, thenRSET. DATA is never sent, so no message is delivered. On shared hosting the mail server belongs to the hosting provider and serves every account on it, so leave the option off there. A mail server outside your domain that your MX records name (a mail provider's) gets the greeting and STARTTLS only, as from any sending server. - Problems: per section, the error labels, else the warning labels, else "all checks passed."
What you see
| Situation | Result |
|---|---|
| No SPF record / no DMARC record | Error: "no SPF record — senders can't be authorized." / "no DMARC record at _dmarc.<domain>." |
SPF warnings (more than one record, +all, ?all) or DMARC warnings (p=none, no rua) |
Warning per item |
| No DKIM key at the 7 default selectors | Warning |
MTA-STS policy not in enforce mode, or absent |
Warning; enforce is Passed |
| No TLS-RPT record | Warning: "(optional)" |
| An MX address or the domain listed | Error: "<target> — <zone>", "LISTED" |
| Answered and not listed | Passed: "not listed" |
| MX hosts without IPv4 addresses | Warning: "no MX IP addresses to check." |
| HTTP or HTTPS gives no response | Error: "no response: <exception>" |
| TLS certificate expired / under 14 days left | Error / Warning |
| TLS verification or handshake fails | Error |
| No MX records | Error: "no MX records found for <domain>." |
| MX connect fails | Error |
| MX connect time above 5,000 ms | Warning |
| No PTR record / PTR does not resolve back to the address | Error / Warning |
| Banner host is not an FQDN | Warning |
| Exim version in the banner | Verdict of the Software version currency rule |
| STARTTLS not offered | Warning |
| Server accepts the relay recipient | Error: "server ACCEPTED relay to an external address!" |
| Our server may not open outbound SMTP connections (see Limits) | Only the MX records and PTR rows; a note under the Mail Server section: "Mail server connection checks not run: our hosting provider blocks outbound SMTP connections (ports 25, 465 and 587) from our server. …" It counts as no error, warning or pass. |
| The option "I control this whole server" is off | No relay row; no MAIL FROM or RCPT TO is sent; a note under the Mail Server section: "Open relay test not run: the option “I control this whole server” is off. …" It counts as no error, warning or pass. Connect time, banner and STARTTLS rows are unchanged. |
| An MX host outside your domain (a mail provider) | No relay row for it; a note: "Open relay test not run on <hosts>: these mail servers are outside <domain>, …" |
| Domain is not a verified site of yours | Only the MX records and PTR rows; a note under the Mail Server section: "Mail server connection checks not run: they connect to your mail servers, so they run only for sites you have verified. …" It counts as no error, warning or pass. |
| A section raises an exception | Error: "Section failed" with the exception |
Limits
- Blacklist rows without a verdict (provider refusal, DNS error, timeout) are dropped from the section, not shown. If every query fails this way, the section shows one Passed row: "Blacklist status", "no targets to check."
- Blacklist verdicts depend on the DNS resolver used and, for the Spamhaus lists, on whether a Spamhaus data-query access key is configured, as for the Email Blacklist Check.
- Each MX host is probed on one resolved address; further addresses of the same host are not probed. IPv6 addresses are not checked against blacklists.
- The Web Server requests, the MTA-STS policy fetch and the MX probes go only to public addresses; any request or redirect hop to a non-public address is refused.
- Our hosting provider blocks outbound SMTP connections (ports 25, 465 and 587) from our server, as of 2026-11-08. While it does, the Mail Server section runs its DNS checks only (MX records and PTR per MX host) and says so; connect time, banner, Exim version, STARTTLS and the open relay test are not run.
- The open relay test checks one recipient domain (
example.org); a server that only relays after authentication or for other domains is not distinguished. - An SMTP error during the relay test (for example a refused
MAIL FROM) counts as "relaying correctly rejected." - Of the SPF Record Checker's 10 tests (lookup count, void lookups,
ptr), none is carried into this scorecard; only its warnings are. - DKIM is found only at the 7 default selectors.