Changed Subdomain Detected

Changed Subdomain Detected: what it means, why it may matter, and how to remediate with external verification using ExposureGrid.

The problem

Changed Subdomain Detected: Asset inventory gaps make it hard to apply consistent security controls across hostnames you own or influence.

Why it matters

Shadow IT and stale DNS often precede misconfiguration or takeover-class issues.

How to check

Maintain authoritative inventory, reconcile DNS records, monitor new subdomains, assign owners.

How to fix

Decommission unused hosts, bring assets under change control, verify third-party ownership.

  1. Identify owners for the affected component (app, edge, DNS, or mail).
  2. Make a minimal change and validate in staging or a canary route.
  3. Deploy with monitoring and rollback readiness.
  4. Re-run ExposureGrid to confirm the external signal improved.

Run a scan to verify this fix on your domain

Use the same public scanner as the homepage — results honor your plan tier.

Scan your domain

What ExposureGrid checks

ExposureGrid helps discover and track externally visible hostnames over time on supported plans.

FAQ

Why does "Changed Subdomain Detected" appear in ExposureGrid?
Scanners observe externally visible signals. A finding means our rules matched - validate severity and applicability in your environment.
Could this be a false positive?
Yes, depending on context and coverage limits. Especially for heuristic, partial, or pattern-based checks, corroborate with manual review.
What should I do after changing configuration?
Re-run a scan to confirm the external signal changed, then enable monitoring where your plan supports it.

ExposureGrid continuously monitors these issues and alerts you before they become exploitable.

Run a private scan

Compare plans