shipapis
StarSubmit an APISubmit API

MailCheck.ai vs xfetch

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

APIMailCheck.aiNEW—xfetchNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limit5 req/window · 4 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

MailCheck.ai vs xfetch: common questions

Which is more reliable, MailCheck.ai or xfetch?

On our scheduled checks, xfetch leads on measured uptime — MailCheck.ai 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 MailCheck.ai and xfetch need an API key?

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

Can I call MailCheck.ai and xfetch from the browser?

Yes — both MailCheck.ai 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 MailCheck.ai and xfetch free for commercial use?

MailCheck.ai 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.