Start with a direct HTTPS URL
The app keeps URL input explicit so a user knows they are asking the scanner to fetch a remote page rather than inspect a local file.
HTTPS source path
HTTPS URL scanning with strict redirect boundaries.
Veridicus Scan treats URL scanning as a separate path from imported files. The app accepts HTTPS input, applies the selected redirect policy, and carries the resulting boundary and coverage information into the final report. Premium MCP mode can call the same URL scan path through Scan URL while the app is active.
Workflow
The URL path stays explicit from input through report.
A strong URL scan flow keeps the network behavior legible. Users should know they are scanning a remote source, what redirect policy applies, and how that boundary is reflected in the result they read later.
Apply strict or lenient redirect policy
Strict mode blocks at the redirect boundary when the destination changes. Lenient mode exists for broader compatibility with safe HTTPS redirects.
Carry the outcome into the report
The report reflects what the scan path allowed, what was blocked, and whether the result is complete or partial.
Redirect policy
Strict mode is for workflows where the boundary matters.
When a redirected destination would change the trust decision, the scanner needs to stop at that boundary. Lenient mode is still useful for normal web compatibility, but strict mode exists for the cases where the original URL is part of the risk question.
Strict mode
- Used when redirect boundaries should not silently change the scan target
- Stops at the redirect boundary instead of continuing into a changed destination
- Helps preserve the original trust question
Lenient mode
- Used when broader compatibility matters more than a hard redirect boundary
- Follows safe HTTPS redirects to keep scanning practical
- Useful for normal website review flows
Report output
- Boundary behavior remains visible in the result
- Coverage notes help prevent overconfident interpretation
- Report and export details live here
Use it when
URL scanning matters most when a page will become prompt context.
The URL path is especially useful when content is about to be pasted into an assistant, imported into a knowledge system, or reviewed as a suspicious public page with hidden parser-visible content.
Check a page before it becomes prompt context
Scan web content before it is copied into a model so hidden channels or redirects do not alter the prompt silently.
Review help pages, guides, and public sites
Use the URL path to inspect pages that look ordinary to a person but may contain parser-visible or metadata-level instructions.
Keep redirect behavior inside the decision
When the redirected destination would change whether the scan is trustworthy, strict mode keeps that boundary explicit.
Next step
Take the URL decision into trust policy, MCP, or the final report.
Move from redirect handling into local trust boundaries, exported evidence, or the agent workflow that depends on the scan.