Source boundaries stay visible
URL scans remain HTTPS-only and carry strict or lenient redirect policy through the scan path instead of hiding that choice.
Shipped product surface
Scan what the model may parse, not just what a user can read.
Veridicus Scan covers specific source types, extracts concrete hidden-channel signals, and calls out partial coverage when a scan is capped or boundary-limited. This is the practical scan surface you can use today.
Coverage map
The app covers source surfaces, hidden channels, and decision outputs.
The useful question is not “does it scan content?” but “which content, which hidden channels, and what comes back when the scan is done?”
Content surfaces
- HTTPS URL fetches with strict or lenient validation mode
- Imported PDF text plus PDF style and visibility signals
- Imported DOCX text plus DOCX hidden-style metadata
- Imported HTML content and parser-versus-visible text differentials
Hidden channels
- HTML comments, hidden DOM blocks, and parser-only content
- Hidden Unicode controls and suspicious control-style language
- PDF and DOCX metadata or style anomalies
- Redirect blocks and scan-boundary notes for URL scans
Decision outputs
- Risk score, risk band, and finding count
- Evidence-backed findings plus guidance
- Coverage notices when a scan is partial or capped
- JSON or PDF export with evidence redacted by default
Coverage discipline
Coverage stays explicit when the scan is bounded.
Partial results, redirect limits, and evidence-redaction defaults stay visible in the result so a user can judge what the scan did and did not prove.
Partial coverage is disclosed
Large responses or files that exceed the configured scan budget are marked as partial so a “clean” result does not overstate certainty.
Evidence stays usable after export
JSON and PDF output keep findings, guidance, and coverage notes together, with evidence snippets redacted by default.
Related pages
Read the adjacent product surfaces by source, trust model, or output.
Coverage sits in the middle of the product story. The surrounding pages explain why it matters, how the URL path behaves, and how the report communicates the result.
Why it matters
Start with the gap between visible content and parser-visible content before diving into the exact scan surface.
URL scanning
See how strict mode, lenient mode, redirect boundaries, and URL-specific coverage details work.
Reports and exports
See how the scan turns into a readable report with findings, guidance, and PDF or JSON output.
Next step
Take the coverage map into real scenarios.
See how these scan surfaces and outputs show up in assistant safety, document review, team workflows, and local MCP automation.