mail.tm vs Resend

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

Uptime · 30d
Uptime · 90d84.3%0.0%
Uptime · 30d75.0%0.0%
P50 · ms709
P95 · ms2351
AuthnoneapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — temporary mailboxesFree tier — API key required
Rate limitRate limited (429 on exceed); exact policy per docs.mail.tmUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

mail.tm vs Resend: common questions

Which is more reliable, mail.tm or Resend?

On our scheduled checks, mail.tm leads on measured uptime — mail.tm at 84.3% versus Resend at 0.0% 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 mail.tm and Resend need an API key?

mail.tm needs no key, while Resend requires a free API key. If you want to start calling without signup, reach for mail.tm first.

Can I call mail.tm and Resend from the browser?

Neither sends browser-friendly CORS headers reliably, so call mail.tm and Resend from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are mail.tm and Resend free for commercial use?

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