shipapis
StarSubmit an APISubmit API

Hebrew Calendar vs mail.tm

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

APIHebrew CalendarHEALTHY93mail.tmHEALTHY82
Uptime · 30d
Uptime · 90d100%84.3%
Uptime · 30d100%75.0%
P50 · ms533709
P95 · ms20162351
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — temporary mailboxes
Rate limitUnpublishedRate limited (429 on exceed); exact policy per docs.mail.tm
In directory since2026-07-052026-07-05
operationalpartialdownno data

Hebrew Calendar vs mail.tm: common questions

Which is more reliable, Hebrew Calendar or mail.tm?

On our scheduled checks, Hebrew Calendar leads on measured uptime — Hebrew Calendar at 100% versus mail.tm at 84.3% 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, Hebrew Calendar or mail.tm?

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

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

Can I call Hebrew Calendar and mail.tm from the browser?

Only Hebrew Calendar 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 Hebrew Calendar and mail.tm free for commercial use?

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