Monitoring

    DNS CNAME change check

    Detects when a CNAME target changes — the earliest signal of a broken CDN swap, subdomain takeover risk, or accidental alias edit.

    Part of DNS monitoring — the full answer, the facts and the alternatives in one place.

    Updated 2026-07-10
    1 min read
    dns
    cname
    takeover

    Quick answer#

    Lemwatch tracks the CNAME target for every subdomain you monitor and alerts on any change. If the new target resolves to nothing, we flag a potential subdomain-takeover risk.

    What it checks#

  1. CNAME chains up to 8 hops
  2. Final resolved host and its A records
  3. Whether the target returns NXDOMAIN (takeover signal)
  4. Cross-region resolution to filter DNS propagation noise
  5. Where to find it in Lemwatch#

    Site details → Health → DNS tab. Takeover-risk changes also raise an incident with severity: high.

    How to respond#

  6. Compare old vs new target in the DNS tab.
  7. If new target is NXDOMAIN, remove the CNAME immediately.
  8. Confirm the intended vendor now owns the target.
  9. Re-issue TLS certs if the new host uses a different SNI.
  10. Acknowledge once verified.
  11. FAQ#

    What is a subdomain takeover?#

    An attacker claims an abandoned CNAME target (e.g. an old Heroku app) and serves content under your domain.

    Does this cover ALIAS/ANAME too?#

    Yes — resolved through the same path.

  12. DNS A record change check
  13. DNS diagnostics
  14. Bypassing bot protection
  15. Was this article helpful?