Is Phisherman API down?
Current status, daily uptime history and troubleshooting for the Phisherman API (Anti-Malware).
Possibly: Phisherman's last check failed
Our latest daily check of Phisherman (Oct 24, 2026, 12:25 UTC) failed: its domain name doesn't resolve. One failure can be a blip; the live check below tells you whether it's still failing.
Checking Phisherman now…
Sending a request from our server.
Phisherman API uptime history
- Uptime
- 2 checks so far
- Last check
- Oct 24, 2026, 12:25 UTC
- Response
- Its domain name doesn't resolve
- Last up
- Not seen up yet
We check Phisherman's listed URL (https://phisherman.gg/) once a day. History started when Phisherman was first checked, so new entries show fewer than 30 days.
Phisherman API not working for you?
- Phisherman needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string.
- 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, Phisherman 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.
- 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
URLhaus API
Online · 1195 msBulk queries and Download Malware Samples.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 2
ScanMalware API
Online · 706 msScan 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
NoPhishy API
Online · 1021 msCheck links to see if they're known phishing attempts.
- Callable from the browser (CORS)
- HTTPS
apiKeyHTTPSCORS - 4
IPWhois.net Blacklist API
Online · 1260 msCommunity IP blacklist to check and report abusive IP addresses.
- No API key needed
- HTTPS
No authHTTPSCORS ? - 5
Scanii API
Online · 1578 msSimple REST API that can scan submitted documents/files for the presence of threats.
- Callable from the browser (CORS)
- HTTPS
apiKeyHTTPSCORS
Phisherman API status FAQ
Is Phisherman API down right now?
Our latest daily check of Phisherman (Oct 24, 2026, 12:25 UTC) failed: its domain name doesn't resolve. One failure can be a blip; the live check below tells you whether it's still failing. This page also runs a live check from our server when you open it, so you can see whether Phisherman is responding at this moment.
How do you check whether Phisherman API is up?
Once a day our checker requests Phisherman's listed URL (https://phisherman.gg/) 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 Phisherman API is down?
Free Anti-Malware APIs that were up at their last check include URLhaus, ScanMalware, NoPhishy. See the full list of Phisherman alternatives for a comparison.
Why does Phisherman API work for others but not for me?
Phisherman needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string. 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, Phisherman may not allow cross-origin requests. Call it from your server instead.