Urlbox API vs WhoisXML API Email Verification API

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

Uptime · 30d
Uptime · 90d0.0%0.0%
Uptime · 30d0.0%0.0%
P50 · ms
P95 · ms
AuthapiKeyapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Urlbox API vs WhoisXML API Email Verification API: common questions

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

Both are neck-and-neck — Urlbox API and WhoisXML API Email Verification API each measure 0.0% 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.

Do Urlbox API and WhoisXML API Email Verification API need an API key?

Both ask you to authenticate — Urlbox API uses an API key and WhoisXML API Email Verification API uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

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

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

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

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