# Domain Hijacking: 7 Essential Checks to Protect Your Domain

Source: https://hostreta.com/2026/11/domain-hijacking/

Domain hijacking is the unauthorised takeover of a domain registration. Your domain is the key to your website, your email, and every account that sends password resets to your inbox. If an attacker takes control of it, they may redirect your site, reroute incoming email, and interfere with account recovery. Domain hijacking can disrupt your business even when your website files remain intact.

This guide explains how domains get hijacked, how registrar lock and transfer codes protect you, how to secure your registrar account, the warning signs of an attack, and what to do if it happens.

Table of Contents

[Toggle](#)

- [How domain hijacking happens](#How_domain_hijacking_happens)
- [Registrar lock and transfer codes](#Registrar_lock_and_transfer_codes)
- [Securing your registrar account](#Securing_your_registrar_account)
- [Warning signs of an attack](#Warning_signs_of_an_attack)
- [What to do if it happens](#What_to_do_if_it_happens)
- [Security services worth adding](#Security_services_worth_adding)
- [Key takeaways](#Key_takeaways)
- [Domain hijacking versus DNS hijacking](#Domain_hijacking_versus_DNS_hijacking)
- [Domain hijacking prevention: 7 checks for your business](#Domain_hijacking_prevention_7_checks_for_your_business)
- [Respond to suspected domain hijacking in order](#Respond_to_suspected_domain_hijacking_in_order)
- [Frequently asked questions about domain hijacking](#Frequently_asked_questions_about_domain_hijacking)
- [Does domain privacy prevent domain hijacking?](#Does_domain_privacy_prevent_domain_hijacking)
- [Does DNSSEC stop someone stealing my registrar account?](#Does_DNSSEC_stop_someone_stealing_my_registrar_account)
- [Is an unexpected outage proof of domain hijacking?](#Is_an_unexpected_outage_proof_of_domain_hijacking)
- [Can I guarantee that a transfer lock prevents every attack?](#Can_I_guarantee_that_a_transfer_lock_prevents_every_attack)

- [Domain hijacking prevention starts with ownership](#Domain_hijacking_prevention_starts_with_ownership)
- [Protect the recovery chain against domain hijacking](#Protect_the_recovery_chain_against_domain_hijacking)
- [Use a documented change process](#Use_a_documented_change_process)
- [Review alerts without trusting the alert itself](#Review_alerts_without_trusting_the_alert_itself)
- [Prepare an incident evidence pack](#Prepare_an_incident_evidence_pack)
- [Coordinate the business response](#Coordinate_the_business_response)
- [Verify recovery beyond the registrar dashboard](#Verify_recovery_beyond_the_registrar_dashboard)
- [Ask about controls before choosing a domain service](#Ask_about_controls_before_choosing_a_domain_service)
- [Review the domain hijacking plan after team changes](#Review_the_domain_hijacking_plan_after_team_changes)
- [A practical domain hijacking response example](#A_practical_domain_hijacking_response_example)

## How domain hijacking happens

- Stolen registrar login: a route attackers can exploit. Attackers use phishing, leaked passwords, or reused passwords to log in and change nameservers or start a transfer.

- Compromised email: if attackers control the email on your registrar account, they can reset the password.

- Expired email domain: if your registrar email uses a domain you let expire, someone can register it and receive your reset emails.

- Social engineering: tricking registrar support into making changes.

- Accidental expiry: not technically hijacking, but a lapsed domain can be bought by someone else.

## Registrar lock and transfer codes

Registrar lock (also called transfer lock or clientTransferProhibited) stops your domain from being moved to another registrar. Keep it on at all times, and only turn it off when you’re transferring the domain yourself.

The transfer code (EPP or auth code) is like a password for moving your domain. Never share it by email or chat, and request a new one if you think it was exposed.

For high-value domains, some registrars offer a stronger registry lock, which adds registry-level restrictions and a verification process for covered changes. Availability, scope and unlocking procedures vary.

## Securing your registrar account

- Turn on two-factor authentication using a strong supported method, such as a suitable security key or authenticator, with a reliable recovery plan. Compare options in [Two-Factor Authentication Apps Compared](https://hostreta.com/2026/10/two-factor-authentication-apps-compared/).

- Use a unique, strong password stored in a password manager.

- Use a secure email for the account — ideally on a different domain from the one you’re protecting, with its own 2FA.

- Keep contact details current so you receive alerts and renewal notices.

- Turn on login and change notifications.

- Limit access: only the people who truly need registrar access should have it.

Choosing a registrar with these features? See [Best Domain Registrars for Privacy and Security](https://hostreta.com/2026/10/domain-registrars-privacy-security/).

## Warning signs of an attack

- Emails about password resets, login attempts, or transfer requests you didn’t make.

- Unexpected changes to nameservers or DNS records.

- Your website suddenly showing different content, or email stopping without explanation.

- Unexpected registration data or registrar changes that need confirmation through the official account and support channel.

Phishing emails pretending to be your registrar are common, so learn to spot them: [Phishing Emails: How to Spot Them in 5 Seconds](https://hostreta.com/2026/10/phishing-emails-how-to-spot-them-in-5-seconds/).

## What to do if it happens

- Contact your registrar immediately by phone or emergency support, explain the situation, and ask them to freeze the domain.

- Secure your email and change passwords for your registrar and email accounts.

- Gather evidence: receipts, account history, screenshots, and WHOIS records.

- If the domain was transferred, your registrar can open a dispute with the new registrar. ICANN’s transfer dispute process exists for this.

- Tell customers through other channels if email or the website may be compromised.

## Security services worth adding

Monitoring and logging work best alongside layered protection. [SiteLock](https://kawedma.com/sitelock.php) scans for malware, [CodeGuard](https://kawedma.com/codeguard.php) keeps off-site backups with version history, and [360 Monitoring](https://kawedma.com/store/360monitoring) alerts you to downtime. Secure hosting matters too: [Kawedma WordPress hosting](https://kawedma.com/wordpress-hosting.php) and [managed WordPress hosting powered by Rocket.net](https://my.hosting.com/aff/08a016e41d3100e5460ff6ebee1b5e0a91e643d6) include firewalls and automatic updates. Use [NordVPN](https://kawedma.com/store/nordvpn) when managing sites over public Wi-Fi.

## Key takeaways

- Protect both the registrar login and its recovery email.

- Keep registrar lock on and protect your transfer code.

- Use 2FA and a secure, separate email for your registrar account.

- Keep contact details current and act fast at the first warning sign.

## Domain hijacking versus DNS hijacking

Use our [nameservers vs DNS records guide](https://hostreta.com/2026/10/nameservers-vs-dns-records/) to identify whether the unexpected change concerns delegation or data inside a zone. The [DNSSEC guide](https://hostreta.com/2026/10/what-is-dnssec-and-should-you-turn-it-on/) explains validation’s role; it does not replace account ownership and recovery controls.

These incidents overlap but are not identical. Domain hijacking concerns control of the registration. A DNS takeover can change where visitors or email go without moving the registration to a new owner. A hacked WordPress site can display malicious content while the registrar and DNS remain unchanged. Identifying which layer changed helps you contact the right provider.

Observation
Where to investigate

Unexpected registrar or registrant change
Registrar account and transfer history

Unexpected nameservers or mail records
Registrar and authoritative DNS provider

Changed website content with unchanged DNS
Hosting account, website files and application access

Missing password reset emails
Mailbox access, mail forwarding and domain mail records

A transfer lock is a useful layer against domain hijacking, but it does not replace securing the account. An attacker with sufficient registrar access may be able to remove a lock or change settings it does not cover. Review [ICANN’s registrant guidance on protecting domains](https://www.icann.org/en/blogs/details/do-you-have-a-domain-name-heres-what-you-need-to-know-26-3-2018-en) and your provider’s own security documentation.

## Domain hijacking prevention: 7 checks for your business

- Confirm which business account owns the registration and who is authorised to manage it.

- Use a unique password and the strongest supported authentication method that you can reliably recover.

- Secure the recovery mailbox with its own strong authentication and review forwarding rules.

- Keep the transfer lock enabled when no authorised transfer is in progress.

- Treat transfer authorisation codes as secrets and provide them only through the intended transfer workflow.

- Review login, DNS and registration-change notifications promptly.

- Keep a current inventory, known DNS configuration and registrar support contact outside the affected domain.

Do not put passwords, transfer codes or recovery codes into the inventory. Record who holds approved access and how the organisation can recover it. Review access when staff or suppliers leave. For an important domain, ask whether registry lock is available and which changes it restricts before deciding whether it fits your workflow.

## Respond to suspected domain hijacking in order

Open the registrar’s known website directly and contact its official support channel. Report the domain, the first observed change and whether you still control the account. Request an urgent review of unauthorised changes and ask what containment actions the provider can take. Do not trust a phone number or recovery service included in a suspicious notification.

Preserve receipts, support case numbers, timestamps and relevant alerts before making extensive changes. Use a trusted device to secure the recovery email and account access. Check for unauthorised forwarding rules and sessions. Once control is restored, compare nameservers and DNS records with your known configuration and test both the website and mail.

ICANN’s [domain transfer FAQ](https://www.icann.org/resources/pages/name-holder-faqs-2017-10-10-en) explains transfer mechanisms and complaint routes. A complaint is not a promise of immediate recovery. Work with the registrar on the evidence and available procedures, especially when a domain has moved between registrars.

## Frequently asked questions about domain hijacking

### Does domain privacy prevent domain hijacking?

Privacy can limit exposure of contact information, but it does not secure the registrar password, recovery mailbox or DNS account. Treat privacy and account security as separate controls.

### Does DNSSEC stop someone stealing my registrar account?

No. DNSSEC authenticates DNS data; it does not replace account authentication or a transfer lock. Protect each relevant management account and review who can alter DNS or registration settings.

### Is an unexpected outage proof of domain hijacking?

No. Expiration, incorrect DNS changes and hosting failures can also cause outages. Check the registrar status, authoritative DNS and hosting service before deciding which recovery process applies.

### Can I guarantee that a transfer lock prevents every attack?

No single setting guarantees protection. Combine account security, transfer controls, monitoring and a recovery plan. The goal is to reduce the chance of domain hijacking and detect unauthorised changes quickly.

## Domain hijacking prevention starts with ownership

Keep an accurate map of the business accounts that control registration, DNS, hosting and recovery email. These roles can belong to different providers. Record the responsible person and the official support route for each role, so an incident does not begin with a search for the right company.

The business should understand who is authorized to approve a transfer or a significant configuration change. Domain hijacking prevention becomes harder when a critical name sits in an undocumented personal account belonging to a former supplier. Arrange a supported handover while everyone involved is available.

Keep the account map separate from secrets. A general operational note should explain ownership and recovery responsibility without exposing passwords, transfer codes or emergency recovery material.

## Protect the recovery chain against domain hijacking

Include [domain renewal ownership and expiry checks](https://hostreta.com/2026/11/domain-renewals/) in the recovery plan. Keep registration continuity and access protection as separate checks so an expired domain is not mistaken for a confirmed account takeover.

A strong registrar login is only one part of the access path. Review the mailbox and other supported methods used for account recovery. Make sure the organization can maintain them and that a staffing change does not silently remove access.

Check whether the recovery route depends entirely on the domain being protected. That dependency can complicate a domain hijacking incident if mail routing is affected. Choose a recovery design appropriate to the provider and business, and document how authorized people will use it.

Do not test recovery by exposing credentials or disrupting a working account. Follow the provider’s supported review process. Keep sensitive recovery information in the approved credential system with access limited to the appropriate people.

## Use a documented change process

Record the reason for a planned transfer, nameserver change or contact update before it happens. Include the person approving it and the expected outcome. This gives administrators a reference when an alert arrives and helps distinguish legitimate maintenance from a possible domain hijacking attempt.

Confirm unusual requests through a known channel. An urgent message asking for a transfer code or a change to recovery details deserves verification independent of the supplied link. Do not let a convincing logo or familiar display name replace that check.

After an authorized change, inspect the result and record completion. A requested change and an applied change are different states. Keeping both visible reduces confusion during later domain hijacking investigations.

## Review alerts without trusting the alert itself

Notifications can help detect unexpected activity, but attackers can imitate them. Open the known registrar or provider site directly and review the account state. Use the official support route if a message claims something urgent that you cannot confirm.

Domain hijacking monitoring should cover the settings relevant to your services. Keep known nameservers and important DNS records documented, along with the registration owner and renewal arrangements. A change should be reviewed in context rather than judged solely by whether the website still loads.

Assign an owner to alerts and define what happens when that person is away. A warning is useful only if someone can evaluate it and take the appropriate next step.

## Prepare an incident evidence pack

Keep registration receipts and legitimate account references available through the organization’s normal records process. During a suspected incident, preserve the relevant messages, times and support case numbers. Do not publish the entire evidence pack in a public forum.

Describe what changed and what remains under your control. For domain hijacking, that distinction helps the registrar assess the case. A hosting compromise with unchanged registration may require another response team, even when visitors see a similar symptom.

Keep observations factual. Do not publicly accuse a person or provider based only on an outage or unfamiliar lookup. Gather evidence, contact the responsible service and document the available containment and recovery process.

## Coordinate the business response

Decide who communicates internally and who works with the provider. If customer-facing services are affected, use the organization’s established incident communication process. Confirm facts before making broad statements about what data or accounts were compromised.

A domain hijacking incident can affect website links, mail routing and account recovery. Review those dependencies with the relevant owners. Avoid assuming that restoring a home page confirms the mail service and every connected account are secure.

Keep a single timeline of provider instructions and actions taken. This helps prevent different team members from applying conflicting changes while the incident is being investigated.

## Verify recovery beyond the registrar dashboard

After the provider confirms restored control, review authorized access, recovery settings and the intended public configuration. Use the approved account-management process and preserve evidence before making broad changes. Follow any additional provider instructions for the case.

For domain hijacking recovery, test both the website and mail. Check the important customer routes and any business accounts that depend on messages sent to the domain. Record unresolved issues separately from the administrative recovery confirmation.

Review the underlying cause with the responsible team. A restored registration does not automatically explain how the incident occurred. Document the corrective actions and ownership so the same access weakness is not left in place.

## Ask about controls before choosing a domain service

When evaluating a registrar, ask about supported authentication, delegated access, change alerts, transfer controls and recovery procedures. For a critical name, clarify the availability and scope of any additional locking service. Do not assume a product label describes every protected action.

Promotional recommendation: Consider [KAWEDMA’s domain services](https://kawedma.com/) if you are comparing domain services alongside hosting or business email. Ask which domain hijacking prevention controls and support procedures apply to the actual registration and extension. Confirm the service terms rather than assuming a complete protection guarantee.

Review [ICANN’s domain security resources](https://www.icann.org/resources/pages/securely-managing-domain-name-2020-08-26-en) for further reading, and use the current instructions from the provider managing your account.

## Review the domain hijacking plan after team changes

A new supplier, employee departure or mailbox migration can alter the account recovery chain. Review ownership and supported access at those moments rather than waiting for the next incident. Keep the inventory current and retire obsolete assumptions.

Practise a discussion-based incident walkthrough with the team: who receives the alert, how they verify it, which provider they contact and what evidence is available. Domain hijacking preparation does not require making risky live account changes merely to demonstrate a scenario.

At the end of the review, assign remaining work and record completion evidence. The useful outcome is an organization that can maintain its accounts and respond through known channels, with no claim that one setting prevents every possible attack.

## A practical domain hijacking response example

Imagine that a business receives an unexpected nameserver-change notice. The person monitoring alerts does not use the link in the message. They open the known registrar site and compare the current settings with the documented configuration. They also ask the designated change owner whether an authorized project is in progress.

If the change is unexplained, the business contacts the provider through its official support channel and preserves the relevant timeline. One person coordinates the case while the website and mail owners collect their own observations. The team does not assume that every failed email or changed page has the same cause; it records what each service actually shows.

After the provider resolves the account issue, the business verifies the intended public configuration and the affected customer routes. It checks whether the recovery mailbox and authorized access still match the approved design. Remaining application problems are assigned separately, rather than hidden by a successful registrar login.

This domain hijacking example illustrates a process, not a promise that every case has the same outcome. Recovery depends on the evidence, provider procedures and incident circumstances. The preparation that helps is knowing who owns the accounts, where legitimate support is reached and which configuration the business expects to see.

Keep the final support reference and the review actions with the incident record so a future maintainer can understand the result.

Review authorized access again after completing any account recovery or supplier handover.
