Use this domain registrar security checklist to review two-factor authentication, recovery options, transfer locks, user permissions, API credentials, payment settings, DNS access, and account activity before a small mistake becomes a domain outage or unauthorized transfer.
Overview
A domain registrar account is more than a place to buy a domain name. It may control registration details, renewal settings, nameservers, DNS records, transfer permissions, billing information, and access for everyone who works on the website. If an attacker gains control of the account, the consequences can include a changed website, interrupted email, redirected traffic, or an attempted transfer to another registrar.
The best domain registrar for your business is therefore not defined only by introductory pricing or a convenient domain name search. Account security controls, recovery procedures, user management, notifications, and support processes should be part of a domain registrar comparison. Features and terminology vary by provider and domain extension, so use this guide as an audit framework rather than assuming every registrar offers the same controls.
Review the checklist at least quarterly for important domains. Also use it after a team member leaves, before a major renewal, when ownership changes, after a suspected phishing attempt, or whenever you move domains between providers. Keep a written record of who has access, what each person can change, and how the account can be recovered if the primary administrator is unavailable.
What to track
1. Account login and multi-factor authentication
Start with the registrar account itself. Confirm that every person with direct access uses a unique password that is not reused on the website, hosting account, email, or payment services. Where available, enable multi-factor authentication (MFA) for all administrators. An authenticator app or security key may provide a stronger account-protection option than relying on a password alone, but the appropriate method depends on what the registrar supports.
Record which authentication methods are enabled and where backup codes are stored. Do not leave recovery codes in a shared chat or an unprotected document. If a business uses a password manager, store them in a restricted vault with a documented emergency-access process. Check whether the registrar sends login, password-change, MFA-change, or new-device alerts, and make sure those notifications reach an actively monitored address.
2. Recovery contacts and ownership details
Review the account email address, registrant contact information, administrative contact details, and recovery phone number where applicable. They should belong to the business or domain owner, not to a former employee, temporary contractor, or personal inbox that nobody else can access.
Separate recovery responsibility from day-to-day website work when practical. The person who edits DNS does not necessarily need to be the person who can recover the registrar account. Keep an offline record of the legal owner, account identifier, recovery contacts, and the process for changing them. Avoid making changes in a hurry during an incident without documenting what was changed and why.
3. Domain transfer locks
Check the transfer status for each important domain. A registrar-level transfer lock is intended to help prevent an unauthorized transfer, but it is not a substitute for account security. Confirm whether the lock is enabled and learn how the registrar displays it in the dashboard. Some extensions or situations may use different rules, and a transfer may require additional confirmation.
Before an intentional transfer, verify the domain name, destination registrar, authorization requirements, and expected timing. Do not unlock a domain because of an unsolicited email or message. Open the registrar dashboard directly rather than following a link in a request. For high-value or business-critical domains, ask whether an additional registry-lock service is available and what identity checks, fees, approval steps, or operational delays it involves. Availability and requirements can vary, so confirm them with the registrar and the relevant registry.
4. Delegated users and permissions
List every user, delegated account, support contact, and shared login with access to the registrar. Remove accounts that are no longer needed. Assign the narrowest practical permission level: someone who only needs to view renewal dates or update DNS should not automatically receive ownership, billing, transfer, or account-recovery authority.
Shared credentials make it difficult to identify who made a change and create problems when someone leaves. Prefer individual user accounts with an activity history. If the registrar does not offer granular roles, document the limitation and reduce access by using a controlled administrator process. Review access after staffing changes, ownership transfers, agency or developer handoffs, and the completion of a website launch.
5. API keys and automated access
Developers and infrastructure tools may use API credentials to manage DNS or domain settings. Treat each key like a password. Name keys by purpose, limit their permissions where the provider allows it, and avoid placing them in public repositories, browser code, screenshots, or shared documents.
Track who created each credential, which system uses it, when it was last reviewed, and when it should be rotated. Revoke unused keys immediately. If a key may have been exposed, rotate or disable it first and then inspect recent account and DNS activity. Do not assume that deleting a local configuration removes access from the registrar.
6. Payment and renewal protection
Security also includes preventing an accidental expiration. Confirm that auto-renewal settings match the business decision for each domain and that the payment method will remain valid through the renewal period. Keep billing contacts current, but do not give every website administrator access to payment details.
For a portfolio, maintain a separate inventory showing the domain, owner, renewal date, auto-renewal status, registrar, renewal contact, and business purpose. This complements a registrar dashboard and makes it easier to identify unexpected changes. For additional planning, see how to compare domain renewal pricing and the calendar for domain expiration and redemption periods.
7. DNS access and change monitoring
Determine who can change nameservers and DNS records. Nameserver changes can redirect an entire domain, while individual records can affect a website, email, verification service, or security control. Separate DNS editing from transfer and billing permissions when possible.
Keep a basic record of important records and their purpose. This should include website records, mail records, verification records, and any deliberate security records. The DNS records cheat sheet can help distinguish common A, AAAA, CNAME, MX, TXT, and NS records. Turn on change notifications if offered, and investigate an unexpected nameserver or DNS change promptly.
8. Account activity and notifications
Review login history, password changes, MFA changes, user invitations, domain unlocks, transfer requests, nameserver edits, DNS changes, and billing updates. The exact activity categories depend on the registrar, so record the events that matter in your environment.
When an alert appears, do not judge it only by whether the change looks familiar. Confirm who made it, why it was needed, which domain was affected, and whether the change was completed through the expected workflow. If something is unexplained, preserve the notification and account details before reversing settings. Contact the registrar through its official support channel if you suspect unauthorized access.
Cadence and checkpoints
A practical review does not need to be complicated. Use these checkpoints:
- Monthly: Review alerts, recent logins, pending transfers, domain unlock status, and unusual DNS or nameserver changes for critical domains.
- Quarterly: Audit users, delegated access, API keys, recovery contacts, MFA coverage, auto-renewal, and payment details. Confirm that the domain inventory matches the registrar account.
- Before a renewal: Verify the registrant, renewal term, payment method, auto-renewal decision, and the person responsible for resolving a failed payment.
- Before a transfer: Confirm ownership details, transfer lock status, authorization requirements, destination registrar, DNS continuity plan, and the person approving the move. The domain transfer checklist covers common preparation steps.
- After personnel changes: Remove departing users, rotate shared or exposed credentials, update recovery contacts, and check recent activity.
- After an incident: Change passwords, revoke sessions or API keys where possible, restore correct MFA and locks, inspect DNS and nameservers, and document the timeline.
For a larger portfolio, apply the same schedule by risk. A parked defensive domain may need a lighter operational review than a domain supporting a company website and email, but ownership, recovery, and renewal information should remain current for both.
How to interpret changes
Not every dashboard change indicates an attack. A planned website migration can create legitimate DNS activity, and a registrar may redesign its security settings or rename a transfer control. The useful question is whether the change is authorized, explainable, and recorded.
Classify findings into three groups:
- Expected: The change has a named owner, a business reason, and a matching ticket, launch plan, or transfer record.
- Needs attention: The setting is outdated or unclear, such as an inactive recovery email, an unused user, an unreviewed API key, or an unknown auto-renewal choice.
- Urgent: There is an unexplained login, account-email change, disabled MFA, unlocked domain, unauthorized nameserver change, or transfer request.
Prioritize controls by consequence. Protect the account that controls the most important domain first, then the DNS and recovery paths connected to it. Do not make broad changes such as switching nameservers during an investigation unless you understand the effect on the website, email, certificates, and verification records. If you need to connect a domain to hosting, use the relevant DNS and hosting troubleshooting guide and record each deliberate change.
When to revisit
Use this article as a recurring audit rather than a one-time setup task. A quarterly review is a sensible baseline for valuable domains, with a shorter interval for accounts that have frequent staff, developer, or infrastructure changes. Revisit the checklist immediately when the registrar changes its dashboard, authentication methods, transfer terminology, registry-lock process, user roles, API controls, or notification settings.
Also review it when buying a domain, moving to a new registrar, adding a new developer or marketing teammate, consolidating a portfolio, changing hosting, or preparing for a major campaign. A registrar comparison should include the security controls available at the time of purchase, not just the first-year registration offer. If you are evaluating providers, compare privacy options, renewal handling, support access, delegation, transfer protection, and DNS management alongside price.
To finish an audit, export or write down the current state of each important domain, assign an owner to every open issue, and set the next review date. Then verify the highest-impact controls: MFA works, recovery contacts are controlled, unnecessary users and API keys are removed, transfer locks are understood, auto-renewal matches your plan, and DNS access is limited. Repeat the process after any material account or ownership change so that your domain security remains an active part of domain management.