Could someone fake your academy trust’s email?
On 9–10 Nov 2026 we read the public DNS of 1,472 email domains used by academy trusts in England. 747 of them (50.7%) would have fake email using the trust’s own domain delivered as normal, because they have no DMARC record, one set to p=none, or one receivers can’t use. 179 still send their DMARC reports to NCSC’s Mail Check, which no longer reads them. We name no trusts. These are observations, not accusations.
Why this matters
Anyone can put an organisation’s address in the “From” line of an email. DMARC is the published instruction that tells Gmail, Microsoft and other receivers what to do when a message claims to be from that domain but fails authentication:
p=reject: refuse it. Nobody sees the fake.p=quarantine: deliver it to spam or junk. Better, but people do check their junk folder.p=none, or no record at all: deliver it as normal. The domain owner may get reports, but the fake lands in the inbox.
Academy trusts email parents, staff and suppliers every day, about everything from trips to invoices. A fake from a trust’s real domain can ask parents for payments or personal details, or ask a supplier to change bank details, and it is hard to tell apart from the real thing.
What we observed (9–10 Nov 2026)
| DMARC policy | Domains | Share of 1,472 |
|---|---|---|
Reject (p=reject) | 251 | 17.1% |
| Quarantine, applied to all mail | 460 | 31.2% |
Quarantine, applied to only part of the mail (pct below 100) | 14 | 1.0% |
Monitoring only (p=none) | 354 | 24.0% |
| No DMARC record | 392 | 26.6% |
| A DMARC record receivers can’t use (for example two records) | 1 | 0.1% |
Reports going nowhere
NCSC’s Mail Check service stopped processing DMARC reports on 24 March 2025 and closed on 31 March 2026. Domains that still list its address are sending their reports to a service nobody reads, so whoever runs them gets no warning when someone sends email in their name.
179 trust domains (12.2%) still list Mail Check as the place to send DMARC reports, and 162 still list it for TLS reports.
This is not a finding that any trust has been impersonated, or that any is non-compliant. A trust may have good reasons for its current policy, for example while it finds every service that sends email in its name, such as payment, parent-communication and HR systems. Moving from p=none to p=reject is normally done in stages, reading the DMARC reports at each step.
Method
- List: every open multi-academy trust in England, plus single-academy trusts in the West Midlands and East Midlands, from the Department for Education’s Get Information About Schools register, with each trust’s website and published email domain.
- Domains: the domain of each trust’s website, plus its email domain where that was different. One row per domain; 1,472 had at least one MX record (they receive email), and only those are counted.
- Query: public DNS only, over DNS-over-HTTPS to Cloudflare and Google’s public resolvers, at a paced rate, between 9 and 10 November 2026. We made no connections to trust servers. A random sample was re-checked live on 10 November and matched.
- Classification: by the
p=tag of the domain’s DMARC record. “Fake email delivered” means no record,p=none, or a record receivers can’t use. Apctbelow 100 is shown separately and not counted as delivered. - Data: aggregate totals only, with no trust or domain names, in this CSV (CC BY 4.0).
Limits
- This is a snapshot from 9–10 Nov 2026. DNS changes all the time.
- Single-academy trusts outside the Midlands aren’t included, so this covers multi-academy trusts nationally but not every trust.
- Schools inside a trust sometimes send from their own domains, which this study doesn’t cover.
- DMARC is only one layer. A receiver can still block a fake for other reasons, and a trust on
p=rejectcan still be imitated with a look-alike domain.
Could someone fake your email?
FaultyPacket’s free scan reads your domain’s public DNS and tells you, in plain English, whether fake email using your name would be blocked, sent to junk or delivered. You don’t need to sign up.
Journalists and researchers can ask for the method note or domain-level detail at [email protected]. Requests are reviewed by a person.
© 2026 FaultyPacket™ · UK/EU DNS and email security · Published November 2026 · All figures observed 9–10 Nov 2026