How to Monitor a Website for Unauthorized DNS Changes and Domain Hijacking
DNSdomain hijackingregistrar securitywebsite monitoringnameservers

How to Monitor a Website for Unauthorized DNS Changes and Domain Hijacking

PPrivacy Sentinel
2026-11-18
7 min read

Learn how to monitor DNS records, nameservers, and registrar settings to detect unauthorized changes and respond to possible domain hijacking.

Unauthorized DNS changes can redirect a website, interrupt email, or send visitors to a fraudulent destination without changing the site’s visible code. This guide explains how to document your approved DNS configuration, monitor the records and nameservers that control your domain, check registrar protections, and respond safely when something does not match.

Overview

DNS, or the Domain Name System, connects a human-readable domain name with services such as a web server, email provider, verification platform, or certificate authority. A domain hijacking incident may involve a compromised registrar account, altered nameservers, a changed DNS record, or an unauthorized transfer attempt. The practical risk is not limited to a broken homepage: an attacker may redirect visitors, intercept email, imitate a login page, or use a trusted domain to support a scam.

The most reliable way to detect an unauthorized DNS change is to establish a known-good baseline and compare it with current information on a recurring schedule. Your baseline should be stored somewhere separate from the DNS provider account and should identify the purpose of each record, its expected value, and the person or system authorized to change it.

DNS changes can be legitimate. Hosting migrations, email-platform changes, verification requests, CDN configuration, certificate deployment, and temporary testing can all alter records. Monitoring is therefore not about treating every difference as an attack. It is about making every difference explainable, approved, and recorded.

What to track

1. DNS records

Start with a complete export or written inventory of the records used by your domain and its important subdomains. Record the hostname, type, value, time to live (TTL), purpose, and date of last approval. The exact interface varies by DNS provider, so use the provider’s current documentation when exporting or reviewing records.

RecordWhat it commonly controlsWhat to verify
AMaps a hostname to an IPv4 address.Confirm the address belongs to your approved hosting, CDN, or service provider.
AAAAMaps a hostname to an IPv6 address.Check that the IPv6 destination is expected and maintained. An overlooked record can direct IPv6-capable visitors somewhere different from IPv4 visitors.
CNAMEPoints one hostname to another hostname.Confirm the target is correct, still owned or authorized by you, and needed. Pay attention to unused subdomains.
MXIdentifies the servers that receive email for a domain.Compare the mail hosts with your approved email provider and investigate unfamiliar destinations.
TXTStores text used for verification, email authentication, and other service configurations.Review SPF, DKIM-related, and service-verification entries. Remove obsolete entries only after confirming they are no longer required.
NSIdentifies the authoritative nameservers for a domain or delegated subdomain.Verify that nameservers match the registrar and DNS provider you intentionally selected. Unexpected NS changes are high priority.
CAACan indicate which certificate authorities may issue certificates for a domain.Confirm the entries reflect your certificate-management plan. Do not add or remove them without understanding the effect on certificate issuance.

Also document DNSSEC status if your registrar and DNS provider support it. DNSSEC is a separate layer from ordinary record review, and changing providers or nameservers may require careful handling of signing and delegation details. Treat its status as an infrastructure setting to verify during migrations rather than assuming it remains unchanged.

2. Nameservers and registrar settings

Record the authoritative nameservers shown in your registrar account and compare them with independent DNS lookups. The registrar’s account view tells you what is configured at the domain-management level; an external lookup helps show which nameservers are answering publicly. A mismatch may be caused by propagation or a recent approved change, but it deserves investigation.

Review registrar lock or transfer-lock settings, account recovery email addresses, multifactor authentication, notification preferences, and the list of users or delegates with access. Names and menu labels differ between registrars. Look for settings that restrict unauthorized transfers or require additional confirmation before sensitive domain changes. Check the registry and registrar’s current requirements when ownership, contact details, or transfer status changes.

3. A change record

Keep a simple change log with the requested change, affected record, old value, new value, reason, approver, implementation time, and rollback plan. If a managed service changes records automatically, document that integration and the account responsible for it. This log turns an ambiguous alert into a quick comparison against an approved deployment or migration.

Cadence and checkpoints

