shipapis
StarSubmit an APISubmit API

CVEDB vs dead-drop

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

APICVEDBHEALTHY98dead-dropHEALTHY89
Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d98.3%98.3%
P50 · ms217722
P95 · ms8011299
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished100 req/window · 100 remaining · resets 1783513841
In directory since2026-07-052026-07-05
operationalpartialdownno data

CVEDB vs dead-drop: common questions

Which is more reliable, CVEDB or dead-drop?

Both are neck-and-neck — CVEDB and dead-drop each measure 99.02% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, CVEDB or dead-drop?

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

Neither needs a paid key — CVEDB is callable with no signup, and dead-drop is callable with no signup. Both are quick to prototype with; rate limits still apply.

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

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

Are CVEDB and dead-drop free for commercial use?

CVEDB has unclear commercial terms, and dead-drop 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.