MEDIUM SEVERITYDNSCVSS 7.5Requires Account VerificationID: statuspage-io
Atlassian Statuspage Dangling DNS & Takeover Fingerprint
A status page was decommissioned but the custom domain CNAME record still resolves to Atlassian Statuspage edge.
DNS CNAME Delegation Rules
*.statuspage.io
CNAME points to statuspage.io. Returns 'Status page not found'.
404 Not Found
Authoritative Response Token
“Status page not found”
curl -sI http://subdomain.example.com | grep 'Status page not found'When SubdomainWatch scanner identifies this response on an unresolved CNAME target, an automated alert is triggered within 800ms.
Remediation Guide & Defensive Action Plan
Immediate Action Required: Delete the CNAME record in DNS or re-link your Statuspage organization.
Defensive Verification Checklist:
- Audit authoritative DNS zone records for any CNAME pointing to
*.statuspage.io. - Verify whether the target resource or bucket still exists under your organization's cloud tenant.
- If decommissioned, delete the DNS record immediately to close the public exposure window.
- Deploy a pre-merge IaC security gate (such as SubdomainWatch Takeover Guard) to intercept dangling records before pull requests merge.
Terraform Remediation Example
# Remove Atlassian Statuspage CNAME
ATTACK SURFACE DETECTION COMPARISON
Why Static DNS Scanners Miss Atlassian Statuspage Takeovers
Passive DNS repositories like SecurityTrails and heavy scanners like Detectify record domain records retrospectively or trigger alert fatigue. SubdomainWatch conducts active recursive CNAME testing with zero false positives.
Atlassian Statuspage Takeover FAQs
Adversaries can declare fake outages or service notices to damage brand reputation or spread disinformation.
FREE UNRESTRICTED SCANNER
Scan Your Domain for Atlassian Statuspage Orphans
Test any hostname live. Our diagnostic engine traverses CNAME hops and verifies authoritative provider tokens in seconds without requiring an account.