How Do Domains Get Hijacked Through Expiry and Registrar Accounts?
Published 2026-11-14 · Reviewed 2026-11-14 · 6 min read · By the Ingenious AI team
Is someone impersonating your domain right now?
Run the free DomainGuard scan: lookalike registrations, MX-armed variants, certificate-transparency and CAA checks for your domain, in one report.
Run my free DomainGuard scanThe short answer
Domains are hijacked two ways: they expire and get re-registered — sometimes within minutes by automated drop-catchers watching valuable names lapse — or the registrar account controlling them is compromised and the domain is transferred or repointed. Both failures are administrative, not technical, and both are prevented by the same unglamorous stack: auto-renewal on a monitored payment method, multi-year renewal for crown-jewel names, transfer and registry locks, two-factor authentication on registrar accounts, and a register that names an owner for every domain you hold.
Expiry: the self-inflicted hijack
An expired domain follows a published descent: a grace period at your registrar, a redemption period at punishing prices, then deletion and return to the open market. Waiting at that final step are drop-catching services that register desirable names in the first seconds of availability — desirable meaning traffic, backlinks, brand value, or, in the worst case, your customers' habits. The re-registered name inherits your printed materials, your old links, your app configurations, and any subdomain references scattered across the internet.
The damage list is longer than a lost website. Mail to the expired domain can be received by its new owner — password resets for services registered with addresses at that domain become account-takeover keys. Certificates can be issued to whoever controls DNS. If the lapsed name was a defensive registration, the hijack is worse in one way: the name returns armed with your own foresight about its value. Read the expiry dates in your register the way you read insurance renewals, because that is the correct analogy and the correct emotional register.
Registrar-account compromise: the quiet hijack
The second route never touches expiry. An attacker who controls your registrar account — through a phished password, a reused credential from some other breach, a departed employee's lingering access — can unlock the domain, change its contacts, transfer it out, or simply repoint its DNS and leave the registration looking untouched. DNS-only hijacks are the stealthiest incidents in this field: the website is cloned or redirected, mail is intercepted through altered MX records, and the domain's owner sees nothing wrong in the registrar console they never visit.
Defenses are account-hygiene basics applied with unusual seriousness because the asset is unusually total. Unique passwords in a manager, two-factor authentication (authenticator or hardware key, not SMS where avoidable), access limited to named current staff, and change-notification emails routed to a mailbox that is monitored daily. Transfer lock stays on permanently — it is a default, not a decision — and registry lock, which requires out-of-band verification for changes, belongs on every domain whose loss would be a headline.
The register: one page that prevents both routes
Both hijack paths exploit the same precondition — nobody whose job it is to notice. The countermeasure is a register, kept where the business keeps its other asset lists: every domain, its registrar, its account, its renewal date, its payment method, its lock status, and its named owner. Twice a year, somebody works the register physically: logs into each account, confirms the locks and 2FA, confirms the payment method is current, and confirms the owner still works here. That afternoon is the entire prevention program for most hijack scenarios.
Consolidation makes the register enforceable. Domains scattered across six registrars and three former employees' personal accounts cannot be locked, renewed, or audited coherently. Move everything to one reputable registrar under a company account, accept the small migration effort once, and never let a new domain be registered anywhere else — including by agencies on your behalf without transfer into your account. The rule for vendors is absolute: they may manage, they may not own. A domain registered in an agency's account is, in every way that matters during a dispute, the agency's domain.
Recovery when prevention failed
If a domain has expired into someone else's hands, your options narrow quickly and honesty helps: attempt purchase (the new holder's business model usually is resale), pursue UDRP if the registration is in bad faith against your trademark, and meanwhile sever the name's remaining power — rotate every credential and reset address that referenced it, revoke certificates, and notify services where it was a contact domain. If the hijack is a registrar-account incident in progress, speed runs the other way: registrar support desks have fraud teams who can freeze transfers and revert changes when contacted in hours rather than weeks.
Document from the first phone call. Registrars act on evidence and timelines; insurers and law enforcement will ask for the same file. And treat recovery as the down payment on the register you will now keep — every recovered company in these case studies implements one within the quarter, because the tuition for learning its value twice is more than anyone volunteers to pay.
Your main domain deserves crown-jewel handling
Apply the strictest tier where the value concentrates: your primary domain and any domain that receives mail or hosts login. Multi-year registration (up to ten years where offered) so expiry is a rare, calendarised event rather than an annual one; registry lock; an account whose recovery paths — email, phone — are themselves controlled and reviewed; and monitoring that alerts on DNS changes to your own names, so an unauthorised MX or nameserver change is a same-day alarm rather than a discovery made by a customer.
DomainGuard's posture checks fold several of these signals — locks visible in domain status, expiry horizon, DNS change watching on monitored names — into the same report as your lookalike exposure, because defenders should see their whole name estate in one place. Attackers already do. The gap between their view and yours is the vulnerability; everything in this guide is about closing it.
Five actions to take today
- Keep a register of every domain: registrar, account, renewal date, payment method, locks, named owner.
- Turn on auto-renewal everywhere, multi-year terms for primary domains, and audit payment methods twice a year.
- Enable transfer lock permanently and registry lock on primary and mail-receiving domains.
- Secure registrar accounts with unique passwords, strong 2FA, current-staff-only access, and change alerts to a monitored mailbox.
- Consolidate all domains into one company-owned registrar account; vendors may manage but never own.
Worked example: the defensive domain that nearly lapsed
During a twice-yearly register audit, a fictional retailer — Trailhead Outfitters again, monitoring 4 domains — found its highest-risk typosquat defensive domain 11 days from expiry: the card on file had been replaced during a finance migration and auto-renewal had silently failed. The domain averaged real daily type-in traffic and sat one letter from the store's checkout. Renewal took ten minutes. The same audit found a legacy campaign domain still registered in a former marketing manager's personal account at another registrar; it was transferred into the company account the same week. Neither name made the news, which is what success looks like in this discipline.
FAQ
How fast can an expired domain be re-registered?
Within seconds of becoming available, for names that drop-catchers value. Grace and redemption periods give you expensive second chances; after deletion, assume the name is gone the same day.
What is registry lock and how is it different from transfer lock?
Transfer lock (clientTransferProhibited) blocks registrar transfers and is a console toggle. Registry lock is a stronger, registry-level control requiring manual out-of-band verification for transfers and key changes — slower to change, far harder to abuse.
Our agency registered our domains years ago. Are they ours?
Legally and practically, the registrant of record controls them. If that is the agency, arrange transfer into your own account now, while the relationship is warm — this conversation is only ever awkward before it is urgent.
Can monitoring detect a DNS hijack of our own domain?
Yes, if your own names are watched for change. Unexpected MX, nameserver, or A-record changes on a monitored domain are high-severity alerts precisely because they indicate account-level compromise.
Is multi-year registration worth it?
For primary domains, yes: it converts an annual failure opportunity into a rare scheduled event, and the cost difference is trivial against the asset. Keep auto-renewal on as well — belts and braces are cheap here.