CVEDB vs SniffCat

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

Uptime · 30d
Uptime · 90d99.02%83.3%
Uptime · 30d98.3%83.3%
P50 · ms217290
P95 · ms801598
AuthnoneapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverified
Free tierFree — limits not published
Rate limitUnpublishedRetry-After: 24s
In directory since2026-07-052026-08-19
operationalpartialdownno data

CVEDB vs SniffCat: common questions

Which is more reliable, CVEDB or SniffCat?

On our scheduled checks, CVEDB leads on measured uptime — CVEDB at 99.02% versus SniffCat at 83.3% 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, CVEDB or SniffCat?

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

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

Can I call CVEDB and SniffCat from the browser?

Neither sends browser-friendly CORS headers reliably, so call CVEDB and SniffCat 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 SniffCat free for commercial use?

CVEDB has unclear commercial terms, and SniffCat allows commercial use on its free tier. 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.