CVEDB vs URLScan.io

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitUnpublished30 req/window · 29 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

CVEDB vs URLScan.io: common questions

Which is more reliable, CVEDB or URLScan.io?

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

Do CVEDB and URLScan.io need an API key?

CVEDB needs no key, while URLScan.io requires a free API key. If you want to start calling without signup, reach for CVEDB first.

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

Neither sends browser-friendly CORS headers reliably, so call CVEDB and URLScan.io from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are CVEDB and URLScan.io free for commercial use?

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