schedule 14-min read

DMARC for Schools and Universities

DMARC AI editorial team · Last updated

DMARC for schools, academy trusts and universities: why education is targeted, the sender inventory, multi-domain rollout table and an MSP checklist.

01

How should schools and universities approach DMARC?

Schools and universities should treat DMARC as an inventory project first and a DNS change second. Publish p=none with aggregate reporting on every domain, list every platform that sends as the school or university, fix SPF and DKIM alignment for each, then move each domain to p=quarantine and p=reject. Trusts and federations repeat this per domain.

DMARC (Domain-based Message Authentication, Reporting and Conformance) builds on SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail). This guide covers why education is a target, the typical sender inventory, department subdomains, multi-academy trusts with many domains, UK guidance from the Department for Education (DfE) and the National Cyber Security Centre (NCSC), a rollout table and a checklist for MSPs (managed service providers). For protocol basics, start with the DMARC guide.

02

Key takeaways

  • Phishing dominates education incidents in the UK government's own survey data, and impersonation is far more common in further and higher education than in business.
  • The DfE cyber security standard asks schools to reduce the risk of "imitation emails" and points to NCSC email guidance, but it does not name DMARC.
  • Most rollout blockers in education are third-party platforms (parent communication, payments, admissions, alumni) that send as the school without aligned DKIM.
  • Trusts and universities need a per-domain plan, including parked and legacy school domains, not one record copied everywhere.
03

Why are schools and universities targeted by email spoofing?

Schools and universities are targeted because their domains are trusted by parents, students, staff and suppliers, and they handle payments, personal data and research. The UK Cyber Security Breaches Survey 2025/2026 education annex shows breach rates well above the business average.

The survey (fieldwork August to December 2025, published 30 April 2026) reports these figures for UK institutions that identified a breach or attack in the previous 12 months:

Institution type Identified a breach or attack Of those, impersonation
Primary schools 49% 31%
Secondary schools 73% 44%
Further education colleges 88% 79% (FE and HE combined)
Higher education institutions 98% 79% (FE and HE combined)

The report states that "phishing was overwhelmingly the main threat to schools (90% of primary schools and 96% of secondary schools)". The survey counts only incidents institutions identified themselves, and the education samples are unweighted, so treat the figures as indicative rather than precise. For comparison, 28% of UK businesses that identified an attack reported impersonation.

Not all of that is domain spoofing. Much impersonation uses lookalike domains or compromised accounts, which DMARC does not stop. What DMARC at p=reject does stop is mail that uses the exact school domain in the From header without passing aligned SPF or DKIM. In education, typical lures include:

  • fake invoice or bank detail changes sent to the finance office or bursar
  • fake trip, lunch or uniform payment requests sent to parents
  • fake account verification or fee notices sent to students
  • fake donation appeals sent to alumni
  • fake head teacher or vice-chancellor requests sent to staff
04

What does a typical education sender inventory look like?

A typical education sender inventory has five to fifteen platforms per domain, most of them outside the IT team's direct control. The core mail platform is usually Google Workspace for Education or Microsoft 365 with education licences. Everything else is a third-party service that may send as the school's domain.

Group senders by category, then confirm each one in aggregate reports.

Category What it sends Common alignment problem
Core mail (Google Workspace for Education, Microsoft 365) Staff and student mail DKIM never enabled for the custom domain, or a second tenant domain left unauthenticated
MIS and parent communication platforms Absence alerts, newsletters, reports to parents Sends with the school's From address but signs DKIM with the vendor's domain
Payment platforms Receipts, payment requests, balance reminders Uses its own bounce domain, so SPF never aligns; custom DKIM not set up
Learning management system (LMS) Assignment and grade notifications Often sends as noreply@ the school domain from vendor infrastructure
Admissions and applicant systems Offers, interview invites, document requests Run by a separate office, missing from IT's list entirely
Alumni, fundraising and marketing platforms Appeals, event invites, newsletters High volume, needs its own subdomain and DKIM
Library, catering, transport, room booking Reminders and confirmations Small vendors with limited authentication support
Devices and on-premises systems Scanners, printers, door entry, CCTV alerts Direct relay with no DKIM; see Microsoft 365 Direct Send and printers

For each sender, record the owner, the From domain, the envelope (bounce) domain and the DKIM d= domain. DMARC passes only when SPF or DKIM passes for a domain that aligns with the From domain. The third-party sender guide covers how to ask vendors for custom DKIM.

Check what is already published before you start:

dig +short TXT _dmarc.example-school.org.uk
dig +short TXT example-school.org.uk | grep spf1
dig +short TXT google._domainkey.example-school.org.uk

On Windows:

Resolve-DnsName -Type TXT _dmarc.example-school.org.uk
Resolve-DnsName -Type TXT selector1._domainkey.example-school.org.uk

Google documents the core platform steps in Set up DMARC, and Microsoft in Set up DMARC for Microsoft 365. Our Google Workspace implementation guide and Microsoft 365 implementation guide walk through both for MSPs.

05

How should universities handle department subdomains?

