shipapis
StarSubmit an APISubmit API

CVEDB vs dead-drop

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

APICVEDBUNMONITORED—dead-dropNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
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?

Only dead-drop is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

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.