osintverse-community/safebrowsing
Checks a URL against Google Safe Browsing's lists of malware, phishing and unwanted software sites
Key required · Docker
7 tools. 7 run with ot in a sandbox on Windows, macOS and Linux. Compare them side by side ↓
The safest way to look at a suspicious link is through other people's records. Blocklists such as Google Safe Browsing and PhishTank say whether it is a known phishing or malware page, URLhaus whether it served malware, and VirusTotal and urlscan what dozens of engines and earlier scans made of it, all without your browser loading the page.
Windows, macOS and Linux, with Docker or Podman. Each tool runs in a read-only container that can reach only the sites it declares, and every result comes back in the same JSON shape.
Checks a URL against Google Safe Browsing's lists of malware, phishing and unwanted software sites
Checks a URL against CIRCL's copy of the PhishTank feed of verified phishing pages
Looks up a URL, domain, IP address or file hash in abuse.ch URLhaus: malware URLs, their status, tags and payloads
Looks up an IP, domain, URL or file hash in VirusTotal: engine verdicts, reputation, tags, owner, DNS records
Searches urlscan.io's existing scans of a domain, IP or URL: each page's title, server, IP, network and country
Looks up an IP, domain or URL in Pulsedive: risk level and factors, linked threats and feeds, ports, technologies
Looks up an IP, domain, URL or file hash in AlienVault OTX: the threat reports that mention it, malware, tags
ot install osintverse-community/safebrowsing osintverse-community/phishtank-lookup osintverse-community/urlhaus osintverse-community/virustotal osintverse-community/urlscan-searchInstalls the first 5 in one go; ot auto url:… then runs every installed tool that takes an URL and saves the results. No ot yet? Install it in one line.
| osintverse-community/ | document, domain, ip, location… | None | Online, passive | No | Docker | No reports yet | fewer than 10 |
| osintverse-community/ | url | None | Online, passive | No | Python | No reports yet | fewer than 10 |
| osintverse-community/ | domain, ip, location, organization… | None | Online, passive | No | Docker | No reports yet | fewer than 10 |
| osintverse-community/ | url | Required | Online, passive | No | Docker | No reports yet | fewer than 10 |
| osintverse-community/ | document, domain, ip, url | Required | Online, passive | No | Docker | No reports yet | fewer than 10 |
| osintverse-community/ | domain, ip, subdomain, url | None | Online, passive | No | Docker | No reports yet | fewer than 10 |
| osintverse-community/ | dns record, document, domain, ip… | Required | Online, passive | No | Docker | No reports yet | fewer than 10 |
Facts from each tool's manifest and what people report about whether it works. "Reaches" says whether a run stays offline, reads public sources, sends requests about the target, or may notify them.
Every registry tool here runs on your machine in a sandbox, and ot auto url:… runs all the installed ones on one value.
No. New phishing pages often live for hours and aren't on any list yet. Treat a clean result as unknown, and look at the domain's age and certificate on the domain page.
Looking up existing records doesn't: the tools ask the services, not the site. Submitting a new scan to a public service can, because its scanner visits the page and the result may be public; these tools only read what is already there.
No. ot runs each tool on your own machine in a read-only container that can only reach the sites the tool declares, and results stay in your results folder. The registry only counts installs.
Archived copiesEmails and contactsLinks and endpointsAll URL tools