Meet the company
A US company on the road to an IPO, sending at real scale: marketing mail, product mail, and reply traffic across a root domain and several sending subdomains. The company's name stays off this page, as it should.
The challenge
Deliverability had no single owner. SPF, DKIM, DMARC, spam filters and inbox placement were everybody's side job, which meant they were nobody's job. And the estate was buried in noise: 43 domains sat in the company's DNS account, parked, legacy and live all mixed together, so first the actual sending estate had to be separated out.
The estate mostly looked fine, and mostly was, except for the detail attackers love: one reply subdomain still sitting at DMARC p=none, the setting that watches spoofing happen and does nothing about it.
For a company approaching an IPO, a spoofable domain is not a technical footnote. It is a headline waiting for a date.
The solution
One owner, whole estate
For about six months from the start of 2026, one operator held complete charge of the company's email deliverability: DKIM, DMARC and SPF records, spam filter behaviour and inbox placement, across every sending domain.
Audit every domain, not the average
Each of the 8 sending domains was checked individually on public DNS. Seven were already enforcing at quarantine: the root domain, four sending subdomains, and two mail domains on sister brands. Estates fail at their weakest domain, not their average one, so the audit went domain by domain until the weak one surfaced: the reply subdomain, its record reading simply v=DMARC1; p=none, with nothing else set.
Raise it, then verify it live
On September 28, 2026, the reply subdomain's DMARC was raised to v=DMARC1; p=quarantine; pct=100, with an aggregate reporting address added, and the change was verified live on public DNS across three separate checks.
The results
After the fix, every sending domain on the estate enforces DMARC at quarantine: the root, all sending subdomains, the two sister-brand mail domains, and the reply subdomain that had been the open door.
One item stayed open and was flagged openly rather than buried: DKIM signing on that reply subdomain could not be confirmed from public DNS, because the common selectors returned no key. It was recorded as a follow-up for the sending platform's owner, in writing, the same day.
The return on one record change: a pre-IPO company whose every sending domain now enforces against spoofing. The fix cost an audit and an edit. The gap, at IPO visibility, would have been priced in headlines, and we will not invent a dollar figure for that. The honest ROI is risk removed before it was priced by someone else.
FAQ
Why does p=none not protect a domain?
Because p=none is monitor mode. It asks receivers to send reports about spoofed mail, but tells them to deliver it anyway. Quarantine and reject are the settings that actually stop spoofing.
How do you raise enforcement safely?
Confirm SPF and DKIM alignment first on real sending traffic, read the aggregate reports for anything legitimate that would break, then raise the policy and verify the new record on public DNS. Skipping the report reading is how teams quarantine their own invoices.
What should be checked monthly?
DMARC policy and alignment on every sending domain, DKIM signing status, SPF record size and lookups, and blocklist status for sending IPs. Estates drift; the monthly check is what catches it.
