A secure domain starts with more than a strong password. This checklist shows how to review registrar two-factor authentication, passkeys, recovery controls, transfer locks, registry locks, user permissions, alerts, and support procedures so you can reduce the risk of unauthorized domain changes and repeat the review on a sensible schedule.
Overview
Your registrar account controls critical infrastructure: domain ownership records, nameservers, DNS records, renewal settings, transfer permissions, and sometimes email or hosting connections. If an attacker gains access, the damage may include website downtime, intercepted email, phishing pages, or an unauthorized domain transfer. A domain security review should therefore cover both account access and the controls that protect individual domains.
Security features vary by registrar, domain extension, account type, and sometimes the value or risk profile of the domain. Treat the checklist below as a framework for comparison rather than a claim that every provider supports every control. Before relying on a feature, confirm its current availability, setup requirements, recovery process, and any fees or waiting periods.
This approach is useful when you buy a domain name, move a domain to a new provider, add a team member, prepare for a transfer, or conduct a quarterly security audit.
What to track
Registrar security comparison checklist
Record the answers in a shared but access-controlled inventory. Compare the practical protection offered, not just the number of settings listed in a dashboard.
| Control | What to check | Why it matters |
|---|---|---|
| Two-factor authentication | Whether the registrar supports an authenticator app, hardware security key, text message, or more than one method | Creates a second barrier after a password is exposed. Prefer methods that do not depend solely on a phone number when stronger options are available. |
| Passkeys | Whether passkeys are supported, how they can be added or removed, and whether a backup sign-in method is required | Can reduce dependence on passwords and resist some forms of credential phishing. Review the devices and accounts that can use the passkey. |
| Recovery controls | Recovery email, backup codes, trusted devices, identity checks, and the process for replacing a lost authenticator | Recovery is part of security. An outdated email address or unprotected backup code can undermine otherwise strong authentication. |
| Transfer lock | Whether the domain is locked against an outbound transfer and where the lock status is displayed | Helps prevent an unauthorized transfer. Check the lock before and after legitimate transfer work. |
| Registry lock | Whether an additional registry-level control is available, what verification it requires, and which changes it covers | May add a stronger approval step for high-value or business-critical domains. Availability and operating procedures vary. |
| Delegated user access | Whether separate users, roles, permissions, and activity records are available instead of shared credentials | Limits access by responsibility and makes it easier to remove a former administrator without changing everyone’s login. |
| Login and change alerts | Notifications for sign-ins, password changes, DNS edits, nameserver changes, contact updates, and transfer actions | Shortens the time between an unauthorized action and detection. Send alerts to an account monitored by more than one responsible person where appropriate. |
| Support verification | How support verifies ownership before discussing or changing a domain, and which contact details are accepted | Prevents attackers from using social engineering or publicly available information to influence account changes. |
| Account recovery procedure | Expected evidence, escalation path, business-hours limitations, and the steps to regain access if administrators are unavailable | A documented recovery path reduces panic and discourages unsafe workarounds during an incident. |
Protect the domain after protecting the login
Account security and domain security are related but not identical. Confirm that the registrant and administrative contact information is current, renewal notices reach the right people, and auto-renewal settings match the owner’s plan. Review nameservers and important DNS records, especially A, CNAME, MX, and TXT records. Unrecognized changes should be investigated rather than overwritten immediately, because they may indicate a broader account compromise.
Keep a record of the intended DNS configuration and the date it was last approved. The guide to DNS records and nameserver setup can help separate ordinary DNS maintenance from a suspicious change. For a larger portfolio, use the domain portfolio security audit template as an inventory model.
Cadence and checkpoints
A recurring schedule works best when each review has a defined purpose. Put the following checkpoints on a calendar, and adjust them to the importance of the domain and the number of people who can administer it.
- Monthly: Review login, DNS, nameserver, contact, and transfer alerts. Investigate anything that cannot be matched to an approved task.
- Quarterly: Confirm that two-factor authentication or passkeys remain enabled, recovery details work, transfer locks are active where intended, and delegated users still need their current permissions.
- Every six months: Recheck the registrar’s supported authentication methods, recovery rules, support-verification requirements, and registry-lock process. These features and procedures can change.
- Before a transfer: Verify the account owner, domain lock status, contact information, authorization requirements, DNS continuity plan, and the destination account’s security settings. Use this domain transfer guide to plan the operational steps.
- After staff or ownership changes: Remove former users, rotate shared recovery information, review API keys or integrations, and confirm that the new responsible owner can complete recovery without relying on a departed person.
- After a security event: Preserve relevant alerts and timestamps, secure the email accounts connected to the registrar, change credentials from a trusted device, review DNS and transfer settings, and contact the registrar through its documented channel.
Annual access-review template
Copy this short record into your security or domain-management system:
- Review date and reviewer: Record who performed the review and when.
- Domains covered: List each domain, extension, registrar, account owner, and business purpose.
- Authentication: Record the enabled method, recovery email, backup-code status, passkey devices, and last verification date.
- Permissions: List each user, role, last access review, and reason access remains necessary.
- Domain controls: Record transfer-lock status, registry-lock status if applicable, renewal setting, nameservers, and the date DNS was last approved.
- Alerts: Confirm recipients for login, DNS, contact, renewal, and transfer notifications.
- Recovery: Record where the recovery procedure is stored and who can execute it.
- Actions: Assign an owner and due date for every gap; do not mark the review complete until exceptions are documented.
How to interpret changes
Not every change is an incident. A new login may correspond to a planned device replacement, and a DNS edit may be part of a website launch. The important question is whether the change has an identifiable owner, a matching ticket or approval, and a result that agrees with the intended configuration.
Prioritize changes that affect control of the domain rather than only its content. Examples include an unexpected password or recovery-email change, disabled two-factor authentication, altered nameservers, a removed transfer lock, a new administrator, a changed registrant contact, or an unexplained transfer request. Treat multiple related changes as one possible event instead of reviewing each alert in isolation.
Also distinguish between a security control and a recovery dependency. A registrar may offer strong authentication, but if the only administrator uses an inaccessible mailbox, the organization can still lose practical control. Use separate, well-protected recovery paths where the provider allows them, and document who is authorized to approve high-impact changes.
When comparing registrars, include the full operating model: authentication choices, permission granularity, alert quality, support verification, recovery clarity, DNS controls, renewal management, and transfer procedures. A low introductory price does not compensate for controls that do not fit the domain’s risk. For broader registrar comparisons, review guidance on registrar features for developers and teams and total domain ownership costs.
When to revisit
Revisit this checklist at least quarterly for access and alerts, and refresh the feature comparison every six months. Return sooner when a registrar changes its dashboard or authentication options, a registry changes transfer or lock procedures, a critical domain is acquired, ownership changes, a new administrator is added, a domain is prepared for transfer, or a suspicious notification appears.
Make the next review practical: choose one registrar account, export or record its current users and domains, verify the strongest available sign-in method, test recovery without weakening security, confirm transfer and registry controls, and compare DNS against the approved record. Close or assign each gap before moving to the next account. That small, repeatable process is more reliable than waiting for a major renewal, transfer, or security incident to expose an outdated setting.