Fictional example — not a real scan
All website names, scores, findings and evidence below are invented to explain the report. Opening this page scans no website, sends no test submission and reads no mailbox.
Illustrative owner-authorized check · one contact form · six example findings
example.invalid
Contact form · /contact · #contact-form
Exposed — illustrative result
65 / 100
Illustrative risk score
In this fictional case an active test accepts an invalid CAPTCHA token. That counter-evidence outweighs the visible widget and raises the overall risk.
Six illustrated checks: four positive findings, one issue and one unclear result. These are example values, not measurements.
What each kind of proof means
Publicly visible
The free check reads public pages and visible protection signals. It sends no form submissions and cannot prove server-side enforcement.
Actively tested
After ownership verification, enabled active tests may send clearly marked test submissions to suitable forms. A result applies to the test actually performed.
Delivery confirmed
A matching test message in your configured control mailbox confirms receipt of that test copy. It does not confirm the recipient’s inbox or a CRM entry.
Findings and evidence
CAPTCHA widget
Positive findingPublicly visible- Illustrative evidence
- A CAPTCHA widget and its provider script are visible on the form page.
- Recommended next step
- Keep the widget, then verify that the server rejects missing or invalid tokens.
Honeypot field
Positive findingPublicly visible- Illustrative evidence
- A hidden trap field is visible in the example form markup.
- Recommended next step
- Check server-side handling; a hidden field by itself does not prove that bots are rejected.
Token validation
UnclearPublicly visible- Illustrative evidence
- A token field is visible, but this example contains no server-side validation result for it.
- Recommended next step
- Verify server-side validation separately; keep this finding unclear until there is evidence.
CAPTCHA enforcement
Issue foundActively tested- Illustrative evidence
- The fictional endpoint accepts a marked request containing an invalid CAPTCHA token.
- Recommended next step
- Validate tokens on the server and reject invalid or missing tokens before sending mail. Run an authorized re-check afterwards.
Repeated submissions
Positive findingActively tested- Illustrative evidence
- In this example the endpoint returns HTTP 429 after several marked test requests.
- Recommended next step
- Keep rate limits enabled and monitor whether future authorized tests still encounter them.
Control mailbox
Positive findingDelivery confirmed- Illustrative evidence
- A fictional test copy with the matching test identifier is present in the configured control mailbox.
- Recommended next step
- Keep the control mailbox connected. Confirm recipient inbox or CRM delivery separately if you need that proof.
From a finding to a verified repair
Fix the failing check, run a new authorized test and compare its evidence. A visible widget, a successful browser path and a received test copy each prove a different part of the chain.
Check your own websiteNo live report, personal data, mailbox credentials or customer records are used in this example.