mail.tm vs Public Time API

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesno
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.tmUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

mail.tm vs Public Time API: common questions

Which is more reliable, mail.tm or Public Time API?

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

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

Can I call mail.tm and Public Time API from the browser?

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

Are mail.tm and Public Time API free for commercial use?

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