Is URLScan.io API down?
Current status, daily uptime history and troubleshooting for the URLScan.io API (Anti-Malware).
No, URLScan.io is up
URLScan.io answered our last daily check (Oct 24, 2026, 12:25 UTC) in 1699 ms with HTTP 200.
Checking URLScan.io now…
Sending a request from our server.
URLScan.io API uptime history
- Uptime
- 2 checks so far
- Last check
- Oct 24, 2026, 12:25 UTC
- Response
- 1699 ms · HTTP 200
- Last up
- Now
We check URLScan.io's listed URL (https://urlscan.io/about-api/) once a day. History started when URLScan.io was first checked, so new entries show fewer than 30 days.
URLScan.io API not working for you?
- URLScan.io 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, URLScan.io 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
URLScan.io API status FAQ
Is URLScan.io API down right now?
URLScan.io answered our last daily check (Oct 24, 2026, 12:25 UTC) in 1699 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether URLScan.io is responding at this moment.
How do you check whether URLScan.io API is up?
Once a day our checker requests URLScan.io's listed URL (https://urlscan.io/about-api/) 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 URLScan.io API is down?
Free Anti-Malware APIs that were up at their last check include URLhaus, ScanMalware, NoPhishy. See the full list of URLScan.io alternatives for a comparison.
Why does URLScan.io API work for others but not for me?
URLScan.io 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, URLScan.io may not allow cross-origin requests. Call it from your server instead.