dead-drop vs VulDB

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d98.3%100%
P50 · ms722360
P95 · ms12991138
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limit100 req/window · 100 remaining · resets 1783513841Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

dead-drop vs VulDB: common questions

Which is more reliable, dead-drop or VulDB?

On our scheduled checks, VulDB leads on measured uptime — dead-drop at 99.02% 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, dead-drop or VulDB?

VulDB has the lower median latency in our checks — dead-drop responds in 722 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 dead-drop and VulDB need an API key?

dead-drop needs no key, while VulDB requires a free API key. If you want to start calling without signup, reach for dead-drop first.

Can I call dead-drop and VulDB from the browser?

Yes — both dead-drop and VulDB send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are dead-drop and VulDB free for commercial use?

dead-drop 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.