Anti-Malware · head-to-head

AbuseIPDB vs Google Safe Browsing

AbuseIPDB

AbuseIPDB is a crowdsourced IP, domain, and URL reputation database where network operators report malicious activity like brute-force attempts, spam, and port scans. A live GET against the real gateway, api.abuseipdb.com/api/v2/check, returned a 401 with an invalid key rather than a CORS-enabled response, reconfirming API-key auth over HTTPS and resolving cors to no. A free Individual tier allows 1,000 checks a day forever with no card required, while paid Basic/Premium/Enterprise plans raise the daily ceiling for high-volume users.

Google Safe Browsing

Google Safe Browsing lets clients check URLs against Google's continuously updated lists of malware, phishing, and unwanted-software sites via the v4 threatMatches:find endpoint, the same data that powers warnings in Chrome and Search. A live POST with a syntactically valid but bogus key returned a 400 "API key not valid" error from safebrowsing.googleapis.com, reconfirming API-key auth and HTTPS, and both that call and its OPTIONS preflight echoed the request Origin in Access-Control-Allow-Origin. The API is free for any Google Cloud project under its published quota.

AbuseIPDBGoogle Safe Browsing
AuthenticationAPI KeyAPI Key
Pricingfreemiumfree
FormatsJSONJSON
CORSnoyes
HTTPSYesYes

Google Safe Browsing supports CORS, while AbuseIPDB doesn't — pick Google Safe Browsing for direct browser calls.

More comparisons