A domain can remain registered and still be at risk if the controlling account, DNS settings, renewal process, or recovery details are poorly protected. This domain security checklist gives you a repeatable way to audit registrar access, transfer controls, DNS changes, renewal safeguards, and recovery readiness each quarter or after a major ownership or infrastructure change.
Overview
Protecting a domain from hijacking or accidental loss requires more than enabling a single setting. A practical review should cover four connected layers:
- Account security: Who can sign in to the registrar, and how is identity verified?
- Registration controls: Can the domain be transferred, deleted, or modified without an approved process?
- DNS control: Who can change nameservers and records that direct website and email traffic?
- Recovery and continuity: Can an authorized person regain access if an administrator leaves, loses a device, or becomes unavailable?
These controls should be documented separately from website hosting credentials. A hosting provider may serve the website, while the registrar controls the domain registration and the DNS provider controls some or all of its records. Mapping those responsibilities prevents a common failure: assuming that one login protects the entire web presence.
Begin with an inventory containing the domain name, registrar, renewal date, registered owner or business entity, DNS provider, nameservers, hosting provider, email provider, and named account administrators. Store the inventory in an access-controlled location, not in a public project document or a shared email thread.
What to track
1. Registrar account access
Review every person, team, and integration with access to the registrar account. Remove former employees, unused users, duplicate accounts, and credentials that were created for a temporary task. Where the registrar supports roles or delegated permissions, give each user the smallest level of access needed. Registration ownership, billing, DNS administration, and support access do not always need to belong to the same person.
Check that the primary email address is monitored and belongs to the business rather than to one individual. Confirm that the recovery email and telephone details are current, but do not treat them as substitutes for a documented recovery process.
2. Authentication and recovery
Use multi-factor authentication when it is available, preferably with an authenticator application or hardware security key rather than relying on a single password. Review enrolled devices and recovery methods after staff changes. Store backup codes according to your organization’s secure credential procedures, and test that an authorized backup administrator can follow the recovery path without weakening account security.
Keep a short recovery worksheet with these fields:
- Registrar and account identifier
- Primary and backup account administrators
- Recovery email and phone ownership
- Authentication methods and backup-code location
- Billing contact and approved payment owner
- Escalation path for registrar support
- Date the recovery details were last verified
3. Domain transfer and registrar locks
Check whether the domain has a registrar-level transfer lock or equivalent transfer protection enabled. Learn how your registrar describes the control, which account roles can change it, and what approval is required before a transfer can proceed. Do not assume that a lock prevents every type of account compromise; it is one layer in a broader access-control plan.
Record the intended transfer process in advance. A useful rule is that no one person should be able to request, approve, and validate a high-impact domain transfer without independent review. For a planned move, confirm the domain’s administrative contact, authorization requirements, transfer timing, DNS provider, and rollback plan. The Domain Transfer Playbook provides a separate workflow for moving a domain without avoidable downtime.
4. DNS and nameserver changes
List the authoritative nameservers and identify who can change them. Then document important records, including website address records, mail exchange records, SPF, DKIM, DMARC, verification records, and redirects where applicable. A nameserver change can affect every record at once, so it deserves a higher approval threshold than a routine record edit.
Use a DNS-change approval note with the following fields:
- Requester and date
- Domain and exact record or nameserver change
- Business or technical reason
- Expected effect on website, email, certificates, and verification services
- Planned start time and propagation-check plan
- Reviewer and approval
- Rollback value and person responsible for reversal
Limit editing access to the DNS platform, enable its available audit logging, and retain a known-good record inventory. For record-level troubleshooting, use the DNS Troubleshooting Guide. For a new connection between a registrar and host, see How to Connect a Domain to Web Hosting.
5. Renewal and ownership safeguards
Confirm that automatic renewal is configured only if the payment method and billing notifications are actively monitored. Automatic renewal is not a complete safeguard if a card expires, an invoice goes to an unmonitored inbox, or the account cannot be accessed. Record the renewal date, expected renewal owner, and at least two reminder checkpoints before expiration.
Review the registration contact and legal owner after acquisitions, reorganizations, or changes to the business name. Keep renewal planning separate from website hosting planning: a hosting migration does not necessarily renew or extend a domain registration. See Domain Expiration and Renewal Guide and Domain Renewal Costs Explained when reviewing expiration risk and budgeting.
Cadence and checkpoints
A quarterly audit is a practical default for an active business domain. Increase the frequency for domains used by financial, customer-support, authentication, or high-volume email systems. Use the following schedule as a working baseline:
| Timing | Review | Evidence to retain |
|---|---|---|
| Monthly | Unexpected login notices, DNS alerts, renewal messages, and support emails | Alert review and open incidents |
| Quarterly | Users, roles, MFA devices, recovery contacts, transfer lock, nameservers, and DNS inventory | Completed checklist and administrator sign-off |
| Before renewal | Payment method, billing contact, renewal term, ownership details, and backup administrator | Renewal confirmation and updated inventory |
| Before a DNS change | Requested values, impact, approval, monitoring, and rollback | Change record and post-change verification |
| After staff or vendor changes | Access removal, credential rotation, delegated permissions, and recovery ownership | Access review and handoff record |
Run an additional review after a suspected phishing attempt, unexpected DNS change, lost authentication device, registrar migration, business acquisition, website migration, or email-provider change. A website move may require a broader continuity review; the Website Migration Checklist can help connect domain controls with hosting and SEO checks.
How to interpret changes
Not every change is an incident, but every unexplained change deserves verification. A new administrator may be legitimate if it matches an approved staff or ownership change. A new nameserver, unfamiliar MFA device, altered recovery email, or unexpected transfer-related notification should be treated as high priority until confirmed through a trusted channel.
Compare the current state with the last approved inventory rather than relying on memory. Ask four questions:
- What changed, and when?
- Who requested and approved it?
- What systems could be affected, including email and certificate validation?
- Can the change be reversed using a documented value or backup?
If you suspect unauthorized access, preserve notifications and audit records, prevent further changes where possible, secure the registrar and DNS accounts from a trusted device, review all users and recovery methods, and contact the registrar through its official support channel. Verify website, email, and DNS records after containment. Do not make broad corrective changes without recording the original state; rushed edits can make recovery harder.
For continuity, maintain backups of website data and configuration separately from domain credentials. A domain recovery plan cannot restore a deleted website, and a hosting backup cannot by itself recover a lost registration. Use the Website Backup and Restore Testing Guide to test the hosting side of that plan.
When to revisit
Schedule the next domain security review now, then repeat it at least quarterly. Revisit the checklist immediately when a domain changes registrar, DNS provider, host, email provider, owner, or administrator. Also review it before a major launch, acquisition, rebrand, domain transfer, or change to the organization’s authentication system.
At each review, mark every item as verified, needs action, or not applicable. Assign an owner and due date to every open item. Finish by checking the public website and domain email from outside the administrative network, confirming that DNS records resolve as expected, and documenting who performed the verification.
Keep this article and your internal worksheet together as a recurring audit resource. Security settings, registrar interfaces, authentication options, transfer procedures, and registry requirements can change, so refresh the checklist when your providers publish material changes or when your organization’s ownership and access model changes.