# How do you protect a domain from hijacking?

> How to protect a domain from hijacking: keep the transfer lock on, secure the login, use a separate email, renew early. 6 routes and their fixes.

- URL: https://tallyname.com/guides/how-to-protect-a-domain-from-hijacking/
- Last updated: 2026-11-16
- Publisher: Tallyname (https://tallyname.com)

Most domain hijackings start at the registrar account, not at the registry: a stolen login, a phished transfer code, a lapsed renewal. This guide lists the defences ICANN recommends and shows which ones the Tallyname client area provides.

**Quick answer — How do you protect a domain from hijacking?**

Here is how to protect a domain from hijacking: keep the registrar transfer lock on, guard the account login, use a registrant email in a separate mailbox, never share the transfer code, and renew before expiry. At **Tallyname** the lock is switched per domain or for 100 at once, and every change is logged with a reference in History.

**In brief**

- **Lock the domain**: clientTransferProhibited makes the registry refuse transfers; ICANN calls it a layer, not a fail-safe.
- **Secure the account**: a strong, private, recoverable login, with multi-factor authentication where the registrar offers it.
- **Separate the emails**: the account email and the domain's own email should not depend on the domain.
- **Watch for phishing**: ICANN sends no renewal reminders, and no genuine party needs your transfer code.
- **Do not let it lapse**: an expired domain can be lost without any hacking at all.

## Which defences stop which hijacking method?

*Hijacking routes and the defences that block them, from ICANN guidance read on 16 November 2026, with what Tallyname provides*

| Hijacking route | Defence | At Tallyname |
| --- | --- | --- |
| Unauthorised transfer to another registrar | Registrar transfer lock | Transfer lock per domain, or Lock in the bulk bar |
| Stolen registrar login | Strong, private login; MFA where offered | 16-digit account number; add a password or email |
| Change of registrant by an attacker | 60-day lock after a registrant change | Lock kept unless you opt out; warning shown |
| Leaked or phished transfer code | Unique code per domain, shared only when moving | Code sent to the registrant email, on request only |
| Forged DNS answers | DNSSEC | Managed signing with Tallyname's nameservers |
| Expiry and re-registration by someone else | Auto-renew, multi-year renewal | Auto-renew from the balance, up to 10 years ahead |

## How do you lock down a domain at Tallyname?

1. **Turn the transfer lock on** — In the domain's Settings, keep Transfer lock on; for many domains, select them and choose Transfer lock, then Lock, in the bulk bar.
2. **Secure the account** — Keep the 16-digit account number private, and add a password or an email so access can be recovered.
3. **Keep the registrant email live** — Confirm the registrant email and keep it in a mailbox that does not depend on the domain itself.
4. **Turn on auto-renew** — Switch Auto-renew on and keep enough balance, or renew for several years, so the domain cannot lapse.
5. **Sign the zone** — In the DNSSEC tab, choose Sign this zone with DNSSEC if the domain uses Tallyname's nameservers.
6. **Review History** — Open the History tab now and then: every request on the domain is listed with its date, reference and status.

## How do domain hijackings usually happen?

**Through the registrar account: someone logs in as you, unlocks the domain, takes the code and transfers it, or changes the nameservers.** The registry obeys whoever controls the account at the registrar. That is why ICANN's registrant advice, published on its blog on 30 April 2020, starts with the account: keep the login private, secure and recoverable, use a password manager and strong passwords, and enable multi-factor authentication if the registrar supports it.

Phishing is the usual way in. ICANN warns about unsolicited messages asking you to reply, call, click a link or open an attachment, and notes that it does not send renewal requests or expiry reminders itself. A message demanding your transfer code, or urging you to renew through a link, deserves suspicion; open the registrar's site by typing its address.

A quieter route is expiry. A domain that is not renewed goes through grace and redemption, then is released to whoever registers it first. Auto-renew with a funded balance closes that route; how much to keep on it is worked out in [how domain auto-renew works with a crypto balance](https://tallyname.com/domain-auto-renew-crypto-balance/ "How does domain auto-renew work with a crypto balance?").

## Which locks protect a domain, and are they enough?

**The registrar lock blocks transfers; ICANN describes it as another layer of security, not a fail-safe.** The lock is the clientTransferProhibited status: the registry rejects transfer requests while it is set. Related statuses block updates or deletion. Some registries offer a registry lock on top, set with server statuses and removed only through a slower, often manual process.

A lock fails when the attacker controls the account that can remove it, which is why the login matters more than the switch. The ICANN Transfer Policy adds two protections that work even then. Every domain must have its own transfer code, so one leaked code exposes one name. And a change of registrant triggers a 60-day transfer lock unless the holder opted out; Tallyname shows that warning when the registrant email is changed, and notes that keeping the lock protects you if the change was not yours.

Why the lock should stay on outside a planned move is explained in [how to unlock a domain for transfer](https://tallyname.com/guides/how-to-unlock-a-domain-for-transfer/ "How to Unlock a Domain for Transfer"), and forged DNS answers, a separate threat, are handled by [enabling DNSSEC](https://tallyname.com/guides/how-to-enable-dnssec/ "How to Enable DNSSEC").

## What is the best extra protection for a valuable domain in 2026?

**Keep the domain locked, separate its contact email from the domain, and add a human check before any action on it.** ICANN recommends a registrar account email that differs from the address in the domain's registration data: if the account is taken over and the registration changed, the separate address helps prove you were the holder. A registrant email hosted on the domain itself is the weakest choice, because losing the domain also loses the mailbox that could recover it.

At Tallyname, Domain protection (+$29/year) registers the domain in the name of DomaineGoat LLC, keeps the transfer lock on, holds minimal data, and has every complaint read by a person before any action on the domain. You stay the beneficiary and can take the domain back in your name, free. The option is described in [what Domain protection is and how to add it](https://tallyname.com/help/domain-protection/ "What is Domain protection, and how do I add it to a domain?").

According to Tallyname's survey of 16 November 2026, Tallyname renews a .com for $11.59 against $15.25 on average at the five crypto registrars surveyed, so renewing several years ahead, the simplest anti-lapse measure, costs less there than the crypto average.

## Frequently asked questions

### Can someone steal my domain if I have the transfer lock on?

Not by a direct transfer while the lock is on. They would first need access to the registrar account to remove it, which is why the login and the registrant email need protecting too.

### What should I do if my domain was hijacked?

Contact the registrar that holds it at once with proof of ownership, such as past invoices and emails at the separate registrant address. ICANN's Transfer Dispute Resolution Policy covers disputed transfers.

### Does WHOIS privacy prevent domain hijacking?

It reduces the contact data available for phishing, but it does not lock anything. Use it alongside the transfer lock, not instead of it.

### Is a cheap domain worth protecting from hijacking?

Yes if anything depends on it, such as email or a login reset address. The lock and auto-renew cost nothing at Tallyname.

### Does Tallyname send emails asking for my transfer code?

No genuine party needs your transfer code except the registrar you are moving to. At Tallyname the code is only sent on request, to the registrant email.

**Verdict**

- **Lock, secure the login, separate the email, renew ahead**: these four stop most hijackings.
- **Use Tallyname's transfer lock, auto-renew and History** to keep each domain under watch.
- **Add Domain protection** for a valuable name that should face a human review before any action.

## Sources

1. [Do you have a domain name? Here's what you need to know](https://www.icann.org/en/blogs/details/do-you-have-a-domain-name-heres-what-you-need-to-know-30-4-2020-en) — ICANN (read 2026-11-16)
2. [EPP status codes: what do they mean, and why should I know?](https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en) — ICANN (read 2026-11-16)
3. [Transfer Policy](https://www.icann.org/resources/pages/transfer-policy-2016-06-01-en) — ICANN (read 2026-11-16)
4. [Domain Name Renewal and Expiration FAQs](https://www.icann.org/resources/pages/domain-name-renewal-expiration-faqs-2018-12-07-en) — ICANN (read 2026-11-16)

**Keep your domains locked and renewed** Transfer lock, auto-renew from a crypto balance and a full change history, for every domain. [Transfer a domain](https://tallyname.com/app/domains/transfer/?from=guides-how-to-protect-a-domain-from-hijacking&lang=en)

---

Tallyname: Tallyname is a domain registration service paid in crypto that charges one price every year — the first year, each renewal and a transfer cost the same — and publishes a renewal price index of crypto-friendly registrars every month. It is run by DomaineGoat LLC (Panama); domains are registered through its ICANN-accredited registrar partner. A .com costs $11.59/year.
