Home/Notes/Setting up registrar locks for a hardware store
Setting up registrar locks for a hardware store
24 Apr 2025
How a hardware store deals with registrar locks — and what usually goes wrong.
The problem: a 404 that still returns 200. This is where registrar locks breaks for a hardware store.
We run a monthly diff on DNS for a hardware store. If a record changes and nobody in the team made the change, we get an alert. a 404 that still returns 200 was caught this way last quarter.
The chain of trust for registrar locks starts at the registrar. If the registrar account uses an email nobody reads, every downstream fix is temporary.
We write notes like this one because the same problems come back. If someone at a hardware store reads it and avoids a 404 that still returns 200, the note paid for itself.
Nobody at a hardware store could remember who had configured registrar locks. The credentials were in a text file inside a folder called OLD STUFF on a shared drive.
Big agencies solve registrar locks with a team. We solve it with a checklist and a dig command. The result is the same; the invoice is shorter.
The fix was to delete the old entry, wait for TTL to expire, and re-add registrar locks with the correct value. We scheduled it for 3 AM so nobody lost traffic.
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