IPWhois.net Blacklist
Anti-Malware
Community IP blacklist to check and report abusive IP addresses
Google Link/Domain Flagging
Verified 4 days ago: 100% uptime
API key
Required
HTTPS
Supported
Browser calls
No, needs a proxy
Status
Live · 100/100
Last checked 2026-09-18. Measured independently, not self-reported by the provider.
A starting template for Google Safe Browsing. Replace ENDPOINT with the path from the official documentation, which we link above rather than guess at.
# Requires an API key. Check the docs for whether it goes in a header or a query parameter.
curl -s "https://developers.google.com/ENDPOINT" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Accept: application/json"This API does not send CORS headers, so a browser will block a direct call from your front end. Call it from your server, or put a small proxy in front of it.
Aggregated from 2 public sources (public-api-lists, public-apis), then normalised and checked by us. If something here is wrong, tell us and we will correct it.
Anti-Malware
Community IP blacklist to check and report abusive IP addresses
Anti-Malware
Bulk queries and Download Malware Samples
Anti-Malware
Malware execution and analysis
Anti-Malware
Provide malware datasets and threat intelligence feeds
Anti-Malware
IP/domain/URL reputation
Anti-Malware
Multi-account and fraud detection. Sending emails without ending up in SPAM
Answered from what our own scheduled checks found, not from the provider's marketing.
Google Safe Browsing is listed in our free catalogue, but it requires an API key, so you will need to register before your first call. Providers frequently reserve higher limits and commercial use for paid plans.
Yes. Google Safe Browsing authenticates with an API key. Keep it server-side rather than in browser code, because anything in your frontend bundle is readable by anyone who opens developer tools.
Not directly. Google Safe Browsing did not return CORS headers when we checked, so the browser will block your page from reading the response even though the request itself succeeds. Call it from a server, or put a small proxy in front of it.
Yes, as of 2026-09-18. Our automated check reached Google Safe Browsing and recorded a 100% reliability score with a median response time of 628 ms. We re-check on a schedule, and this page updates with the result.
Yes. Google Safe Browsing serves over HTTPS, so you can call it from a secure page without triggering a mixed-content block.