Catalog/VULNERABILITY/subdomain-takeover
SCAN-ID: SUBDOMAIN-TAKEOVERREVISION 2026.4
VULNERABILITYCVSS 8.8 (HIGH)

Subdomain Takeover & Dangling DNS Scanner

Detect abandoned CNAME records pointing to decommissioned third-party cloud providers (AWS, S3, Vercel, GitHub).

Technical Scope & Verification Behavior

Scans DNS records against known fingerprint signatures of 40+ cloud hosting services to spot claimable unclaimed tenant subdomains.

Automated Inspection Checks (18)
Passive URL parameter fuzzing
Non-destructive boundary tests
Header & cookie flag assertions
Differential latency timing

Proof of Concept (PoC) Vector

Canonical test payload dispatched during security surface audits.

docs.example.com CNAME -> unclaimed-bucket.s3.amazonaws.com

Probe Execution Simulator

Watch the probe engine test this signature in an isolated sandbox.

probe-runner (isolated ephemeral container)
Click 'Simulate Check' to watch the headless audit engine test this vector.

Remediation Patch

DNS Record Cleanup

patch.diff (dns)
--- a/handler.dns (Vulnerable)
docs.example.com. 300 IN CNAME old-service.herokuapp.com.
+++ b/handler.dns (Remediated)
; Delete dangling CNAME or re-point to active service

Audit your DNS zone files and immediately delete CNAME records whose backing cloud resource has been decommissioned.

AI Agent Prompt (Cursor · Claude · Copilot)

Copy and paste into your editor to refactor this issue automatically.

"Log into your DNS provider and delete the dangling CNAME record for this subdomain to prevent unauthorized takeover."

Run Isolated Check

Test your public domain specifically for Subdomain Takeover & Dangling DNS Scanner.

100% passive • No server load

Specification Details

CVSS Score
8.8 / 10.0
Severity Level
HIGH
Category
VULNERABILITY
Test Vectors
18 automated
Execution SLA
< 2.5 seconds
False Positive Defense
Strict assertion
Related Standards
#DNS#Takeover#CNAME#Cloud

Run continuous monitoring for Subdomain Takeover & Dangling DNS Scanner

Audit your site across all 41 vectors automatically on every deploy.

Back to Catalog