A domain name audit is a once-a-year check that every domain your business depends on is owned by the business, renews on time, is locked against theft, and points where it should. Work through ten areas for each domain: inventory, ownership, contact details, registrar account access, expiry and auto-renew, locks and security, nameservers and DNS, email records, SSL certificates and website status, and finally purpose and cost. Fix anything that is wrong, write down what you found, and set reminders for next year.
Most small businesses never do this until something breaks. The checklist below takes an afternoon for a handful of domains, and it catches the problems that cause outages: expired cards, auto-renew switched off, a former employee as the registrant, or a contact email nobody reads.
Before you start: gather your list
You cannot audit domains you do not know about. Start with a full inventory: log into every registrar account, export the domain list, and add anything you find in email receipts, card statements or your hosting control panel. Our guide on how to find all the domains you own walks through each source.
Put the results in one table with a row per domain. The columns you need are the same items as the checklist below, so you can tick them off as you go.
The domain audit checklist
| Area | What to check | Good result |
|---|---|---|
| Ownership | Registrant name and organization at the registrar | The business, not an individual or a former supplier |
| Contacts | Registrant, admin and account email addresses | A role address you control, on a different domain if possible |
| Account access | Who can log into the registrar account | At least two current people, with two-factor authentication on |
| Expiry | Expiry date from RDAP or WHOIS | More than 90 days away, or a renewal planned |
| Auto-renew | Auto-renew setting per domain, and the payment method | On, with a card that will not expire before the renewal |
| Lock | Domain status codes | clientTransferProhibited present |
| Nameservers | Nameservers listed in the registry record | The DNS provider you expect, and nothing unfamiliar |
| DNS records | A, AAAA, CNAME, MX and TXT records | Each record has a known purpose; nothing stale |
| Email security | SPF, DKIM and DMARC records | Present and matching the services that send your mail |
| SSL | Certificate expiry and the names it covers | Valid, auto-renewing, covering www and the bare domain |
| Purpose and cost | What the domain is for and what it costs to renew | A clear reason to keep it |
1. Ownership and contact details
The registrant is the legal holder of the domain. If a web designer registered your main domain under their own name or in their own account, you do not fully control it, and getting it back later can be slow. Fix this first.
- Log into the registrar and open the domain's contact or registrant details.
- Check the registrant name and organization show your business.
- Replace any personal or ex-employee email with a role address such as
domains@orit@. - If the domain sits in someone else's account, ask for an account-to-account move (sometimes called a push) at the same registrar, or a transfer to your own registrar account.
Changing the registrant name or organization can trigger a 60-day transfer lock at many registrars. That is normal, and only matters if you plan to move registrars soon.
Use a contact email that does not depend on the domain itself. If the domain expires, email at that domain stops too, and the renewal warnings vanish with it.
2. Registrar account security
Most domain hijacks start with a compromised registrar login. For each account:
- Turn on two-factor authentication, preferably an authenticator app rather than SMS.
- Remove users who have left the business or no longer need access.
- Make sure at least two people in the business can log in, so a holiday or departure does not lock you out.
- Store the login in a password manager the business controls.
3. Expiry, auto-renew and payment
Look up each domain with RDAP or WHOIS and note the expiry date. Then check, in the registrar account, that auto-renew is on for that specific domain and that the payment card is valid past the renewal date. Account-level auto-renew settings do not always apply to domains added later by transfer. Our article on what to do when auto-renew fails lists the usual causes.
For your main business domain, consider renewing for several years. It costs the same per year and removes a single point of failure.
4. Locks and status codes
Every domain you are not actively transferring should show clientTransferProhibited. Watch for statuses that need action, such as clientHold or serverHold, which stop the domain resolving, or redemptionPeriod, which means it has already expired. See how to lock a domain name for the steps and when a registry lock is worth paying for.
5. Nameservers and DNS records
Confirm the nameservers match the DNS provider you actually use. Then review the zone itself:
- A and AAAA records: do they point to your current host? Old records for a retired server are an invitation for subdomain takeover.
- CNAME records: any that point to a service you no longer use should be deleted.
- MX records: do they match your current email provider?
- TXT records: remove verification records for tools you have cancelled, and make sure there is only one SPF record.
Save a copy of every record as part of the audit. If something changes unexpectedly later, you will know what it used to be.
6. Email authentication
Check that SPF lists every service that sends mail as your domain, that DKIM is set up with your email provider, and that a DMARC record exists. Even a monitoring policy (p=none) with a reporting address is better than nothing. Domains you own but never send email from can publish an SPF record of v=spf1 -all and a strict DMARC policy, which makes them harder to spoof.
7. SSL certificates and website status
For each domain that hosts a site, check the certificate expiry date and that it covers both the bare domain and www. Certificate lifetimes are getting shorter, so automatic renewal matters more each year; see the new SSL certificate validity periods. Also confirm that every site loads, that redirects go where you expect, and that parked or defensive domains redirect to your main site rather than showing a registrar parking page.
8. Purpose, cost and next steps
Finally, write one line on why you keep each domain: main site, email, campaign, brand protection or investment. Add the renewal price. Anything with no clear purpose is a candidate to drop at its next renewal, after you have checked nothing depends on it.
Making the audit faster next year
The slowest part of an audit is collecting the data. Names Organizer, a domain manager for Windows, does most of that for you. Import your registrar exports, and it fills in each domain's registrar, dates, nameservers and status from WHOIS and RDAP, and it keeps fields for auto-renew and lock status, privacy, hosting and IP, SSL certificate, renewal price and notes. Custom fields cover anything extra, such as the registrant you confirmed or the person responsible. Names Organizer can also warn you when nameservers or DNS records change unexpectedly, and its DNS and nameservers report prints a record of every domain's settings to file with your audit.
It does not change settings at your registrar, so fixes such as turning on auto-renew are still done there. But having every domain's status in one sorted list turns the yearly audit into a short review rather than a research project.
Frequently asked questions
How often should I audit my domains?
Once a year is a sensible minimum, plus after any change of staff, agency or hosting provider.
Who should be the registrant of a business domain?
The business itself, with a role email address the business controls, not an individual employee or a former web designer.
What is the most common problem a domain audit finds?
Out-of-date contact emails and auto-renew switched off are among the most common, and they are exactly what lets a domain expire unnoticed.
