SPF, DKIM and DMARC
DMARC, SPF and DKIM for Domains That Don't Send Email (Parked Domains)
Lock down a domain that never sends email with SPF -all, DMARC p=reject and a null MX. Here are the exact records, the subdomain catch and how to check them.
On this page
A domain that doesn't send email should say so in DNS. Publish an SPF record of v=spf1 -all, a DMARC record with p=reject, and a null MX record (MX 0 .) if the domain doesn't receive mail either. That tells receivers any message using the domain is fake, and the ones that enforce DMARC will refuse it.
People skip this because nothing seems broken. A parked domain with no records isn't failing anything. That's the problem: to a receiver, "no SPF, no DMARC" means "no instructions," and mail spoofing your unused domain gets judged on content alone. Unprotected domains that look like your real one are an easy pick for phishing.
Which domains count as "parked"
Any domain you own that should never appear in a From address. Typical examples:
- Defensive registrations:
example.net,example.co,examp1e.com. - Old brand names and acquired companies that now redirect to your main site.
- Campaign and product microsites that host a web page but no mailboxes.
- Domains bought for a project that never launched.
A domain can have a website and still be "parked" for email. The web records (A, AAAA, CNAME) and the mail records are independent.
p=reject goes live. If you have any doubt, publish DMARC at p=none with reporting first, read the aggregate reports for a few weeks, then move to reject.The records to publish
Here's the full set for example.net, a domain that sends nothing and receives nothing:
example.net. TXT "v=spf1 -all"
_dmarc.example.net. TXT "v=DMARC1; p=reject; sp=reject; rua=mailto:dmarc@example.com"
example.net. MX 0 .
*._domainkey.example.net. TXT "v=DKIM1; p=" (optional)
What each one does:
| Record | What it tells receivers | Source |
|---|---|---|
SPF v=spf1 -all | No IP address is authorized to send for this domain | M3AAWG, Microsoft, GOV.UK |
DMARC p=reject | Reject mail that fails authentication for this domain | M3AAWG, GOV.UK |
Null MX 0 . | This domain accepts no mail | RFC 7505 |
DKIM p= (empty key) | Any DKIM key under this domain is revoked | RFC 6376, GOV.UK |
SPF: v=spf1 -all
An SPF record with no mechanisms and a hard fail. Every sending IP fails. There's no include to maintain and no lookup cost. If you need a refresher on the syntax, see what an SPF record is.
DMARC: p=reject
This is the record that actually matters. SPF on its own only covers the envelope sender, which the recipient never sees. DMARC covers the From address people read, and it's what tells receivers to reject. Since nothing legitimate sends from this domain, nothing legitimate can pass, and there's no reason to start at p=none or p=quarantine once you've confirmed that.
sp=reject applies the same policy to subdomains. Under the DMARC spec, a missing sp tag falls back to p, so sp=reject here is belt and braces, but it makes your intent explicit. The DMARC record reference covers every tag, and the DMARC generator will build the record for you.
RFC 9989, the updated DMARC standard, also adds an np tag for subdomains that don't exist at all. If it's absent, sp applies, then p. On a parked domain with p=reject, you don't need it.
The reporting address
rua is optional, but reports are how you learn someone is spoofing the domain. Two things to know:
- A parked domain with a null MX can't receive the reports, so point
ruaat a mailbox on a domain that does receive mail, like your main domain. - When the report address is on a different domain, that domain has to authorize it. For
rua=mailto:dmarc@example.comonexample.net, publish this onexample.com:
example.net._report._dmarc.example.com. TXT "v=DMARC1;"
If you use a DMARC reporting service, it usually handles this authorization for you.
Null MX: MX 0 .
RFC 7505 defines this as the way to say "this domain accepts no mail": a single MX record with preference 0 and a target of ., and no other MX records alongside it. Senders trying to deliver to the domain fail immediately instead of queuing and retrying. Receivers can also use it to reject mail that uses the domain as a sender, and RFC 7505 gives 550 5.7.27 as the code for that.
Only publish it if the domain really has no mailboxes. GOV.UK notes that some DNS providers don't support null MX; if yours doesn't, skip it. The SPF and DMARC records still do the main job.
DKIM: optional revoked key
DKIM is the one record where the guidance differs. M3AAWG says a parked domain doesn't need a DKIM record at all. GOV.UK recommends a wildcard record at *._domainkey with v=DKIM1; p=. In the DKIM spec, an empty p= means the key has been revoked, so any signature claiming any selector on your domain fails.
Either approach is fine, since SPF and DMARC already reject unauthenticated mail. What you should do is remove any old DKIM keys (TXT or CNAME) left over from a time when the domain did send.
Subdomains: the catch
DMARC covers subdomains automatically through sp (or p). SPF and MX don't: each hostname has its own records, and www.example.net doesn't inherit anything from example.net.
M3AAWG recommends wildcard records where your DNS policy allows them:
*.example.net. TXT "v=spf1 -all"
*.example.net. MX 0 .
A DNS wildcard only answers for names that don't otherwise exist in the zone. Any subdomain you've actually created (say, www or shop) needs its own SPF and null MX records if you want it covered.
If a parked domain has a subdomain that does send, give that subdomain its own SPF, DKIM and DMARC records, and loosen sp on the parent so you don't block it. GOV.UK's guidance is to set sp=none in that case and protect the sending subdomain with its own DMARC record.
Step by step
- List every domain you own. Your registrar account is the source of truth, not your memory.
- Check each one for sending. Search your mail logs and vendor settings, and if in doubt, run
p=nonewith reporting for a few weeks. - Publish SPF
v=spf1 -allat the root. - Publish DMARC with
p=rejectand aruaaddress on a domain that receives mail. Add the authorization record on that domain if needed. - Publish a null MX if the domain receives no mail, and remove any other MX records.
- Clean up DKIM. Delete old selectors, and optionally add the wildcard revoked key.
- Cover subdomains with wildcard SPF and null MX, plus explicit records for subdomains that exist.
How to confirm it's working
Run each domain through the SPF, DKIM and DMARC checker. Or check from the command line:
dig +short TXT example.net
dig +short TXT _dmarc.example.net
dig +short MX example.net
You should see "v=spf1 -all", your DMARC record, and 0 .. GOV.UK points out that a wildcard DKIM record can't be confirmed by querying *._domainkey directly, so check it in your DNS provider's console. You can query any made-up selector, like test._domainkey.example.net, and you should get back the revoked key.
Then watch your DMARC reports. On a parked domain, every row in a report is either spoofing or something you missed in step 2.
How to keep it that way
- Make these records part of the checklist for every new domain registration.
- If a parked domain ever starts sending, update SPF, add DKIM and lower the DMARC policy to match before the first send.
- Review your registrar account once a year for domains nobody remembers buying.
When to get help
If you own dozens of domains and can't say with confidence which ones send, or DMARC reports show traffic you can't explain, it's worth having someone sort it out with you before you set anything to reject.
FAQ
Do I really need DMARC on a domain I don't use?
Yes. SPF alone doesn't protect the From address people see, and without DMARC there's no instruction for receivers to reject spoofed mail. DMARC with p=reject is the record that does the work.
Will these records break my website?
No. SPF, DMARC, MX and DKIM records don't touch the A, AAAA or CNAME records that serve your site. A domain can host a website and still publish all of these.
Should a parked domain use -all or ~all?
-all. The softer ~all exists for domains that worry about legitimate mail they've missed. A domain that sends nothing has nothing to miss.
Why do I need a different domain for DMARC reports?
A domain with a null MX accepts no mail, so reports sent to it would bounce. Point rua at a mailbox on a domain that receives mail, and add the authorization record on that domain if it's a different one.
Sources
- M3AAWG: Protecting Parked Domains Best Common Practices (2022 update)
- GOV.UK: Protect domains that don't send email
- Microsoft Learn: Set up SPF to identify valid email sources for your Microsoft 365 domain
- RFC 7505: A "Null MX" No Service Resource Record for Domains That Accept No Mail
- RFC 6376: DomainKeys Identified Mail (DKIM) Signatures
- RFC 9989: Domain-Based Message Authentication, Reporting, and Conformance (DMARC)
Related guides
- Authenticating Every Tool That Sends as Your Domain (Sender Inventory)List every service that sends mail as your domain, then give each one SPF coverage and DKIM signing on your domain so all of them pass DMARC.
- DKIM Fail: Body Hash Did Not Verify, Signature Failed and Other CausesDKIM fails when the message changed after signing (body hash did not verify), the signed headers changed, or the receiver can't find a matching public key.
- DMARC Fail: Why DMARC Fails and How to Fix ItDMARC fails when neither SPF nor DKIM passes for a domain aligned with your From address. Usually a sender lacks custom DKIM. Here's how to find and fix it.
- DMARC Policy: p=none vs quarantine vs reject (and Getting to Enforcement)p=none only monitors, p=quarantine asks receivers to junk failing mail, p=reject asks them to refuse it. Start at none, fix your senders, then tighten.
- DMARC Record Syntax and Tags ExplainedA DMARC record is a TXT record at _dmarc.yourdomain with tags for policy, reporting and alignment. Here's what each tag does and what's changed under DMARCbis.
- DMARC Reports: How to Read Aggregate (rua) and Failure (ruf) ReportsDMARC aggregate reports are daily XML summaries of every IP sending as your domain and whether it passed. Here's how to read them and what to do with them.
Still stuck?
Some deliverability problems take an experienced eye to untangle. Tell me what you're seeing and I'll tell you what I'd check first. The first 30-minute call is free.