---
title: "Domain Security Checklist: How to Protect Your Business Domain from Hijacking"
description: "Your domain controls your website, email, and logins. This checklist covers registrar locks, DNSSEC, account security, renewals, email authentication, and monitoring to protect your business domain from hijacking and outages."
canonical_url: "https://cinnamon.digital/insights/domain-security-checklist"
---

> Index of every page on this site: [llms.txt](https://cinnamon.digital/llms.txt)

**Your domain is the single point of control for your website, email, and many of your logins.** Whoever controls the domain can redirect traffic, receive password reset emails, and obtain valid security certificates in your name. Yet domains are often registered by a former employee, on a personal card, behind a password nobody remembers. This checklist covers the controls every business domain should have.

## 1. Know what you own and who controls it

Start with an inventory:

- Every domain your business uses, including old brands, campaign sites, and common misspellings.
- Which registrar holds each domain and which account it sits in.
- Who has login access, and whose email address receives registrar notices.
- Where DNS is hosted, which may be a different provider from the registrar.

Move domains out of personal accounts and into a company-owned account that uses a shared role address such as `domains@yourcompany.com`, not an individual's inbox.

## 2. Secure the registrar account

The registrar account is the most common point of attack.

- Turn on multi-factor authentication, preferably with a security key or authenticator app instead of SMS.
- Use a unique, long password stored in a company password manager.
- Limit access to the few people who need it, and use individual user roles where the registrar supports them.
- Review access when anyone leaves the company.
- Make sure the account's recovery email is on a domain you control, and is not the domain being protected, so a DNS problem cannot lock you out of recovery.

## 3. Apply transfer and update locks

<table>
<thead>
  <tr>
    <th>
      Control
    </th>
    
    <th>
      Where it is set
    </th>
    
    <th>
      What it protects against
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Registrar lock (clientTransferProhibited)
    </td>
    
    <td>
      Your registrar account
    </td>
    
    <td>
      Unauthorized transfers to another registrar
    </td>
  </tr>
  
  <tr>
    <td>
      Update and delete prohibitions
    </td>
    
    <td>
      Your registrar, where offered
    </td>
    
    <td>
      Unauthorized changes to nameservers or contacts
    </td>
  </tr>
  
  <tr>
    <td>
      Registry lock
    </td>
    
    <td>
      The domain's registry, through a registrar that offers it
    </td>
    
    <td>
      Changes even if the registrar account is compromised
    </td>
  </tr>
</tbody>
</table>

Registry lock adds manual verification for any change and is worth the cost for your primary domain and any domain that handles email or logins.

## 4. Prevent accidental expiration

Expired domains cause outages and can be registered by someone else once released.

- Turn on auto-renew for every domain you want to keep.
- Renew primary domains for multiple years.
- Keep the payment method current and set a calendar reminder 90 days before each expiry.
- Make sure renewal notices go to a monitored shared inbox.

## 5. Harden DNS

- **Enable DNSSEC** if your registrar and DNS provider support it, so resolvers can reject forged DNS answers.
- **Secure the DNS provider account** with the same MFA and access controls as the registrar.
- **Remove stale records.** DNS entries pointing to cloud services you no longer use can be claimed by others, a risk known as subdomain takeover.
- **Add CAA records** to specify which certificate authorities may issue TLS certificates for your domain.
- **Keep a record of your zone** so you can restore it quickly if something changes unexpectedly.

## 6. Protect your email with SPF, DKIM, and DMARC

Attackers do not need to hijack your domain to impersonate it. Email authentication stops others from sending mail that appears to come from you.

- **SPF** lists the servers allowed to send mail for your domain.
- **DKIM** signs outgoing messages so recipients can verify them.
- **DMARC** tells receivers what to do with mail that fails those checks and sends you reports. Start at `p=none` to monitor, then move to `quarantine` and `reject` once legitimate senders pass.

For domains that never send email, publish a strict SPF record and a DMARC policy of `reject` so they cannot be spoofed.

## 7. Monitor for changes and lookalikes

- Set alerts for changes to nameservers, DNS records, registrar contacts, and domain status.
- Watch certificate transparency logs for certificates issued for your domain that you did not request.
- Monitor new registrations of lookalike domains that use your brand name, common typos, or swapped characters, which are often used for phishing.

## 8. Write down the recovery plan

When something goes wrong, speed matters. Document:

- Registrar and DNS provider support contacts and account numbers.
- Who is authorized to make emergency changes.
- How to verify ownership, such as invoices and registration records.
- The steps for restoring DNS from your saved zone records.

## Quick self-assessment

If you answer "no" or "not sure" to any of these, start there:

1. Are all your domains in a company-owned registrar account?
2. Is MFA enabled on both your registrar and DNS provider?
3. Is auto-renew on for every domain you need?
4. Is a transfer lock applied to every domain?
5. Do you publish a DMARC policy?
6. Would you know within a day if your nameservers changed?

## Where to start

Begin with the inventory and account security, since those close the most common gaps for the least effort. If you want a team to audit and harden your setup, our [DNS and domain security operations](https://cinnamon.digital/services/dns-domain-security-operations) service covers registrar consolidation, locks, DNSSEC, email authentication, and ongoing monitoring.

## Sitemap

See the full [sitemap](https://cinnamon.digital/sitemap.md) for all pages.