Universities should give each department or service that sends independently its own subdomain, with its own SPF and DKIM, and decide deliberately whether it inherits the parent policy. DMARC policy is inherited by subdomains unless a subdomain publishes its own record, but SPF and DKIM are not inherited.

Microsoft's guidance makes the same point: a parent DMARC record "automatically covers all subdomains (including nonexistent subdomains) that don't have their own DMARC TXT record", while "each subdomain requires an SPF and DKIM record for DMARC". In practice:

  • Move bulk senders (alumni, marketing, events) to a subdomain such as news.example.ac.uk, so a misconfigured campaign tool cannot damage reputation for the main staff domain.
  • Give research groups and faculties that run their own servers a subdomain with a named owner, rather than letting them send as the root domain.
  • Use the sp tag to set a subdomain policy separately while departments catch up, and np (defined in RFC 9989) to reject mail from subdomains that do not exist.

An example parent record partway through a rollout:

_dmarc.example.ac.uk.  3600 IN TXT "v=DMARC1; p=quarantine; sp=none; np=reject; rua=mailto:dmarc-reports@example.ac.uk"

See DMARC for subdomains, the np tag and subdomain or separate domain for bulk email for the detail.

06

Why do student mail and aliases complicate DMARC?

Student mail complicates DMARC because it creates large volumes of forwarding, list traffic and alias domains that IT did not design. Students and staff auto-forward to personal mailboxes, clubs run mailing lists, and former students keep alumni aliases that forward elsewhere. Each path can break SPF alignment.

Common patterns to look for in aggregate reports:

  • Separate student domains. Many institutions run students on students.example.ac.uk or a separate domain. Each needs its own records and its own policy decision.
  • Lifelong or alumni aliases. Forwarding aliases rewrite nothing, so SPF fails at the final receiver. Aligned DKIM usually survives if the message body is untouched.
  • Mailing lists and clubs. Lists that add footers or change subject lines break DKIM. Check whether your list software rewrites the From header for DMARC-protected domains.
  • Legacy and acquired domains. Old college names, merged departments and conference domains that still receive or send mail.

Forwarding failures look alarming at p=none but are normal. The question is whether the message also had aligned DKIM. Read DMARC and email forwarding and ARC explained before you treat forwarders as a blocker.

07

How do multi-academy trusts and university groups manage many domains?

Multi-academy trusts and university groups should manage DMARC as a portfolio: one inventory, one reporting address, one change process, and a separate policy per domain. Schools joining a trust often keep their own domain, MIS and parent platform for years, so senders differ school by school.

Practical rules for a trust or federation:

  1. List every registered domain, including old school names, pre-conversion domains, event and campaign domains, and the tenant domain (*.onmicrosoft.com for Microsoft 365).
  2. Lock down domains that never send with v=DMARC1; p=reject; and an SPF record of v=spf1 -all. Microsoft recommends this for registered but unused domains, including an unused *.onmicrosoft.com domain.
  3. Centralize reporting. Send aggregate reports for every school to one mailbox or platform so the trust IT team sees all domains together.
  4. Stage schools individually. A school with a simple estate can reach p=reject in weeks; one with a legacy MIS mailer may take a term.
  5. Agree ownership. Decide who in each school approves new senders, so business managers do not add platforms without telling IT.

The multiple domains guide and multi-tenant DMARC management cover the portfolio model in more depth.

08

What do UK DfE and NCSC guidance say about email authentication?

The DfE cyber security standard asks schools and colleges to check that email "reduces the risk of third parties being able to send imitation emails", and links to NCSC email security guidance. It does not name DMARC, SPF or DKIM. The NCSC guidance it points to is where DMARC appears explicitly.

DfE. The cyber security standards for schools and colleges are part of "Meeting digital and technology standards in schools and colleges". The email wording sits under data processing and security checks. Anti-spoofing is therefore an expectation, not a named control, and DMARC at enforcement is the standard way to show you meet it.

NCSC. The NCSC email security and anti-spoofing guidance sets out a staged plan: implement a DMARC policy of none, build SPF and DKIM, monitor reports, mark spoof emails as spam, then reject spoof emails. That maps directly onto the rollout table below.

Mail Check. Many schools and universities relied on the NCSC Mail Check service, which the DfE standard still references as a tool for email configuration and reporting. The NCSC retired Mail Check and Web Check on 31 March 2026. Institutions that used it for DMARC reporting need another aggregate report processor. See NCSC Mail Check replacement.

For public sector parallels, see DMARC for government domains.

US angle. US districts and colleges face the same mechanics. FERPA (the Family Educational Rights and Privacy Act) protects student records but does not mandate DMARC, so the practical driver is usually mailbox provider rules. Google's email sender guidelines require senders of more than 5,000 messages a day to personal Gmail accounts to align the From domain with SPF or DKIM, which covers large parent and alumni mailings. See Google, Yahoo and Microsoft sender requirements.

09

What does a DMARC rollout look like for a school or university?

A DMARC rollout for a school or university moves each domain through monitoring, alignment fixes, quarantine and reject, with a monitoring period at each step. RFC 9989 removed the pct tag, so there is no percentage ramp. Use t=y if you want a testing step, which asks receivers to apply the next lower policy.

