example.uk
domain SpoofableNo MX records.
Findings
-
Fail No SPF record SPF-MISSING
Receivers cannot tell which servers may send mail for this domain, and DMARC cannot pass on SPF.
How to fix: Publish a TXT record such as "v=spf1 include:<your provider> -all".
-
Fail No DMARC record DMARC-MISSING
Without DMARC, SPF and DKIM results are advisory and spoofed mail is not rejected. Google and Yahoo require DMARC from bulk senders.
How to fix: Publish _dmarc.example.uk TXT "v=DMARC1; p=none; rua=mailto:dmarc@example.uk" and move to p=quarantine, then p=reject.
-
Fail Spoofing protection: none SPOOF-EXPOSED
Anyone can send mail that appears to come from this domain and most receivers will accept it.
How to fix: Publish SPF with -all, sign with DKIM, then publish DMARC and enforce it.
-
Caution No MX records MX-MISSING
Senders will fall back to the A record of the domain. If the domain is not meant to receive mail, publish a null MX.
How to fix: Add MX records for your mail provider, or "MX 0 ." if the domain never receives mail.
-
Note No DKIM key found under common selectors DKIM-NOT-DISCOVERED
Selectors are chosen by the sender, so a key may exist under a name we did not try. Check a real message header for the s= tag.
-
Note No MTA-STS policy MTASTS-NONE
Optional; protects inbound mail against TLS downgrade.
Mail servers (MX)
No MX records.
SPF
No SPF record published.
DMARC
No DMARC record published.
DKIM
No key found under 54 common selectors.
Selectors are chosen by the sending service, so a key can exist under a name not tried here. The s= tag in a real message header names it.
Transport security
- MTA-STS
- not published
- TLS-RPT
- not published
- BIMI
- not published
Open relay test owners only
Checks whether each mail server accepts mail for recipients at other domains, which spammers exploit. Because the test sends SMTP commands to your server, it is only offered to verified owners.
Create an account and verify the domain to run this test.