When to use this
Use this when your team has a list of links and needs a fast risk review.
How Verifence evaluates it
URL scanning is a reputation decision, not a visual inspection of the destination page. Verifence canonicalizes the link, checks its own reviewed bad-URL data, and queries Google Web Risk so known phishing and malware destinations can be stopped before someone clicks or publishes them.
Canonical matching
Equivalent forms of a URL are normalized so differences such as protocol, case, or a trailing slash do not bypass an existing bad-URL record.
Verifence threat data
Links are checked against URLs that have been reviewed and activated in the Verifence bad-URL database.
Google Web Risk
The scanner checks Google Web Risk and treats a confirmed reputation hit as a bad URL.
Batch processing
The web tool accepts pasted URLs or CSV and Excel files, queues the work in batches, and tracks safe and bad totals as processing completes.
How to do it
- 01 Prepare no more than 500 URLs as pasted lines or a CSV, XLS, or XLSX file. Invalid rows are skipped rather than scanned.
- 02 Submit the batch and keep the page open while queued batches update the processed, safe, and bad totals.
- 03 Review the per-URL status, threat count, and issue messages instead of acting only on the aggregate total.
- 04 Download the CSV to preserve the URL, status, threat count, and reasons for your incident or moderation workflow.
- 05 Quarantine bad destinations and manually investigate links whose context remains suspicious despite a clean reputation result.
How to act on the result
No configured reputation source identified the URL as malicious at scan time.
A Verifence blacklist or Google Web Risk hit identifies the URL as unsafe.
Use manual review when context remains suspicious even though current reputation sources return no hit.
Threat reputation changes. Rescan important or newly reported links before a later high-risk action.
Implementation notes
- Each URL scan costs 5 credits. The web batch tool accepts up to 500 valid URLs per submission.
- The API requires an HTTP or HTTPS URL, with a maximum length of 2,048 characters, and returns a simple safe/bad decision.
- A clean result means no current reputation hit was found; it is not a permanent guarantee about future destination content.