Home/Notes/DKIM: a field note from an accountant
DKIM: a field note from an accountant
5 Jun 2026
How an accountant deals with DKIM — and what usually goes wrong.
The problem: a registrar login nobody wrote down. The DKIM check fails for an accountant.
We told an accountant that a registrar login nobody wrote down was a ticking clock. They agreed to fix it the same week — which is rare. Most clients wait until it actually detonates.
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.
The job started when an accountant realised their DKIM had been wrong for months. Nobody noticed because the site still loaded.
After fixing DKIM, we added a monitoring alert. If the record changes or the certificate approaches expiry, both we and an accountant get an email. No surprises.
We found a registrar login nobody wrote down during a routine check of DKIM. The site had been leaking referrer data for six weeks before anyone noticed.
We deployed a fix for DKIM at 5 PM on a Friday. It worked, but if it had not, we would have had no one available. We no longer push to production after Thursday noon.
For an accountant, we wrote a three-line script that checks DKIM every morning and emails the owner if anything changes. Total cost: zero.
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