Test the email configuration of a domain
Six public declarations are read: the declared mail server, the sending authorisation, the anti-spoofing policy, the brand logo, the age of the registration and the declared registrant. No message is sent, no account is solicited, and these declarations can be read by anyone.
A domain analysis is obtained by submitting an address on that domain: the health of the domain is part of the response returned for it. Any address on the domain will do, since the six checks concern its public declarations.
What the result contains
The domain health block appears in the response, below the checks on the address. It carries a score, a label, and the detail of each declaration read. A missing declaration is returned as missing, never guessed: a missing piece of data is better than an invented one.
| Declaration | What it indicates | What its absence means |
|---|---|---|
| MX | Does the domain declare a server in charge of receiving its mail? | Without an MX record, no message can be delivered: every address on the domain is invalid. |
| SPF | Does the domain declare which servers are allowed to send on its behalf? | Without SPF, anyone can pass themselves off as this domain. Two SPF records are worse than none: RFC 7208 forbids them, and receiving servers reject the check. |
| DMARC | Does the domain tell receiving servers what to do with an unauthenticated message? | Without DMARC, spoofing goes through with no instruction. A policy declared but left without effect is progress for show: it observes, it does not protect. |
| BIMI | Does the domain publish a brand logo intended for inboxes? | Its presence is a positive sign, never a penalty: the approach assumes authentication is already in place. |
| Domain age | How long has the domain been registered, according to the public registry? | A domain registered a few days ago and already used to sign up somewhere is a reason for caution, not proof of fraud. |
| Registrant | Who declared the domain, and through which registrar? | The information is often anonymised for individuals, in line with the GDPR. It is then absent rather than guessed. |
How to read the score
The declarations read produce a score and a label. A defect that stops mail from arriving weighs more than an authentication defect, because it has an immediate consequence. The presence of a brand logo is a favourable sign, it never takes points away.
| Label | Minimum score | What it means |
|---|---|---|
| excellent | 90 | Complete configuration, nothing to report. |
| good | 75 | A minor gap, with no effect on delivery. |
| fair | 55 | Incomplete authentication, or a recent domain. |
| risky | 35 | Several defects combined, easy spoofing. |
| critical | 0 | Domain with no mail server, or a collapsed configuration. |
From the domain to the mailbox
Domain health and SMTP verification complement each other: the first says how the domain is kept, the second confirms the mailbox itself. Together, they give a complete reading of each address, from the domain right down to the mailbox.
The domain and the address, in a single response
Domain health describes the configuration, address verification confirms the mailbox. The free address checker returns both together, check by check.
A dedicated mention for the major providers
The major mailbox providers receive a dedicated mention rather than a score. Their configuration is the same for millions of mailboxes: scoring it would teach nothing about the address analysed. The score is thus kept for the domains where it truly informs.
What happens during the test
The declarations read are public: every mail server in the world consults them before accepting a message. No message is sent, no account is solicited on the domain analysed, and the test leaves no trace with its owner.
The public demo feeds no validation history: that history is only written for the authenticated traffic of an account. What outlives a test concerns the domain, not the address, and benefits everyone: a domain recognised as answering for everything is not queried again for nothing.
Frequently asked questions
- How do I test the email configuration of a domain?
- A domain analysis is obtained by submitting an address on that domain: the health of the domain is part of the response returned for it. Any address on the domain will do, since the six checks concern its public declarations.
- Does the test send a message to the domain analysed?
- SMTP verification opens a session with the receiving server, announces the sender and the recipient, then stops before writing the message. No mail arrives in the mailbox being analysed, and the person whose address is verified receives nothing.
- How does domain health combine with verifying an address?
- Domain health and SMTP verification complement each other: the first says how the domain is kept, the second confirms the mailbox itself. Together, they give a complete reading of each address, from the domain right down to the mailbox.
- How are the major mailbox providers handled?
- The major mailbox providers receive a dedicated mention rather than a score. Their configuration is the same for millions of mailboxes: scoring it would teach nothing about the address analysed. The score is thus kept for the domains where it truly informs.
Content updated on 7 September 2026.