URL and file threat inspection: reading evidence clearly

Understand supported URL and file checks, phishing intelligence, inspection reports, incomplete results, and reasoned administrator review requests.

An inspection needs an identifiable scope

A threat inspection is useful when it explains what was checked and which evidence informed the result. A public URL check, a phishing-database lookup, and an uploaded-file inspection are related activities, but they do not establish exactly the same facts.

Gods.ly distinguishes the available inspection controls and records relevant context in its reports. Supported file inspection currently accepts files within a ten-megabyte limit. Submitted inspection file contents are discarded after the check rather than becoming a published workspace asset.

Known intelligence is evidence with a time context

URL comparisons can use locally refreshed Phishing.Database and PhishDestroy intelligence. A match can identify a known reported threat in those sources. A result without a known match does not prove that a destination has never been harmful or cannot change later.

Read the recorded source and check context instead of turning a database result into an absolute promise. A destination can change after inspection, and a newly created threat may not yet appear in a known dataset.

File results deserve the same precision

Available file reports can include malware-signature findings and a SHA-256 fingerprint. A fingerprint identifies the inspected content so that a team can distinguish it from a different file with the same visible name.

An incomplete check is different from a completed check that found no known threat. Preserve that distinction when reviewing an asset or explaining a result to another team member. Downloadable reports help keep the evidence connected to the decision.

A review request explains why another look is needed

An authorised user can request administrator review with a reason attached to the inspection context. A useful reason points to the evidence or circumstances that need reassessment rather than asking for a decision without explanation.

The review request does not automatically unblock a link or file. Enforcement controls keep their own rules. Use the result, inspection history, and current public destination together when making the next workspace decision.

Explore URL and file threat inspection · Explore all Gods.ly products