MSPs
Stop Email Scammers Using Your Parked Domains (SPF, DMARC, MX)
Rodney Hall, COO— AI-assisted and reviewed prior to publication.

Publish three DNS records on every domain that should never send mail: an SPF record of v=spf1 -all, a DMARC policy of p=reject at the _dmarc subdomain with a reporting address, and a null MX record pointing to . with priority 0. These records tell receiving mail servers to reject all spoofed email instantly.
Why parked domains are spoofing magnets
Parked domains that don't send email are prime spoofing targets because they typically have no DMARC record and are the easiest to spoof (dmarcreport.com). Without protective DNS records, anyone can send email claiming to come from them (sh.consulting). The domains sit unused in your portfolio, nobody monitors them, and attackers know it. They scan for domains with missing authentication records, then forge sender addresses that pass right through to inboxes because there is no policy telling receivers to block them.
Every unprotected domain in your portfolio is a free pass for attackers. Defensive domains registered to block typosquatters or brand variants fall into the same category. If you bought alternativebranding.com to protect your brand but never configured email authentication, an attacker can spoof @alternativebranding.com in a phishing campaign and the domain's real owner, you, will never know unless someone reports it.
What does each of the three records do?
The SPF record of v=spf1 -all is a DNS TXT record on the domain itself. The -all indicator tells the server to reject all non-compliant emails, and with this type of SPF record, no IP addresses or domains are allowed, so all emails are considered non-compliant.
The DMARC record lives at _dmarc.yourdomain.com as a TXT record. A DMARC reject policy tells receiving mail servers to block any email that fails DMARC authentication, set by publishing a DNS TXT record on your _dmarc subdomain with the p=reject tag (valimail.com). A minimal record for a parked domain looks like v=DMARC1, p=reject, rua=mailto:dmarc@youractivedomain.com, where the rua address points to a mailbox you actually monitor. At p=reject, a message that fails DMARC is bounced at the door and never lands in an inbox or a spam folder (palisade.email).
The null MX is defined in RFC 7505. An RFC 7505 null MX record is an MX record with priority 0 and an empty hostname (a single dot), and this must be the only MX record published for the domain. It explicitly declares the domain accepts no inbound mail. If a domain has no MX records, mail servers should check for an A or AAAA record and attempt delivery there, but a null MX record prevents this fallback behavior (support.dnsimple.com).
How do I apply these to a whole portfolio?
Most DNS providers let you manage records in bulk through their API or a CSV upload. For a portfolio of 50 parked domains, manually adding three records per domain is 150 edits. Automate it. Export your current zone files, generate the three records per domain with a script, and push the update back. If your DNS provider is Cloudflare, Route 53, or Azure DNS, all three support Terraform or API-driven updates that let you define the records once and apply them to every domain in scope.
For the DMARC rua reporting address, point every parked domain's reports to a single mailbox on your active domain. You need to authorize this in DNS: publish a TXT record at parked-domain.com._report._dmarc.youractivedomain.com containing v=DMARC1, or use a wildcard record ._report._dmarc.youractivedomain.com that covers every parked domain at once. Without this authorization step, most receivers will ignore the rua address and you will get no reports.
If you manage client portfolios at scale, ActiScore's pricing (/pricing) starts at $79/month for 250 scans that check SPF, DMARC, DKIM and TLS health across domains. The security category in every scan reports whether these three records are present and correctly configured.
What happens after I publish the records?
Nothing breaks. The domains already send no legitimate mail, so there is no delivery to disrupt. Spoofed email claiming to come from those domains will start getting rejected at SMTP time by any receiver that checks DMARC. You will see the attempts in your aggregate reports if you configured the rua address. Each report lists the sending IP, the volume, and the DMARC result. If you see a spike from an unexpected IP, you know someone tried to spoof one of your parked domains and the policy stopped it.
DNS propagation takes minutes to hours depending on TTL. Once the records are live, run the free AI-visibility check (/check) on a sample domain to confirm the SPF and DMARC records resolve correctly. The scan shows whether the policy is published and what a receiving mail server will see when it queries your domain.
Does this work for subdomains too?
Yes, but you need to publish the records on each subdomain explicitly or set a subdomain policy in your DMARC record. The sp=reject tag in a DMARC record applies the reject policy to all subdomains that do not have their own DMARC record. A complete parked domain record then looks like v=DMARC1, p=reject, sp=reject, rua=mailto:dmarc@youractivedomain.com. SPF and the null MX do not inherit, so if you have subdomains that could be spoofed (like mail.parkeddomain.com or info.parkeddomain.com), publish the same three records on each one.
For wildcard coverage, some DNS providers let you publish .parkeddomain.com records, but this only works if the subdomain is queried and your DNS server responds with the wildcard. It is cleaner to publish the records on the apex domain and use sp=reject to cover subdomains in DMARC.
What if I need to send from a parked domain later?
Remove the three records before you send. RFC 7505 is direct about it: do not publish a null MX on a domain you actually send mail from. Replace v=spf1 -all with an SPF record listing your actual sending IPs or services (like v=spf1 include:_spf.google.com -all if you use Google Workspace), change the DMARC policy from p=reject to p=none while you test, and either remove the null MX or replace it with a real mail exchanger. If you skip this step and try to send with the locked-down records still published, every message you send will be rejected.
The safe path is to treat the records as a lock. When a domain is parked, lock it. When you need it for email, remove the lock first, then configure your sending infrastructure, then gradually move DMARC from p=none to p=quarantine to p=reject after you have confirmed all legitimate mail passes. The guide (/guide) walks through that progression for active sending domains.
Common questions
What DNS records do I need to stop spoofing on parked domains?
You need three DNS records on every parked domain: an SPF record of v=spf1 -all published as a TXT record on the domain itself, a DMARC policy of p=reject published at the _dmarc subdomain with a reporting address, and a null MX record with priority 0 pointing to a single dot. These three records work together to tell receiving mail servers to reject all email claiming to come from your parked domain, preventing attackers from spoofing your unused domains in phishing campaigns.
Why are parked domains targeted for email spoofing?
Parked domains are prime spoofing targets because they typically have no DMARC record and are the easiest to spoof. Without protective DNS records, anyone can send email claiming to come from them, and the domains sit unused with nobody monitoring them. Attackers scan for domains with missing authentication records, then forge sender addresses that pass right through to inboxes because there is no policy telling receivers to block them. Every unprotected domain in your portfolio is a free pass for attackers.
How do I apply SPF DMARC and null MX to multiple domains at once?
Most DNS providers let you manage records in bulk through their API or CSV upload. Export your current zone files, generate the three records per domain with a script, and push the update back to avoid manually adding 150 edits for 50 domains. If your DNS provider is Cloudflare, Route 53, or Azure DNS, all three support Terraform or API-driven updates that let you define the records once and apply them to every domain in scope, automating the entire portfolio protection process.
Will publishing these records break anything on my parked domains?
Nothing breaks because the domains already send no legitimate mail, so there is no delivery to disrupt. Spoofed email claiming to come from those domains will start getting rejected at SMTP time by any receiver that checks DMARC. DNS propagation takes minutes to hours depending on TTL, and once the records are live you can run a scan to confirm the SPF and DMARC records resolve correctly and see what a receiving mail server will see when it queries your domain.
What if I need to send email from a parked domain later?
Remove the three records before you send, because RFC 7505 is direct about not publishing a null MX on a domain you actually send mail from. Replace v=spf1 -all with an SPF record listing your actual sending IPs or services, change the DMARC policy from p=reject to p=none while you test, and either remove the null MX or replace it with a real mail exchanger. If you skip this step and try to send with the locked-down records still published, every message you send will be rejected.
