HIGH SEVERITYHOSTINGID: netlify

Netlify Dangling DNS Takeover Fingerprint

A custom domain points to Netlify, but no site claims the domain. An attacker can assign the domain to their Netlify project.

Target CNAME Pattern

*.netlify.app

Expected HTTP Status

404 Not Found

Vulnerable Body Signature String

“Not Found - Request ID”

When SubdomainWatch scanner receives HTTP responses matching this token on a dangling CNAME, it raises a critical alert immediately.

Remediation Guide & Mitigation

Action Required: Remove the Netlify CNAME or re-assign the custom domain in your Netlify site settings.

Audit authoritative DNS zone records for any CNAME records pointing to *.netlify.app.
Verify whether the corresponding target resource is still active in your cloud tenant.
If the service was deprecated, delete the DNS record immediately to prevent hijackers from claiming the endpoint.
Add automated continuous monitoring to alert before third parties can register matching resource names.

SubdomainWatch continuously monitors your DNS zones for orphaned Netlify pointers, expired certificates, and dangling records 24/7.