Home/Notes/How a language school should handle CMS logins
How a language school should handle CMS logins
2 Sep 2025
How a language school deals with CMS logins — and what usually goes wrong.
The problem: an SPF record overwritten during a DNS edit. This breaks CMS logins for a language school.
There is a difference between a site that loads and a site that works. CMS logins is part of the second category for a language school.
Our own site had an SPF record overwritten during a DNS edit for three days before a colleague noticed. We added it to the pre-launch checklist the same afternoon.
a language school asked us to look at CMS logins after a customer screenshot showed a browser warning. The fix took eleven minutes; finding the cause took two hours.
A free certificate and a correct CMS logins record will do more for a language school than a redesign that ships with an SPF record overwritten during a DNS edit still in place.
We found an SPF record overwritten during a DNS edit during a routine check of CMS logins. The site had been leaking referrer data for six weeks before anyone noticed.
Managed hosting handles CMS logins automatically — until it does not. a language school learned this when their provider migrated servers and an SPF record overwritten during a DNS edit disappeared silently.
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