mail.tm vs MailCheck.ai

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

Uptime · 30d
Uptime · 90d84.3%93.1%
Uptime · 30d75.0%93.3%
P50 · ms709272
P95 · ms2351842
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — temporary mailboxesFree — limits not published
Rate limitRate limited (429 on exceed); exact policy per docs.mail.tm5 req/window · 4 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

mail.tm vs MailCheck.ai: common questions

Which is more reliable, mail.tm or MailCheck.ai?

On our scheduled checks, MailCheck.ai leads on measured uptime — mail.tm at 84.3% versus MailCheck.ai at 93.1% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, mail.tm or MailCheck.ai?

MailCheck.ai has the lower median latency in our checks — mail.tm responds in 709 ms versus MailCheck.ai at 272 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 mail.tm and MailCheck.ai need an API key?

Neither needs a paid key — mail.tm is callable with no signup, and MailCheck.ai is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call mail.tm and MailCheck.ai from the browser?

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

Are mail.tm and MailCheck.ai free for commercial use?

mail.tm has unclear commercial terms, and MailCheck.ai 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.