A public DNS result is not a full assessment
The checker on this page observes public DNS records. It cannot inspect private accounts, website files, HTTP responses or backup contents, and it cannot certify security. The paid health check adds an agreed inspection using authorized access, with evidence and a prioritized report. Choose a security audit when the primary question is website exposure.
Read a report as evidence
The sample score is illustrative. Public DNS observations, authenticated inspection and executed recovery tests support different conclusions. Identify access and methods before interpreting any result.
- List systems and available access.
- Record time and evidence.
- Prioritize by exposure and business impact.
- Assign owners and retest criteria.
Observed, reported and untested findings
The public checker queries DNS; it does not scan application code, access mailboxes or inspect backup contents. A useful health check explains what remains unknown and connects priorities to separately scoped work rather than implying assurance from a synthetic score.
| State | Meaning | Next step |
|---|---|---|
| Observed issue | Specific supporting evidence | Agree correction |
| Owner report | Not independently checked | Request evidence |
| Not tested | Method/access unavailable | Document limitation |
Example: a backup test still pending
A sample report marks backup verification pending. A green job icon does not establish recovery; an isolated restore can be proposed separately. This is an illustrative scenario, not a customer case or a promised result.