Find out what it exposes, what matters, and what to ask your team to improve.
example-bakery.com
Example reading
63
Observed posture index
Needs improvement
Areas evaluated 5/5
Observed posture index
Needs improvement
5 areas evaluated. The weakest is HTTPS and TLS, at 38 out of 100.
An outdated TLS version is still enabled
What was observed
protocol: TLS 1.0, TLS 1.1
HTTPS and TLS · An outdated TLS version is still enabled
What to ask for
Ask them to accept TLS 1.2 and TLS 1.3 only, and to remove TLS 1.0 and 1.1.
Five areas, each a different kind of signal your site already publishes to anyone who asks. Choose one to see what is checked and what a finding says.
The protocol versions your server still accepts, the strength of its cipher suites, and whether the certificate chain a browser has to trust is complete and current.
What the example found
What to ask for
Example data. The wording is the same wording a real report uses.See the full example report
Every finding arrives in three parts. This is the real catalog wording for the missing DMARC record in the example above.
No DMARC record was found
_dmarc TXTabsentRFC 7489
No TXT record beginning with v=DMARC1 was published at _dmarc under the domain.
One page. The index with the coverage it was computed over, the findings that warrant action first, and every area with its own reading.
The findings that warrant action, in order. Everything else is below.
What matters
Up to three actions, worst first, each one linked to the finding it came from and written as a sentence you can forward.
What was checked
Five areas, each with its own reading on the same scale as the index. An area that could not be evaluated says so instead of scoring zero.
What the number is
A weighted index over the areas that were evaluated, with its coverage next to it. Not a percentage, and not a grade.
The same reading, read three different ways. What you do with it depends on who you are.
Find out what is worth looking at, even without a security team. The result names what was seen, what it means, and the sentence to send to whoever built the site.
Check my siteRead the public signals of your site and of the domain your customers see in their inbox. Whether someone can send an invoice in your name is a DNS record, and it is one of the five areas.
See what is checkedBring a first reading to the conversation, then open the detail to act on it. Every finding carries its evidence, its severity and its confidence separately.
Open an example reportA first look at your website that you can understand and turn into actions.
Every finding arrives in three parts: what was observed, what it means in plain language, and what to ask your technical team for. The middle part is the one that lets you decide whether to act without already knowing the subject.
A finding, and the one that comes first
The boundary is the product. These are not features waiting to be built; they are things SiteGuardia will not do to a site it has no authorisation for.
SiteGuardia Free performs automated, non-destructive checks and cannot prove that a website is secure or free of vulnerabilities. It does not replace a professional penetration test.
If a check finds something genuinely serious on a domain nobody has proven they own, the technical evidence is classified and dropped before it is written down. The database never holds it, the API never returns it, and there is nothing in the page for a browser to reveal.
What people ask before they type a domain in. If yours is not here, the methodology page goes further.