Skip to content

Parked Domains (Null MX) ​

A parked domain is a domain that doesn't receive email. This includes domains registered to prevent cybersquatting, brand protection domains, or domains used only for websites without email functionality.

Even if your domain doesn't receive email, it can still be abused by attackers to send spoofed emails. Properly configuring parked domains prevents this abuse.

The Problem ​

Without proper configuration, attackers can:

  • Send phishing emails appearing to come from your parked domain
  • Damage your brand reputation
  • Use your domain in spam campaigns
  • Bypass spam filters by exploiting unconfigured domains

Null MX (RFC 7505) ​

The Null MX record is a standard way to explicitly declare that a domain does not accept email.

example.com.  IN  MX  0 .

This tells mail servers: "Don't try to deliver email here. There are no mail servers."

How It Works ​

Sender                           Receiver
  │                                  │
  │  "I want to send to             │
  │   user@example.com"             │
  │ ────────────────────────────────>│
  │                                  │
  │                           Look up MX
  │                           for example.com
  │                                  │
  │                           Found: MX 0 .
  │                           (Null MX)
  │                                  │
  │  "550 Mail not accepted"        │
  │ <────────────────────────────────│
  │                                  │

The sender immediately knows not to deliver, without wasting resources trying to connect to a non-existent mail server.

Complete Parked Domain Configuration ​

For full protection, configure all of these DNS records:

1. Null MX Record ​

example.com.  IN  MX  0 .

Explicitly declares no mail servers exist.

2. SPF Record ​

example.com.  IN  TXT  "v=spf1 -all"

The -all (hard fail) means "no servers are authorized to send email for this domain."

3. DMARC Record ​

_dmarc.example.com.  IN  TXT  "v=DMARC1; p=reject; rua=mailto:abc123@reports.mailshield.app"

Key points:

  • p=reject tells receivers to reject any email claiming to be from this domain
  • rua= must point to an address on a different domain that receives email. Your MailShield Reporting address (shown on the domain's Overview) works: replace abc123@reports.mailshield.app with it
  • The reports show whether anyone is trying to abuse your domain

4. DKIM Wildcard (Optional) ​

*._domainkey.example.com.  IN  TXT  "v=DKIM1; p="

The empty p= value revokes all DKIM keys, explicitly stating no valid signatures exist.

Parked Domains in MailShield ​

MailShield doesn't decide on its own that a domain is parked. You choose Parked domain as the usage type when you add the domain, or later under Domain → Settings → Email Configuration. The usage type decides how the domain is scored.

What the MX check does detect is whether the domain accepts mail:

ResultMeaning
Null MXAn explicit MX 0 . record (RFC 7505)
No MX recordsThe domain has no MX records
UnreachableMX records exist, but no MX host accepts connections
UnresolvableThe MX host names don't resolve to IP addresses
Relay deniedThe MX hosts accept connections but refuse mail for the domain

For a parked domain without a null MX, Checks → MX shows the records to publish. If a domain set to send and receive mail appears not to accept mail, the MX page flags it, so you can check the usage type or the test mailbox.

Scoring for Parked Domains ​

Parked domains are scored differently than active mail domains:

ComponentPointsRequirement
MX10Null MX or no MX records (5 when MX records exist but can't receive mail)
SPF15v=spf1 -all (8 for ~all)
DMARCUp to 25p=reject (15) or p=quarantine (10), plus a rua address (+5), plus your MailShield Reporting address in rua or a ruf address (+5)
DNSSEC10DNSSEC enabled and valid

The points add up to 60, which MailShield scales to 100. Components that don't apply to parked domains (DKIM, MTA-STS, TLS-RPT, BIMI and DANE) aren't counted.

Without DNSSEC, a parked domain tops out at 50 of 60 points, which shows as 83 (a B). With DNSSEC, a well-configured parked domain scores 100. See Security Score.

DMARC Reporting for Parked Domains ​

Even though your domain doesn't receive email, you should still configure DMARC reporting. This helps you:

  • Detect if anyone is attempting to spoof your domain
  • Identify misconfigured systems that might legitimately be sending as your domain
  • Maintain visibility into domain abuse

Important

Since your parked domain has null MX (or no MX), the DMARC rua and ruf addresses must point to a different domain that can receive email.

_dmarc.parked.example.com.  IN  TXT  "v=DMARC1; p=reject; rua=mailto:dmarc@primary.example.com"

When reports go to another organizational domain, that domain must authorize it with a record like this:

parked.example.com._report._dmarc.primary.example.com.  IN  TXT  "v=DMARC1;"

If you use your MailShield Reporting address, you don't need to do this: MailShield publishes the authorization record for you.

Common Scenarios ​

Brand Protection Domains ​

You own mybrand.io but only use mybrand.com. Configure mybrand.io as a parked domain to prevent abuse.

Typosquatting Protection ​

You've registered mycomapny.com (typo of mycompany.com) to protect users from phishing. Configure it as a parked domain.

Expired Email Service ​

Your domain used to have email but no longer does. Convert it to a parked domain configuration rather than leaving old MX records pointing to nowhere.

Website-Only Domains ​

Your domain hosts a website but uses a third-party email service (like Google Workspace) on a different domain. If no email service exists on this domain, configure it as parked.

Migration from Active to Parked ​

If transitioning a domain from active email to parked:

  1. Notify users about the email shutdown
  2. Update SPF from listing authorized senders to -all
  3. Update DMARC to p=reject (if not already)
  4. Replace MX records with null MX (0 .)
  5. Optionally add the DKIM wildcard revocation

TIP

Keep DMARC reporting active during and after the transition to monitor for any issues.

Best Practices ​

Do ​

  • Use null MX for explicit "no email" signaling
  • Always configure SPF with -all for parked domains
  • Set DMARC to p=reject
  • Keep DMARC reporting active to monitor abuse
  • Regularly review DMARC reports for attempted spoofing

Don't ​

  • Leave parked domains without email security records
  • Use ~all (soft fail) for parked domains. Use -all (hard fail) instead
  • Forget to update DMARC rua to point to a working email address
  • Assume "no MX records" is enough: publish a null MX to make it explicit

Next Steps ​

Monitor and secure your email domains.