01

Treat domains as production assets

A domain can direct web, email, authentication and remote access. Record registrars, DNS providers, authoritative name servers, renewal dates, account owners and the services each domain supports. Include defensive and parked domains because forgotten registrations may still be abused for impersonation.

Use organisation-controlled accounts with strong authentication and restricted administration. Avoid tying critical ownership to one employee or supplier mailbox. Enable registrar locks and change protections appropriate to the provider, and document how urgent recovery works if the primary administrator is unavailable.

02

Control and observe changes

Limit who can change nameservers, mail routes and security records. Require review for high-impact changes and preserve an independent record of expected configuration. Infrastructure as code can improve review, but its repository and deployment credentials become part of the trust boundary.

Monitor DNS records, registrar events, certificate transparency and unexpected mail-authentication changes. Alerts need an owner who understands planned change. Baseline common records so responders can distinguish authorised migration from redirection or persistence.

03

Prepare for compromise and expiry

Create a playbook for compromised registrar credentials, altered nameservers, unauthorised certificates and accidental expiry. Maintain verified provider contacts outside the affected domain and know which evidence the provider will require before restoring control.

After recovery, rotate credentials, review delegated access, examine historical changes and validate dependent services. Test renewal and recovery procedures periodically. Domain security is not complete when automatic renewal is enabled; payment failure, ownership confusion and compromised identity can still interrupt service.

Practical checklist

What to do next.

  • ✓Inventory domains, registrars, DNS providers and owners.
  • ✓Protect administration with strong authentication.
  • ✓Restrict and review high-impact record changes.
  • ✓Monitor DNS, registrar and certificate events.
  • ✓Maintain out-of-band recovery contacts.
  • ✓Test renewal and compromise recovery.

Use guidance responsibly

Technology, provider behaviour and legal requirements change. Validate implementation details against current official documentation, test changes safely and obtain qualified legal advice where required.