Warning

Your domain doesn't send email but isn't locked against spoofing

The short version

Publish v=spf1 -all and a DMARC record with p=reject so nobody can send as your domain.

What it means

Your domain says it receives no email (it has a null MX record) and lists no senders, but it isn't locked against forgery. A locked domain has the SPF record v=spf1 -all and a DMARC policy of p=reject.

Why it matters

Domains that never send mail are favourite targets for phishing, because nobody watches them. Without SPF and DMARC saying "reject everything", receivers can't tell that mail claiming to be from this domain is always forged.

How to fix it

  1. Add a TXT record at the root of the domain with the value v=spf1 -all. It says no server may send mail for this domain.
  2. Add a TXT record named _dmarc with the value v=DMARC1; p=reject;. You can add an rua address to see how often the domain is forged, but it isn't required.
  3. Keep the null MX record.

The SPF builder and the DMARC builder write both records for you.

Cloudflare

Cloudflare offers this setup for parked domains under Email, DMARC Management; it adds the same records.

Check it worked

Run the full email check again once DNS has updated, usually within an hour. The result should say the domain doesn't send email and is locked against spoofing.