Blog article

21 Oct 20267 minutes read

Author Profile PictureWaseem OsmanDMARC Practitioner

TXT Record Management for DMARC Enforcement at Enterprise Scale

Digital server with an information document in a cyber environment

Overview:

  • Records that are too narrow fail legitimate email, and records that are too broad can let email from sources you no longer control pass DMARC.
  • Multiple SPF records or more than 10 DNS lookups produce a permerror, so email then passes DMARC only through aligned DKIM.
  • Assign DNS record ownership to one team per responsibility, and keep a sender registry of every authorized sender.
HostTypeValue
@TXTv=spf1 include:_spf.vendor-a.example include:_spf.vendor-b.example ip4:192.0.2.10 ~all
  • A stale SPF include still authorizes that vendor’s infrastructure to send as your domain. RFC 9989 advises reviewing SPF records periodically to confirm they match current needs.
  • A stale DKIM selector keeps a valid public key published for a platform you no longer control. Remove it once you confirm the platform no longer signs for your domain.
  • Stale DNS records make audits harder because reviewers can’t tell which entries are intentional.
  • DNS changes: infrastructure or IT security applies every change to SPF, DKIM, and DMARC records
  • Sender onboarding: the requesting team supplies the SPF include value before the sender goes live
  • DMARC reports: security reviews aggregate reports and approves each policy change
  • Sender registry: a maintained list of every authorized sender per domain, with its SPF include, DKIM selector, and responsible team
  1. Inventory all domains and subdomains. Include parked, legacy, and acquired domains. Record whether each domain sends email, receives email, both, or neither.
  2. Audit existing DNS records. Confirm each domain has a single SPF record, and count its lookups with Sendmarc’s SPF record checker. List every published DKIM selector and match it to an active sender. Confirm that the rua mailbox receives reports.
  3. Assign DNS record ownership. Name a DNS change owner for each domain, and require a change request for every SPF, DKIM, or DMARC update.
  4. Progress the DMARC policy in stages. Start at p=none with a rua address, and use aggregate reports to identify every legitimate sender. Fix unaligned email streams, then move to p=quarantine and p=reject.
  5. Set a review schedule. Review SPF records whenever a sender is added or retired. Review DKIM keys after each key rotation and on a fixed schedule. Review aggregate reports regularly, and audit all DNS records for stale entries at least annually.
Share:

Subscribe to the Impersonation Brief. It's really from us.

Is Your Domain Protected?

Get your domain’s security score in seconds.
Check your impersonation, privacy, and branding ratings.

If you’re at risk of impersonation, one of our experts will be in touch to assist.

Useful Tools

DNS Lookup
Free toolNo sign-up

DNS Lookup

Use Sendmarc's DNS lookup tool to instantly analyze domain records, verify configurations, and detect DNS issues for better performance.

Email Header Analyzer
Free toolNo sign-up

Email Header Analyzer

Quickly analyze email headers with Sendmarc’s email header analyzer. Check SPF, DKIM, and DMARC results, detect phishing, and improve email deliverability.

Domain Checker
Free toolNo sign-up

Domain Checker

Use the Sendmarc domain checker to test against malicious use - free, no sign-up required, with results in under a minute.