MediumInfrastructure · usually medium
No email configuration of any kind was found
No MX, SPF or DMARC records exist for this domain.
Check your own domain
What causes this
The domain resolves but publishes nothing related to email. If it is not used for mail, that is fine — though publishing a null MX and a restrictive SPF record is worth doing, because it stops the domain being an easy candidate for forgery. If it is meant to handle mail, nothing is configured yet.
What it breaks
The domain cannot receive mail, and because it publishes no policy, forged mail claiming to come from it faces no obstacle.
How to fix it
Either configure mail properly, or publish records that state the domain sends and receives none.
- If the domain should handle mail, follow your provider's setup guide for MX, SPF and DKIM, then add DMARC.
- If it should not, publish a null MX record, an SPF record of 'v=spf1 -all', and a DMARC record with p=reject.
Example record
TXT · @
v=spf1 -all
Only for a domain that sends no mail at all.
Related problems
- MTA-STS is not configuredThe domain does not publish an MTA-STS policy. This is optional but worth having.
- MTA-STS record published but the policy file is unreachableThe DNS record announces a policy that cannot be fetched.
- An MX host does not resolve to an addressA mail exchanger is published but its hostname has no A or AAAA record.
- An MX record points at an aliasMX targets must be hostnames with address records, not CNAMEs.
- No MX records foundThis domain publishes no mail exchangers, so it cannot receive email.