Phase What to check Typical blockers in education
1. Discover Every domain has one v=DMARC1 record with p=none and an rua address; one SPF record per name Domains registered by schools or departments that IT does not know about; DNS held by a former supplier or the local authority
2. Inventory Every source IP in aggregate reports mapped to a known platform and owner Parent communication, payment and admissions platforms bought by non-IT staff
3. Align Core platform DKIM enabled; each third party signs with the school domain or moves to a subdomain; SPF under 10 lookups Vendors without custom DKIM; SPF over the lookup limit after adding every platform
4. Quarantine p=quarantine (optionally t=y first); watch failures for two to four weeks Term-start mailings, exam results, admissions cycles: avoid changes in these windows
5. Reject p=reject, sp and np set deliberately; legacy domains locked down Forwarding and list traffic that people fear losing; aligned DKIM normally resolves it
6. Maintain New senders go through change control; reports reviewed monthly Staff turnover, new platforms added mid-year, trust growth

Records at each stage look like this:

; Phase 1: monitoring
_dmarc.example-school.org.uk. IN TXT "v=DMARC1; p=none; rua=mailto:dmarc@example-school.org.uk"

; Phase 4: quarantine
_dmarc.example-school.org.uk. IN TXT "v=DMARC1; p=quarantine; rua=mailto:dmarc@example-school.org.uk"

; Phase 5: reject, with non-existent subdomains rejected too
_dmarc.example-school.org.uk. IN TXT "v=DMARC1; p=reject; np=reject; rua=mailto:dmarc@example-school.org.uk"

Plan around the academic calendar. School holidays are good windows for policy changes; the first week of term, results days and admissions deadlines are not. If the SPF record grows too large, read SPF too many DNS lookups. For the policy meanings, see p=none, p=quarantine and p=reject explained.

10

What should MSPs serving schools and trusts check?

MSPs serving schools and trusts should check domain ownership, DNS access, every sending platform and the calendar before any policy change. The work repeats across many similar clients, so a standard checklist and central reporting pay off.

  • [ ] List every domain per school and per trust, including legacy, parked and tenant domains.
  • [ ] Confirm who controls DNS for each domain (the school, the trust, a local authority, a former supplier or a web agency).
  • [ ] Publish p=none with an rua address on every domain, and remove duplicate DMARC or SPF records.
  • [ ] Enable DKIM on Google Workspace for Education or Microsoft 365 for every custom domain.
  • [ ] Map every source in aggregate reports to a platform and a named school contact.
  • [ ] Ask each third-party platform for custom DKIM, or move it to a subdomain.
  • [ ] Find scanners, printers and on-premises systems that relay mail directly.
  • [ ] Check SPF stays under the 10 lookup limit after all changes.
  • [ ] Agree change windows that avoid term starts, results days and admissions deadlines.
  • [ ] Lock down non-sending domains with p=reject and v=spf1 -all.
  • [ ] Record each policy change with a rollback to p=none, and report progress to the trust or bursar.
  • [ ] Map the work to the DfE standard's anti-spoofing expectation for governors and auditors.

dmarc.ai processes DMARC aggregate (RUA) reports for every domain in one multi-tenant view and uses AI to classify sending sources, which helps when a trust has dozens of school domains with different platforms. Failure (RUF) reports are never used for AI. See DMARC for MSPs and, for UK schools and academy trusts, education DMARC in the UK. The onboarding checklist covers generic steps.

11

FAQ

Are UK schools required to deploy DMARC?

Not by name. The DfE cyber security standard asks schools and colleges to reduce the risk of third parties sending imitation emails and links to NCSC guidance, which recommends DMARC moving towards rejecting spoofed mail. DMARC at p=reject is the most direct way to show you meet that expectation, so many trusts treat it as required in practice.

Will DMARC break our parent communication or payment emails?

Only if you enforce before those platforms are aligned. At p=none nothing is blocked, and aggregate reports show whether each platform passes SPF or DKIM for your domain. Ask each vendor to sign with your domain using custom DKIM, or move it to a subdomain, before moving to p=quarantine or p=reject.

Should a multi-academy trust use one DMARC record for all schools?

No. Each school domain needs its own DMARC record, because DMARC applies per organizational domain and each school usually has different senders. A trust should centralize reporting and change control, then stage each domain separately. Subdomains under one trust domain can inherit a parent policy, but separate school domains cannot.

How long does a DMARC rollout take for a university?

It depends on the number of domains, departments and third-party senders, not on a fixed schedule. A single school with a simple estate can move quickly. A university with many departments, research systems and alumni platforms usually works domain by domain and subdomain by subdomain, often over several terms, with the parent domain last.

What happened to NCSC Mail Check for schools?

The NCSC retired Mail Check and Web Check on 31 March 2026. Schools, colleges and universities that relied on it for DMARC aggregate reporting need another way to receive and read those reports. Keep the DMARC records in place, point the rua address at a new report processor, and continue monitoring before changing policies.

Related articles

Related tools

Ready to Implement?

Get authenticated mail moving in minutes: start free, book a guided demo, or talk to the team about your stack.