EmailRep vs VulDB

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms277360
P95 · ms7511138
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

EmailRep vs VulDB: common questions

Which is more reliable, EmailRep or VulDB?

Both are neck-and-neck — EmailRep and VulDB each measure 100% 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, EmailRep or VulDB?

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

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

Can I call EmailRep and VulDB from the browser?

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

Are EmailRep and VulDB free for commercial use?

EmailRep 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.