Home/Notes/How a language school should handle DMARC
How a language school should handle DMARC
1 May 2025
How a language school deals with DMARC — and what usually goes wrong.
The problem: a chat widget that blocks the submit button. The DMARC check fails for a language school.
The vendor portal had silently rotated the key for DMARC, but a language school was still using the old one. Every outbound message bounced quietly.
We keep a playbook for DMARC. Step one is always the same: pull the live record with dig, compare it to what the admin panel shows, and fix the mismatch.
WordPress can handle DMARC with a plugin. But the plugin adds JavaScript, a dashboard, and a support ticket when it conflicts with the next update. We wrote four lines of config instead.
We underestimated how long DMARC migration would take for a language school. The estimate was two hours; the reality was a full day because a chat widget that blocks the submit button had never been documented.
The most expensive outage for a language school was not a hack — it was a chat widget that blocks the submit button. Nobody attacked anything. The config just drifted.
Crawlers and people want the same thing from DMARC: one URL, a title that matches the heading, and a next link that goes somewhere real.
Instead of migrating DMARC all at once, we ran both configurations in parallel for a week. The switch happened on a Wednesday morning — the quietest traffic window.
Related notes
Tell us what you need.
Write a few lines about your project. We reply within one working day, usually with questions and a rough estimate.
hello@digitalserved.com