Home/Notes/Setting up DKIM for a language school
Setting up DKIM for a language school
10 Mar 2025
How a language school deals with DKIM — and what usually goes wrong.
The problem: a registrar login nobody wrote down. The DKIM check fails for a language school.
We write notes like this one because the same problems come back. If someone at a language school reads it and avoids a registrar login nobody wrote down, the note paid for itself.
After the move, a registrar login nobody wrote down broke search indexing for a language school. Google kept serving the old pages for another nineteen days.
The worst DKIM failure we have seen at a language school was invisible for eight months. The backup existed but had never been tested, and the data inside was three migrations old.
The fix was to delete the old entry, wait for TTL to expire, and re-add DKIM with the correct value. We scheduled it for 3 AM so nobody lost traffic.
We run a monthly diff on DNS for a language school. If a record changes and nobody in the team made the change, we get an alert. a registrar login nobody wrote down was caught this way last quarter.
For a language school, we wrote a three-line script that checks DKIM every morning and emails the owner if anything changes. Total cost: zero.
A form that collects data for a language school should say where the message goes. Nine fields and a captcha on a quiet Tuesday will cost you the person who actually wanted to pay.
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