URL and file checks
Inspect public web destinations and supported files up to the current 10 MB inspection limit.
Threat Protection
Review a destination before you put your name behind it.
Inspect supported destinations and files with results that explain the check, the evidence found, and any incomplete assessment.
Inspect a URL or filePhishing intelligence
Compare URLs with locally refreshed Phishing.Database and PhishDestroy data.
A reviewable record
Download a report and request administrator review with a clear reason.
Understand the inspection you requested
Available controls distinguish database checks from content inspections. Reports identify matching sources and relevant destination or file details.
A result with no known threat found is different from an incomplete check and is not a guarantee of safety.
Keep evidence connected to the decision
Inspection history and downloadable reports provide context for the workspace. File reports can include malware signature findings and a SHA-256 fingerprint.
Submitted inspection file contents are discarded after the check rather than becoming an uploaded workspace asset.
Ask for a review with a useful reason
A review request should explain why the recorded inspection needs another look. Keep that request connected to its inspection context.
Review decisions are shown in the workspace and do not automatically release blocked content. Public link and file controls keep their own enforcement rules.
Common questions
What teams ask before they start.
Does a clear inspection guarantee safety?
No. It means no known threat was found by that assessment; incomplete checks and future changes must be considered separately.
Does requesting review unblock content?
No. A review request and its decision do not automatically release a blocked link or file.
Start with a real workflow