Is Website Security Scanner API down?
Current status, daily uptime history and troubleshooting for the Website Security Scanner API (Security).
No, Website Security Scanner is up
Website Security Scanner answered our last daily check (Nov 15, 2026, 13:58 UTC) in 229 ms with HTTP 200.
Checking Website Security Scanner now…
Sending a request from our server.
Website Security Scanner API uptime history
- Uptime
- 100% of 10 checks
- Last check
- Nov 15, 2026, 13:58 UTC
- Response
- 229 ms · HTTP 200
- Last up
- Now
We check Website Security Scanner's listed URL (https://rapidapi.com/Hitler-HlDevZDwP/api/website-security-scanner-api) once a day. History started when Website Security Scanner was first checked, so new entries show fewer than 30 days.
Website Security Scanner API not working for you?
- Website Security Scanner 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, Website Security Scanner 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.
Security APIs up at their last check
- 1
DefenceLevel Index API
Online · 1080 msDaily cyber threat level (DEFCON 5 to 1) with open method, history in JSON/CSV and a badge.
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 2
IPLogs API
Online · 1003 msFree VPN, proxy, Tor and datacenter IP detection. 13 sources, active probing.
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 3
OSV API
Online · 455 msOpen source vulnerability database and distributed triage infrastructure.
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 4
Passwordinator API
Online · 406 msGenerate random passwords of varying complexities.
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 5
Presend API
Online · 529 msSecurity and developer utility API -- malware, vulnerability, and domain checks, no signup.
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS
Compare all Website Security Scanner alternatives · APIs down right now
Website Security Scanner API status FAQ
Is Website Security Scanner API down right now?
Website Security Scanner answered our last daily check (Nov 15, 2026, 13:58 UTC) in 229 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether Website Security Scanner is responding at this moment.
How do you check whether Website Security Scanner API is up?
Once a day our checker requests Website Security Scanner's listed URL (https://rapidapi.com/Hitler-HlDevZDwP/api/website-security-scanner-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.
How reliable is Website Security Scanner API?
Website Security Scanner answered 100% of our last 10 daily checks. Above 99% is excellent for a free API; below 95% means you should cache responses and keep a fallback ready.
What can I use if Website Security Scanner API is down?
Free Security APIs that were up at their last check include DefenceLevel Index, IPLogs, OSV. See the full list of Website Security Scanner alternatives for a comparison.
Why does Website Security Scanner API work for others but not for me?
Website Security Scanner 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, Website Security Scanner may not allow cross-origin requests. Call it from your server instead.