DNS A/AAAA Resolution
Pass C01 · A/AAAA resolutionThe reserved domain resolves to public anycast addresses over IPv4 and IPv6.
Sample report
This is the recorded SMB Scanner Lite assessment of example.com from 28 October 2026. Nothing is redacted for marketing and nothing is added: the score, findings, evidence, metadata and consent receipt are exactly what the run produced.
example.com demonstrates strong DNSSEC, SPF (-all) and DMARC enforcement, with informational web security header gaps typical of a minimal RFC reference site.
Eight controls completed and none returned an inconclusive answer, so the score covers every check that ran. DNS, email authentication and transport are strong. The two warnings are informational browser-header gaps typical of a minimal reference site.
A grade B is not a statement that the domain is secure. It means the controls that were measured met their expectations, subject to the limitations of external observation. No application, identity system or internal network was examined.
External and read-only. The assessment queried public DNS records, completed TLS handshakes, read HTTP response headers, and made no authentication attempt of any kind.
Eight findings, ordered as recorded. Each carries a status, the control it maps to and the observation behind it.
The reserved domain resolves to public anycast addresses over IPv4 and IPv6.
The zone is signed and the chain of trust validates against the parent.
SPF is published and set to a strict no-mail policy.
Unauthorised senders are rejected at the receiving mail server.
The domain publishes a null MX, signalling that it does not accept mail.
TLS 1.3 is offered with a certificate that covers the domain.
HSTS is not enforced on the reference landing page.
A content security policy is not set on the static reference response.
The literal observations recorded during the run. Copy any line and re-run the equivalent query from outside your own network; if the answer differs, the finding is stale or specific to the assessment vantage point.
| Grade | Score | Band | Interpretation |
|---|---|---|---|
| A | 90-100 | Strong | Every control that completed meets its published expectation, or is one minor gap away. |
| B | 80-89 | Strong | Well configured overall. The gaps are informational or low-impact hardening items. |
| C | 65-79 | Fair | Meaningful gaps in at least one category. Worth a planned fix, not an emergency. |
| D | 50-64 | Needs work | Several controls are missing or weak across more than one category. |
| F | 0-49 | Urgent | Core controls are absent. Start with the highest-severity findings and work down. |
Recommendations are limited to the findings in this run. They are configuration changes with a published basis, not a remediation project plan.
Add Strict-Transport-Security: max-age=31536000; includeSubDomains.
Publish a restrictive Content-Security-Policy (default-src 'self'; object-src 'none').
A failed control is not a confirmed vulnerability. It means a published expectation was not met. Confirm the observation yourself before treating any finding as a defect, and prioritise by the exposure it creates rather than by the colour of a dot.
Before any run, the operator accepts the privacy policy and signs a receipt that is hash-chained to the previous one. The receipt is embedded in the report so the authorisation behind the result travels with it. It is stored on the machine that ran the assessment, not on this website.
The same recorded assessment in four formats. The data is sanitised: it contains no internal hostnames, no operator identity beyond the demo label, and no private infrastructure detail.
Install the public sandbox and run the same reserved domain on your own machine. The documented commands and expected output are on the documentation page.
Installation guideWeights, status credit and grade bands are documented. The score is a weighted summary of what completed — nothing else.
Scoring methodologyWhat an external assessment cannot establish is written down, because a credible tool states the boundary of its own evidence.
Assessment limitationsRequest an assessment and the same structure is produced for your infrastructure — after scope and written authorisation are agreed.