Skip to main content
HighContentOWASP A05:2021CWE-350

How to fix: Subdomain Takeover Fingerprint Detected

The response body matches a known 'unclaimed service' error page (GitHub Pages, Heroku, Fastly, Pantheon, Shopify, Squarespace, or Netlify), which typically means a DNS record still points at a service that no longer has a claim on this hostname.

Why it matters

An attacker who registers the same service and claims the unclaimed name can serve arbitrary content, steal cookies scoped to the parent domain, and phish users who trust the hostname.

Subdomain takeover happens when a DNS record (typically a CNAME) still points at a third-party service (GitHub Pages, Heroku, S3, Shopify, etc.) after the corresponding resource there was deleted or renamed. The hosting provider serves a distinctive 'not found' page until someone else claims that name on their platform, at which point they control the content served under your domain.

How to fix it

  1. 1Remove the DNS record if the third-party resource is no longer in use.
  2. 2Re-provision the resource on the third-party service under the same name if it is still needed.
  3. 3Audit all CNAME/ALIAS records pointing at third-party platforms on a recurring basis.

Code examples

Audit dangling CNAMEs

bash
# List CNAME records and check each target still resolves to a claimed resource
dig CNAME sub.example.com
curl -sI https://sub.example.com | head -5

References

Detected automatically by VulnRadar. The check id is subdomain-takeover-fingerprint, stable across every scan so you can filter or diff on it.

See every content check

Questions

How severe is Subdomain Takeover Fingerprint Detected?
VulnRadar rates this high severity in the content category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id subdomain-takeover-fingerprint, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Subdomain Takeover Fingerprint Detected map to?
It maps to CWE-350. In the OWASP Top 10 it falls under A05:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for subdomain takeover fingerprint detected

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

Subdomain Takeover Fingerprint Detected fix | VulnRadar