WhoisXML API Email Verification API vs Zenodo

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublished30 req/window · 29 remaining · resets 1783516620
In directory since2026-07-052026-07-05
operationalpartialdownno data

WhoisXML API Email Verification API vs Zenodo: common questions

Which is more reliable, WhoisXML API Email Verification API or Zenodo?

On our scheduled checks, Zenodo leads on measured uptime — WhoisXML API Email Verification API at —% versus Zenodo 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 WhoisXML API Email Verification API and Zenodo need an API key?

Zenodo needs no key, while WhoisXML API Email Verification API requires a free API key. If you want to start calling without signup, reach for Zenodo first.

Can I call WhoisXML API Email Verification API and Zenodo from the browser?

Yes — both WhoisXML API Email Verification API and Zenodo send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are WhoisXML API Email Verification API and Zenodo free for commercial use?

WhoisXML API Email Verification API has unclear commercial terms, and Zenodo 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.