CloudSpex methodology
How CloudSpex evaluates domain health
Public-facing checks
CloudSpex evaluates publicly reachable DNS, HTTPS, HTTP, email-authentication, redirect, certificate, and related domain signals. It does not change a domain's DNS, website, certificate, email, or account settings.
Findings and scores
Findings classify observed conditions so teams can prioritize review. Scores summarize active signals; they do not replace technical validation or create a guarantee about a domain's security, availability, or deliverability.
Root cause and blocked checks
Where evidence supports it, CloudSpex distinguishes an observed issue from a dependency-blocked or incomplete check. A blocked result means the service could not establish the signal safely or reliably enough to classify it as healthy.
Review before remediation
Infrastructure settings can have provider-specific consequences. Confirm ownership, the responsible provider, and change impact before applying a recommendation.