Skip to content
AdminKit

Parked domain

What is Parked domain?

A parked domain is a registered domain that runs no real service: at most a placeholder web page, and no email. AdminKit's SPF check, DMARC check and MX lookup show whether it still publishes the records that stop spoofing: SPF -all, DMARC p=reject and a null MX.

By AdminKit team, Netbase JSC · Updated

M3AAWG’s Protecting Parked Domains Best Common Practices describes parked domains as names registered with no immediate plan to use them, or to use them only in a limited way. A common reason is a defensive registration: a brand registers a name, often a typosquatting variant of its own, so that nobody else can. A domain that only hosts a website and has no mail service is treated the same way, because it should never send or receive email either.

Why does a domain with no mail still need SPF, DMARC and a null MX?

A receiving server cannot tell that a domain is unused just because it has no mail server. Without records saying otherwise, anyone can put the domain in a From address and the receiver has nothing to check it against. The UK government’s guidance to protect domains that do not send email says criminals can use unprotected domains for spoofing and phishing, and asks for the same set of records M3AAWG lists:

  • An SPF record with only -all, so no server is allowed to send for the domain.
  • A DMARC record with p=reject. With SPF failing for every sender and no usable DKIM key, every message using the domain fails DMARC.
  • A null MX record, defined in RFC 7505, so senders know the domain accepts no mail.

A minimal set for a parked domain, with example.com as a placeholder, looks like this:

example.com.          TXT  "v=spf1 -all"
_dmarc.example.com.   TXT  "v=DMARC1; p=reject"
example.com.          MX   0 .

M3AAWG makes the aggregate report address (rua) optional for a parked domain, since there is no real mail stream to tune. The UK guidance notes that some DNS providers cannot create a null MX, so the SPF and DMARC records matter even when that one is missing. A parked domain is the opposite of a catch-all address: one accepts mail for every address, the other for none.

To confirm the setup, AdminKit’s SPF check explains how strict the domain’s “all” mechanism is, its DMARC check shows whether the policy is reject or only monitoring, and its MX lookup reports a null MX explicitly. Parked domain is part of AdminKit’s email authentication cluster; the full AdminKit glossary lists other related terms.

Frequently asked questions

Why would anyone send spoofed mail from a domain that sends no mail?

Because nobody is watching it. M3AAWG's parked domains best practice says that not publishing records which signal a domain sends and receives no mail gives third parties a chance to abuse it, and that domains similar to well-known ones are especially exposed. The UK government's guidance says criminals can use unprotected domains for spoofing and phishing.

Should a parked domain publish a DKIM record?

The two main sources differ. M3AAWG says to publish no DKIM record at all, so any forged signature fails because there is no public key. The UK government's guidance asks for an empty wildcard DKIM key record with p= left blank and for all existing selectors to be revoked. Either way, no valid DKIM key for the domain should be left in DNS.

Do the records need to cover subdomains too?

Yes, if the subdomains are not used for mail either. M3AAWG suggests wildcard SPF and null MX records for subdomains, and the UK guidance uses sp=reject in the DMARC record so the reject policy also covers subdomains. If a subdomain does send mail, it needs its own normal SPF, DKIM and DMARC setup instead.

Who can people contact about a domain that accepts no email?

M3AAWG notes that role addresses like postmaster@ cannot work on a domain with a null MX, and recommends using the contact mailbox in the domain's SOA record instead.