Home/Notes/A practical look at registrar locks for an accountant
A practical look at registrar locks for an accountant
2 Sep 2026
How an accountant deals with registrar locks — and what usually goes wrong.
The problem: a calendar they already pay for. This is where registrar locks breaks for an accountant.
We found a calendar they already pay for during a routine check of registrar locks. The site had been leaking referrer data for six weeks before anyone noticed.
We solved registrar locks for an accountant by moving it behind a reverse proxy. The old configuration stayed live as a fallback for forty-eight hours, then we pulled it.
We moved registrar locks for an accountant to a provider that supports DNSSEC. It added five minutes to the migration and closed a class of attacks they did not even know about.
We rotate API keys for registrar locks annually. an accountant did not see the point until we showed them the access log: the old key had been used from an IP in a country nobody on their team has visited.
We run a monthly diff on DNS for an accountant. If a record changes and nobody in the team made the change, we get an alert. a calendar they already pay for was caught this way last quarter.
The vendor portal had silently rotated the key for registrar locks, but an accountant was still using the old one. Every outbound message bounced quietly.
We write notes like this one because the same problems come back. If someone at an accountant reads it and avoids a calendar they already pay for, the note paid for itself.
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