URLScan.io vs VulDB

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d97.1%100%
Uptime · 30d95.0%100%
P50 · ms1322360
P95 · ms49081138
AuthapiKeyapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree tier — key may be required
Rate limit30 req/window · 29 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

URLScan.io vs VulDB: common questions

Which is more reliable, URLScan.io or VulDB?

On our scheduled checks, VulDB leads on measured uptime — URLScan.io at 97.1% versus VulDB at 100% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, URLScan.io or VulDB?

VulDB has the lower median latency in our checks — URLScan.io responds in 1322 ms versus VulDB at 360 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do URLScan.io and VulDB need an API key?

Both ask you to authenticate — URLScan.io uses an API key and VulDB uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call URLScan.io and VulDB from the browser?

Only VulDB is browser-friendly — it returns CORS headers over HTTPS. URLScan.io needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are URLScan.io and VulDB free for commercial use?

URLScan.io has unclear commercial terms, and VulDB has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.