Three newer standards protect and present your domain's email, and each one is easy to get slightly wrong. This check reads all three straight from the source, the way a sending mail server or an inbox would, and says in plain words what works and what to fix.
What this check looks at
- MTA-STS tells other mail servers to deliver to you only over encrypted
connections with a valid certificate. We read the
_mta-stsDNS record, fetch the policy file fromhttps://mta-sts.<your domain>/.well-known/mta-sts.txtexactly as senders do (no redirects, a strict certificate check) and match every host in your MX records against the policy's mx lines. - TLS-RPT says where senders should report encrypted deliveries that failed. We
read the
_smtp._tlsrecord and check that each reporting address can receive reports. We never send anything to those addresses. - BIMI points to your brand logo for inboxes that show one. We read the
default._bimirecord, check that DMARC is strict enough, fetch the logo and test it against the SVG Tiny Portable/Secure profile inboxes require, and read the mark certificate if you name one.
Reading the result
Each standard gets a verdict. MTA-STS is enforced, in testing mode, switched off, missing or broken. TLS-RPT is valid, missing or broken. BIMI is ready, declined, missing, not shown (DMARC doesn't enforce yet) or broken. Under each verdict you see the facts it rests on: the record, the policy file with its mode and max_age, every MX host with the pattern that matched it, the reporting addresses, the logo's size and shape, and the certificate's owner, issuer and expiry.
Missing is never a fault here. MTA-STS, TLS-RPT and BIMI are optional, so a domain without them gets an information note and nothing more. Something that is published but broken is a fault, because senders then act on a promise you can't keep: a policy that forgets a mail server makes mail bounce, and an expired certificate hides a logo you pay for.
This check has no grade of its own. The same findings, with their weights, are part of the email check, which runs this check inside it and grades the whole setup.
Getting MTA-STS right
Start in testing mode with a TLS-RPT record, so reports tell you what would have failed. Read them for a few
weeks, fix what they show, then switch the policy to enforce and raise max_age to a week or more. Every time
you edit the policy file, change the id in the _mta-sts record, or senders keep using their cached copy.
The policy host needs its own valid certificate and must serve the file directly. A redirect to your main website, a certificate for another name or a missing file all mean senders ignore the policy.
What we don't do
We don't connect to your mail servers on port 25, so their own certificates aren't checked here; the result says so. We don't verify mark certificates against the certificate authorities' roots or ask for revocation status: we read the facts in the certificate. The logo and certificate are fetched by our checker, never by your browser, and the logo itself isn't kept in the result.
Fetches go out from our server with an honest user agent, at most a few per check, and never more than our per-site limit allows. If a policy host is slow or busy, the result says that part couldn't be checked instead of guessing.
Fixing what you find
Every fault links to a step-by-step guide. For the DMARC side of BIMI, the DMARC builder writes a stricter record for you. Run this check again after a change; records show up once their TTL has passed, and senders pick up a new policy within its max_age.