Subdomain Takeover Checker
Trace a hostname's CNAME chain for dangling DNS and selected service patterns. Free, DNS-based checks with manual verification guidance.
Quick answer
Check an authorized hostname for possible subdomain takeover signals using its public CNAME chain. The checker queries Google Public DNS and flags nonexistent CNAME targets or selected community service patterns. It never requests the target website. A match is a lead for manual verification, not proof that a subdomain is claimable.
What this check covers
An observed CNAME target returning NXDOMAIN is flagged as a possible dangling record. Separately, targets are compared with this small table from can-i-take-over-xyz, checked 2026-11-16. Every selected entry was marked Vulnerable with a fingerprint. Community entries can be incomplete or become outdated.
AWS Elastic Beanstalk
elasticbeanstalk.com
Reference fingerprint: NXDOMAIN
Microsoft Azure
azurewebsites.net, cloudapp.net, cloudapp.azure.com, azure-api.net, azurecontainer.io
Reference fingerprint: NXDOMAIN
Discourse
trydiscourse.com
Reference fingerprint: NXDOMAIN
AWS S3
s3.amazonaws.com
Reference fingerprint: The specified bucket does not exist (HTTP content not checked)
Bitbucket
bitbucket.io
Reference fingerprint: Repository not found (HTTP content not checked)
Surge.sh
na-west1.surge.sh
Reference fingerprint: project not found (HTTP content not checked)
Uses Google's DNS-over-HTTPS JSON API. Stops after eight CNAME hops, detects loops, and treats DNS errors as incomplete. It does not enumerate subdomains or test whether resources can be registered. No target HTTP requests are made.
Frequently asked questions
What does a dangling CNAME mean?
A CNAME aliases one DNS name to another. If the target returns NXDOMAIN, the alias may point to a deleted or nonexistent resource. Whether someone else can claim that resource depends on the provider and ownership protections, so NXDOMAIN alone does not prove takeover.
Does this checker visit my website?
No. The server queries only the fixed Google Public DNS JSON endpoint with the hostname you submit and its CNAME targets. It does not fetch HTTP content from your hostname or any target. Protego and Google receive the queried hostnames; do not submit private internal names.
Why does a service match require manual verification?
The curated service table comes from entries marked Vulnerable with a fingerprint in the can-i-take-over-xyz community project, checked on November 16, 2026. An HTTP error fingerprint is not checked here. Even NXDOMAIN can reflect configuration mistakes or provider protections, rather than a claimable resource.
Can a clean result prove my domain is safe?
No. This is a DNS-only check of one hostname and at most eight CNAME hops. It does not enumerate subdomains, inspect HTTP fingerprints, test resource registration, or cover NS, MX, ALIAS and other takeover paths. Timeouts, DNS failures, loops and long chains are incomplete assessments.
How should I investigate and fix a warning?
Check only domains you own or are authorized to assess. Confirm the intended resource and ownership in your provider account. Remove an unused CNAME or restore its authorized resource, then recheck DNS after caches expire. Do not claim another party’s resource to test a warning. Use DNS Lookup and the SSL Checker CT logs tab to investigate additional hostnames.