Skip to main content
Resources/Guides
Guide

DMARC for Parked and Non-Sending Domains

A parked, inactive or non-sending domain is the easiest mail infrastructure to spoof. There are no legitimate senders to break, so the locked-down configuration below applies to every parked domain you own. The sources are RFC 7505 (NULL MX), RFC 7208 (SPF) and RFC 7489 (DMARC). RFC 7489 is the original DMARC specification, obsoleted in May 2026 by DMARCbis (RFC 9989). The remaining sources are RFC 6376 (DKIM), the M3AAWG Parked Domains BCP (June 2022) and the NCSC blog “Protecting parked domains for the UK public sector”.

By ShieldMarc · 9 min read · Updated November 2026

Facts checked against live DNS, the relevant RFC or the provider’s own documentation.

How do I set up DMARC for a parked domain that never sends email?

Publish a DMARC policy of p=reject with strict alignment (v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s). Publish an SPF record that authorises nobody (v=spf1 -all). Publish either no DKIM record or an explicit revocation record. Add a NULL MX record (0 .) to declare that the domain does not accept mail either. Together they leave no record that could make a spoofed message pass SPF, DKIM or DMARC for the domain.

The minimum DNS to publish on a non-sending domain is:

example.com.            IN  MX   0 .
example.com.            IN  TXT  "v=spf1 -all"
_dmarc.example.com.     IN  TXT  "v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s; rua=mailto:dmarc@example.net;"

The free SPF Record Generator builds the SPF record (choose hard fail and add no senders). The DMARC Record Generator builds the DMARC record with strict alignment. The generator leaves sp= out when it matches p=, so add sp=reject by hand if you want it written out, as recommended below.

The 0 . in the MX is a NULL MX as defined in RFC 7505 §3 (preference 0, exchange a single zero-length label). Receiving servers that see it should reject mail with SMTP reply 556 and enhanced status 5.1.10 (RFC 7505 §4). The SPF record uses -all (Fail). RFC 7208 §8.4 defines it as “an explicit statement that the client is not authorised to use the domain in the given identity”. Most operators call this “hard fail”.

A few DNS providers historically rejected a bare dot as the MX target. If your DNS UI refuses 0 ., try 0 . with an explicit trailing dot, or contact support. Cloudflare, Route 53, Azure DNS, Google Cloud DNS and most managed DNS services accept it today.

How do I redirect a parked domain to reject all mail?

You do not redirect a parked domain to a separate “reject mailbox”. You publish DNS records that tell the rest of the internet not to send mail there in the first place, and ask receivers to treat any message claiming to be from there as forged. The records are a NULL MX, v=spf1 -all, a DMARC record at p=reject and, optionally, a wildcard DKIM revocation record.

The table sets out what each of the four records does.

RecordValueWhat it does
MX0 .NULL MX (RFC 7505). Receiving servers reject inbound mail with SMTP 556 / 5.1.10.
TXTv=spf1 -allSPF Fail (RFC 7208). No host is authorised to send as the domain.
TXT (_dmarc)v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s; rua=mailto:...DMARC reject with strict alignment for both DKIM and SPF (RFC 9989, which replaced RFC 7489 in May 2026). Receivers are asked to refuse mail that fails, which on a non-sending domain is all of it, and each receiver makes the final call (RFC 9989, section 5.4).
DKIM (optional)*._domainkey TXT "v=DKIM1; p="Wildcard revocation: per RFC 6376 §3.6.1 an empty p= means the key has been revoked. Defence in depth: the M3AAWG BCP's primary recommendation is to publish no DKIM record at all on a parked domain.

If you also want to lock down inbound TLS posture, add a single belt-and-braces extra. The extra is an MTA-STS policy of mode: enforce with no MX entries. It documents that this domain has no inbound mail at all.

Why p=reject and not p=none for a non-sending domain?

p=none is for active sending domains during the DMARC monitoring phase, when you need aggregate reports to confirm legitimate mail aligns before enforcing. A non-sending domain has no legitimate mail flow to break, so there is nothing to monitor first. Going straight to p=reject is the correct default, and it is what NCSC and M3AAWG both recommend for parked domains.

For an active sending domain we tell people to start at p=none and only move to p=reject once aggregate reports show that legitimate mail aligns. That progression is always report-driven: you read the aggregate reports and tighten the policy when they show alignment, never by ramping a percentage. DMARCbis (RFC 9989) reinforces this by removing the pct tag entirely (Appendix A.6).

See the quarantine vs reject guide for the same decision applied to active domains.

Why include sp=reject if I already set p=reject?

RFC 7489 §6.3 (retained in DMARCbis, RFC 9989) says that if sp= is absent, receivers MUST apply p= to subdomains. So technically p=reject alone covers subdomains too. We recommend setting sp=reject anyway, because it is explicit, it survives anyone copying the record into a tool that splits the tags, and it documents intent for the next admin who reads the record. That's also how ShieldMarc's DMARC Checker scores it: a record with sp= weaker than p= is flagged as a separate control failure.

Should I publish a DKIM record on a parked domain?

The M3AAWG Parked Domains BCP (June 2022) recommends publishing no DKIM record at all on a non-sending domain. With no DKIM key in DNS, the verifier cannot retrieve a public key. Any signature claiming to be from your domain will therefore fail verification automatically. That is the simplest and lowest-maintenance option.

Some operators add a wildcard DKIM revocation record at *._domainkey.example.com with value v=DKIM1; p= for defence in depth. RFC 6376 §3.6.1 states that an empty p= value means the key has been revoked. Any selector an attacker tries to assert therefore resolves to an explicit revocation. This is a community technique, not a M3AAWG mandate.

Do I need MX records at all for a parked domain?

Yes, but only one: the NULL MX. If you publish no MX records, receivers fall back to the A or AAAA record of the bare domain (RFC 5321 §5.1). That means anyone hosting a website on the parked domain could end up with surprise inbound SMTP. The NULL MX short-circuits that and gives senders an unambiguous machine readable refusal.

If the domain still has MX records from when it was in use, see our blog post on how to remove MX records from a parked domain. It walks through replacing them with a NULL MX.

Where else can I read the official guidance?

Authoritative pages worth bookmarking:

Verify your parked-domain setup in one click

Run a free Security Grade against the parked domain. The scan reads the SPF record (-all), the DMARC p= and sp= policy and any DNSSEC or CAA gaps. It treats a NULL MX as a domain that accepts no mail. It tells you which record is missing or weaker than recommended. It does not check DKIM: the DKIM checker does. No account required.

Parked and defensive domains are also the easiest to forget at renewal time, and a lapsed one can be re-registered by anyone. Check each domain's expiry with the free Domain Expiry Checker so a domain you locked down does not quietly drop.

For continuous monitoring across many parked domains at once, ShieldMarc's MSP plan groups TLD variants of one brand into a single domain slot. That means a brand with .com, .co.uk and .org parked variants does not triple your bill.

We use optional analytics cookies (Google Analytics) to understand how visitors use the site. Essential cookies are always on. Privacy policy