03 Nov 20265 minutes read
Email Authentication After an Acquisition: A Step-by-Step Guide

Email authentication after an acquisition overview:
- Inventory first: List every domain and sending service before you change any policy.
- Standardize email authentication: Set one baseline for every domain, then fix the records that keep a domain from meeting it.
- Check alignment: DMARC passes only when SPF or DKIM passes and aligns with the “From” domain.
- Enforce in stages: Move from p=none to p=quarantine to p=reject only after reports show every legitimate sender passing.
- Keep monitoring: New platforms and SaaS tools can break SPF and DKIM alignment.
An acquisition adds domains, email platforms, and sending services that your security team didn't set up and may not know exist. Any of them can be used to send email that appears to come from your combined organization. Email authentication after an acquisition determines whether that email is blocked or reaches inboxes.
The acquired company's email authentication policies rarely match yours. Some domains have no DMARC record, some sit at p=none, and some have SPF records that fail once both businesses' sending services are combined. Fixing this means applying the same email authentication policies to every domain without blocking legitimate email for either organization.
This guide covers five steps: inventory, consolidation, alignment, staged enforcement, and ongoing monitoring.
Explore how Sendmarc's DMARC Management gives your security team one view of every acquired domain and sender, so you can see which email authentication policies need to change before you touch a single DNS record.
The Risk of Weak Email Authentication After an Acquisition
Acquired companies usually bring legacy, regional, and parked domains. They also bring sending services that a former IT team approved without documenting, and tools that marketing, HR, and finance teams set up on their own. After the deal, your team is responsible for all of them, including the ones it doesn't know exist.
Attackers target this complexity. Without an enforced DMARC policy, nothing instructs receiving servers to reject unauthenticated email sent from an acquired domain. The people who receive it are the acquired business's customers, suppliers, and partners, and they trust the brand in the "From" line. Inbound email filtering doesn't help here, because the people at risk sit outside your organization.
Full enforcement doesn't stop attackers from trying. It blocks unauthenticated email from reaching inboxes.
How to Secure Email Authentication After an Acquisition
Step 1: Inventory Domains and Senders First
Build a complete list before you change any policy. A single missed sender is how legitimate email gets blocked later.
Document four things about the acquired company's email environment:
- Domains: include parked and legacy domains
- Records: current DMARC, SPF, and DKIM records
- Senders: every service that sends email
- Owners: one named owner per domain and sender
For domains with no DMARC record, publish one at p=none with a reporting address. DMARC aggregate reports from receiving servers then show which sources send email as that domain, including sources nobody listed.
Step 2: Standardize Email Authentication
Set one baseline for every domain in the combined business: a DMARC record, a target policy, and a reporting address. Then fix any record that keeps a domain from meeting that baseline.
SPF needs the most care. A domain can publish only 1 SPF record, and publishing 2 causes SPF to fail. SPF also allows a maximum of 10 DNS lookups. Adding the senders of both organizations to a single record can exceed that limit, which makes SPF fail for every message.
DKIM needs less change. Each sending service signs with its own key under a selector. Keep the acquired company's selectors in place until you confirm that no service still uses them. Before you replace a key, publish the new selector.
Step 3: Fix SPF and DKIM Alignment After an Acquisition
DMARC passes only when SPF or DKIM passes, and the authenticated domain aligns with the domain in the visible "From" address. A message can pass SPF and DKIM and still fail DMARC.
Third-party services often send with their own return-path domain and sign with their own DKIM domain, so neither aligns with the "From" domain.
Step 4: Move to DMARC Enforcement in Stages
Move each domain from p=none to p=quarantine and then to p=reject, but only after aggregate reports show every legitimate sender passing with alignment. Start with domains that don't send email, because there's no legitimate mail to disrupt. Publish p=reject and an SPF record that authorizes no senders on those domains.
Move sending domains next, starting with the lowest volume. Check that billing, password reset, and customer notification emails are authenticated before you tighten policy on the sending domains. Work domain by domain so one misconfigured sender doesn't hold up the rest.
Step 5: Keep Monitoring After Enforcement
Email authentication after an acquisition doesn't end when the last domain reaches p=reject. Teams migrate platforms and add SaaS tools, and each change can break SPF and DKIM alignment. Review DMARC aggregate reports continuously, and require every new sending service to be authenticated before it goes live.
How Sendmarc Can Help
Acquisitions add workload to security and IT teams that are already stretched. Few teams have the capacity to inventory senders, fix SPF and DKIM alignment, and manage staged enforcement across inherited domains while integration work continues.
Sendmarc takes that work on and addresses the specific problems acquisitions create:
- Unknown senders and shadow IT: DMARC Management identifies legitimate and unauthorized senders across every acquired domain and business unit.
- Inconsistent email authentication policies: The Sendmarc Platform shows the DMARC status of every domain in one place, so your team can apply the same policies everywhere and catch misconfigurations before they become incidents.
- Risk of disrupting critical email: Sendmarc moves each domain from p=none to p=reject in stages, with hands-on implementation support, so critical communications keep flowing, and your team doesn't need in-house DMARC experts.
- Authentication that falls out of date: Sendmarc continues monitoring and optimization after full enforcement, so protection stays current as the combined environment changes.
Explore how Sendmarc takes acquired domains to p=reject with hands-on implementation support and continuous monitoring, so your team can finish integration without adding an email authentication project to its workload.


