Blog / Web management /
Domain expiry and DNS hijacking: protecting client domains
Your website can be in perfect health and still vanish overnight. All it takes is an expired domain registration or a DNS record someone changed.
The domain is the address people type. DNS points that address at the services behind it. Lose control of either and the site, the email and everything else tied to that domain can stop.
When I pick up a client site, the first thing I ask for is the registrar login, before I touch a single page. Renewals happen quietly and DNS rarely changes, so the risk is easy to forget, right up until something goes wrong. Protect the registrar account, write down who owns it, and make sure the organisation can get back in without relying on one person’s memory.
Know who controls the domain
Record the registrar, legal owner, account email, renewal date, payment method and the people authorised to make changes. The domain should normally be registered in the business’s name, with the service provider given delegated access where needed. If an agency or a former employee owns the account personally, the organisation can struggle to renew or transfer the domain later.
Keep the account’s recovery email and phone current. Use a password manager and multi-factor authentication where available. Give each authorised person their own login, not a password pasted into a chat or spreadsheet. Review access when someone leaves or a service relationship ends. One registrar account can affect several websites, so I treat its permissions like hosting access.
Make expiry difficult to miss
Enable auto-renew where it is appropriate and the payment method is kept current. Auto-renew isn’t oversight. Cards expire, billing emails go to old inboxes and accounts get suspended for unrelated reasons. Set calendar reminders well ahead and name someone to confirm the renewal actually went through.
Keep a record of the domain’s term, the renewal route and the support contact. Expiry and recovery rules vary by registrar and registry, so don’t assume every domain has the same grace period. If a renewal is missed, contact the registrar quickly through its verified support channel, and resist the urge to make speculative DNS changes while you recover access.
Protect DNS changes
DNS hijacking can happen when an attacker gains access to the registrar or DNS provider and changes records or nameservers. A visitor may then be sent to a fake site, or email may stop reaching the organisation. Use strong unique credentials, multi-factor authentication, registrar lock or transfer controls where supported, and alerts for account or nameserver changes.
Keep a known-good copy of the current DNS configuration, with the purpose and owner of the important records. Store it securely and update it after approved changes. Never copy records blindly: mail, verification, CDN, payment and subdomain records all do different jobs. An old record might be stale, but deleting the wrong one can break a working service.
Where supported and appropriate, consider DNSSEC as an additional integrity measure, but understand the setup and renewal responsibilities first. It does not prevent an account takeover or replace access controls. If the business uses a DNS provider, know how to contact it and who can approve an emergency change.
Make changes deliberately
Before a migration or provider change, inventory the site, email, subdomains and third-party services that depend on the domain. Agree on a change window, identify who can verify each service and keep a rollback plan. DNS changes are cached in different places, so they may not reach every user at once. Don’t change several records at once without noting what each one does.
After a change, test the website, secure connection, forms, email delivery and critical integrations. A homepage loading is not enough to prove the domain is healthy. Check the hostnames the business actually uses and monitor for errors after the work.
Plan for account recovery
If control is lost, use the registrar’s recovery process and gather proof of the organisation’s ownership. Contact the DNS provider and hosting provider through verified channels, and alert the people responsible for email and security. If visitors may have reached a fraudulent destination, follow the organisation’s incident process. Do not post account details or verification codes publicly.
A short, current domain register is dull work with a very practical payoff. It gives the next person a route to act before a missed renewal becomes an outage.
Responding when control is in doubt
If the site or email suddenly stops resolving, start by checking the registrar and DNS provider through a known route—not by clicking a link in an unexpected message. Confirm whether the account is accessible, whether nameservers changed and whether the hosting destination still responds. Preserve evidence such as alert emails and timestamps. If unauthorised changes are suspected, involve the organisation’s security contact and follow the provider’s account recovery process.
Restore a known-good DNS configuration only after you have confirmed the correct records and the change is authorised. A hurried copy from an old screenshot may omit records that were added later. Once service returns, review account access, change notifications, recovery details and the source of the incident. Update the register so the next response starts with current information rather than guesswork.
Related reading
- Domain names and SEO: does the name still matter?
- Uptime isn’t enough: monitoring forms, checkout and email
- Hosting outages: what I tell clients
Look up the registrar owner, renewal date and recovery contact for one important domain. Who could restore access if the usual administrator were unavailable?