Skip to content
IPWhois.net Blacklist logo

Is IPWhois.net Blacklist API down?

Current status, daily uptime history and troubleshooting for the IPWhois.net Blacklist API (Anti-Malware).

No, IPWhois.net Blacklist is up

IPWhois.net Blacklist answered our last daily check (Oct 24, 2026, 12:25 UTC) in 1260 ms with HTTP 200.

Checking IPWhois.net Blacklist now…

Sending a request from our server.

IPWhois.net Blacklist API uptime history

30 days agoLatest check
Uptime
2 checks so far
Last check
Oct 24, 2026, 12:25 UTC
Response
1260 ms · HTTP 200
Last up
Now

We check IPWhois.net Blacklist's listed URL (https://ipwhois.net/blacklist/docs) once a day. History started when IPWhois.net Blacklist was first checked, so new entries show fewer than 30 days.

IPWhois.net Blacklist API not working for you?

  1. A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header.
  2. If calls fail only in the browser with a CORS error, IPWhois.net Blacklist may not allow cross-origin requests. Call it from your server instead.
  3. If it works from one network but not another, check firewalls, VPNs and regional blocks.
  4. Check the provider's documentation, status page or social accounts for planned maintenance or a changed endpoint.

Anti-Malware APIs up at their last check

  1. 1URLhaus logo

    URLhaus API

    Online · 1195 ms

    Bulk queries and Download Malware Samples.

    • No API key needed
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  2. 2ScanMalware logo

    ScanMalware API

    Online · 706 ms

    Scan URLs in a sandboxed browser and search past scans by domain, IP, ASN, JARM or favicon hash.

    • No API key needed
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  3. 3NoPhishy logo

    NoPhishy API

    Online · 1021 ms

    Check links to see if they're known phishing attempts.

    • Callable from the browser (CORS)
    • HTTPS
    apiKeyHTTPSCORS
  4. 4Scanii logo

    Scanii API

    Online · 1578 ms

    Simple REST API that can scan submitted documents/files for the presence of threats.

    • Callable from the browser (CORS)
    • HTTPS
    apiKeyHTTPSCORS
  5. 5

    AbuseIPDB API

    Online · 1055 ms

    IP/domain/URL reputation. A free anti-malware API by AbuseIPDB.

    • HTTPS
    apiKeyHTTPSCORS ?

Compare all IPWhois.net Blacklist alternatives · APIs down right now

IPWhois.net Blacklist API status FAQ

Is IPWhois.net Blacklist API down right now?

IPWhois.net Blacklist answered our last daily check (Oct 24, 2026, 12:25 UTC) in 1260 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether IPWhois.net Blacklist is responding at this moment.

How do you check whether IPWhois.net Blacklist API is up?

Once a day our checker requests IPWhois.net Blacklist's listed URL (https://ipwhois.net/blacklist/docs) and records whether it answers within 15 seconds. Answers like 401 (needs a key), 403 (blocks bots) or 429 (rate-limited) count as up, because the server responded. The listed URL is often the documentation page, so an API endpoint can occasionally fail while its docs stay up.

What can I use if IPWhois.net Blacklist API is down?

Free Anti-Malware APIs that were up at their last check include URLhaus, ScanMalware, NoPhishy. See the full list of IPWhois.net Blacklist alternatives for a comparison.

Why does IPWhois.net Blacklist API work for others but not for me?

A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header. If calls fail only in the browser with a CORS error, IPWhois.net Blacklist may not allow cross-origin requests. Call it from your server instead. If it works from one network but not another, check firewalls, VPNs and regional blocks.