Email authentication at 561 hiring B2B startups
We read the public DNS of 561 B2B startups that were hiring in November 2026 and checked whether they publish SPF, DKIM and DMARC. Measured 18 November 2026.
| Measure | Domains | Share |
|---|---|---|
| Domains checked | 561 | 100% |
| SPF, DKIM and DMARC all present | 496 | 88.4% |
| Missing at least one of the three | 65 | 11.6% |
| DMARC record present | 529 | 94.3% |
| DMARC policy reject | 165 | 29.4% |
| DMARC policy quarantine | 203 | 36.2% |
| DMARC policy none (monitoring only) | 160 | 28.5% |
| No DMARC record | 32 | 5.7% |
| One valid-form SPF record | 531 | 94.7% |
| No SPF record | 28 | 5.0% |
| SPF over the 10-lookup limit | 5 | 0.9% |
| DKIM key found at a probed selector | 515 | 91.8% |
| Mail hosted at Google Workspace | 515 | 91.8% |
| Mail hosted at Microsoft 365 | 20 | 3.6% |
What these records do
Receiving mail systems use three public DNS records to decide whether to trust a company's email. SPF lists who may send for the domain, DKIM signs the message and DMARC says what to do when the checks fail. Google and Yahoo have required all three from bulk senders since February 2024. Among companies that publish DMARC, 448 of 529 (84.7%) also ask for aggregate reports.
Sample and method
The list comes from the open dataset of the public Y Combinator company directory. We kept active companies with a website, marked as hiring, with 8 to 150 people, in B2B, industrials, fintech, healthcare, real estate and construction or government, in North America or Europe, excluding sales and marketing software. That leaves 561 domains. Reapline is not affiliated with Y Combinator, and the sample is not random.
For each domain on 18 November 2026 we queried public DNS only: MX, SPF (record count and lookup limit), DMARC (policy and reporting address) and DKIM at 28 common selectors. Nothing was sent to any company and no company is named. Download the anonymised CSV or the script (Node.js, DNS queries only) to repeat it.
Limits
- DKIM was probed at 28 selectors, so the DKIM gap probably overstates real absence.
- SPF was judged on form, not on whether it lists every service the company uses.
- Nine domains have no MX record and may not send email at all.
- It is a snapshot of one group of fast-growing companies. It says nothing about other company types and we did not test inbox placement.
What to do if you send email from a company domain
Publish exactly one SPF record under 10 lookups, sign your mail with DKIM, and publish DMARC. Start at p=none, read the reports, and move to quarantine or reject once your own mail passes. Build the record with our DMARC record generator; the guide to deliverability covers the sending side.
Cite this
Reapline, Email authentication at 561 hiring B2B startups: SPF, DKIM and DMARC, 18 November 2026. https://reapline.com/research/email-authentication/
Questions
How many startups publish SPF, DKIM and DMARC?
88.4% (496 of 561) of the B2B startups we checked on 18 November 2026 publish all three. 11.6% are missing at least one.
How many enforce DMARC?
65.6% publish a DMARC policy of quarantine or reject. 28.5% publish p=none, which only monitors. 5.7% publish no DMARC record at all.
Is the DKIM figure reliable?
It is the least certain number. A sender can use any selector name and we probed 28 common ones, so "not found" means not found at those selectors.
