Protecting a domain at the registrar: the site can be turned off without touching the code

A domain is a separate key to the company. It may sit in a registrar account on the director's mail or on the mail of the studio that registered the name in the launch year. The password is old. Nobody waits for the registrar's invoices. One day the NS records change, the site opens as someone else's, mail stops arriving. The file backup is intact and useless while the name does not point at you.

The minimum worth turning on

• The registrar account in the company's name, not a former contractor's. The recovery mail is yours too.
• A second factor and a transfer lock. A DNS change should not go through "in one click from someone else's laptop".
• A payment term longer than accounting's memory. Expiry sometimes turns the name off with no attack at all.
• A short list of who may change DNS. Not the whole contractor chat.

If the name is already being moved, the clock is in seconds: the registrar, a lock if it is still available, and in parallel an understanding of whether the mail used to recover the account was taken too. Advice from search often arrives late exactly here.

Lexora checks the domain owner and recovery in a site audit. This is not a separate "domain service" and not a promise to take someone else's name through court. If a change already happened, we bring in incident response. Monitoring helps because it notices when the page became someone else's, but it does not replace a lock at the registrar. The basic audit is free for new clients.