Emailvalidation vs xfetch
Same instrument, two spec sheets — measured, not claimed.
Emailvalidation vs xfetch: common questions
Which is more reliable, Emailvalidation or xfetch?
On our scheduled checks, xfetch leads on measured uptime — Emailvalidation at —% versus xfetch 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 Emailvalidation and xfetch need an API key?
Both ask you to authenticate — Emailvalidation uses an API key and xfetch 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 Emailvalidation and xfetch from the browser?
Yes — both Emailvalidation and xfetch 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 Emailvalidation and xfetch free for commercial use?
Emailvalidation has unclear commercial terms, and xfetch 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.