A practical DNS security checklist combines automated alerts with scheduled human review. If your DNS provider, registrar, monitoring platform, or security tooling offers change notifications, enable them for record updates, nameserver changes, registrar-account activity, transfer attempts, and changes to recovery or authentication settings. Alerts should go to at least one channel that is not dependent on the affected domain’s email system.

Use this review schedule as a starting point:

  • After every deployment: Confirm only the intended A, AAAA, CNAME, TXT, or related records changed. Compare the public result after allowing for normal DNS propagation.
  • After a registrar, hosting, CDN, or email migration: Recheck nameservers, web records, mail records, verification records, DNSSEC settings, and registrar locks. Save a new approved baseline.
  • Monthly: Review the complete record set, inactive subdomains, registrar access, recovery details, and recent change notifications.
  • Quarterly: Remove documented obsolete records, test the incident-response contact list, and confirm that former employees, contractors, integrations, and temporary services no longer have unnecessary access.
  • Immediately: Investigate an unexpected nameserver change, unfamiliar mail destination, new subdomain, unexplained website redirect, certificate warning, or registrar notification you did not initiate.

For important domains, consider keeping the baseline in version control or another access-controlled location. Limit who can edit it, preserve previous versions, and avoid storing account passwords or private recovery codes in the same document.

How to interpret changes

First, separate a DNS discrepancy from a DNS incident. A change may be legitimate but not yet documented, or it may appear inconsistent because different resolvers are serving cached data during propagation. Check the record at the authoritative nameservers, compare responses from more than one independent resolver, and review the provider’s change history. Do not rely on a single browser result or a single lookup.

Prioritize changes by likely impact:

  1. Nameserver changes: Treat an unfamiliar NS value as urgent because it can give another DNS service control over many records.
  2. Mail changes: An unexpected MX or email-authentication change can affect message delivery and domain impersonation risk.
  3. Web destination changes: An unfamiliar A, AAAA, or CNAME value may redirect visitors or expose a subdomain.
  4. New verification or delegation records: Confirm that every TXT, CNAME, or other validation entry has a current business purpose.
  5. CAA or DNSSEC changes: Review these in the context of certificate management and provider migrations.

If a change is unexpected, do not edit records repeatedly while investigating. Preserve screenshots, exports, alert messages, timestamps, and relevant account logs. Contact the registrar and DNS provider through contact details obtained independently of a suspicious email or message. If the website or email may be compromised, use a separate trusted account and communication channel.

After securing the registrar account, change its password from a trusted device, review active sessions and delegated users, strengthen multifactor authentication, and verify recovery details. Ask the registrar whether transfer restrictions, account locks, or restoration procedures are available for the domain. Restore only known-good records, and coordinate with your hosting and email providers before making broad changes. Review website files, administrator accounts, email forwarding rules, and payment or customer-facing systems as separate parts of the investigation. For related account checks, see how to review email forwarding and recovery settings.

Once service is restored, document the cause, affected records, duration, actions taken, and remaining uncertainties. Update access permissions and the baseline. If the incident involved phishing or a stolen credential, review how to verify suspicious messages without using their contact information and consider the wider account-security checklist in the monthly online security checkup.

When to revisit

Review this process monthly for active websites and at least quarterly for lower-change domains. Revisit it immediately after a deployment, domain transfer, DNS-provider change, hosting migration, email-provider change, certificate-management change, or staff-access update. Update the article’s operational notes whenever your registrar or DNS provider changes its interface, notification options, lock controls, recovery process, or domain-transfer requirements.

Keep a short recurring checklist:

  • Compare public A, AAAA, CNAME, MX, TXT, NS, and CAA records with the approved baseline.
  • Confirm authoritative nameservers and DNSSEC status where applicable.
  • Review registrar lock, multifactor authentication, recovery contacts, delegates, and recent activity.
  • Check that every record has an owner and a current purpose.
  • Test that alerts reach a trusted channel outside the affected domain.
  • Record approved changes and investigate every unexplained difference.

DNS monitoring works best as routine maintenance rather than a one-time audit. A documented baseline, independent verification, protected registrar account, and clear response plan make it easier to tell a normal infrastructure change from a domain hijacking attempt before it becomes a larger website or email security problem.

Related Topics

#DNS#domain hijacking#registrar security#website monitoring#nameservers
P

Privacy Sentinel

Website & Domain Safety Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.