mail.tm vs Namedays Calendar
Same instrument, two spec sheets — measured, not claimed.
mail.tm vs Namedays Calendar: common questions
Which is more reliable, mail.tm or Namedays Calendar?
On our scheduled checks, Namedays Calendar leads on measured uptime — mail.tm at 84.3% versus Namedays Calendar at 91.2% 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 Namedays Calendar?
Namedays Calendar has the lower median latency in our checks — mail.tm responds in 709 ms versus Namedays Calendar at 480 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 Namedays Calendar need an API key?
Neither needs a paid key — mail.tm is callable with no signup, and Namedays Calendar is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call mail.tm and Namedays Calendar from the browser?
Neither sends browser-friendly CORS headers reliably, so call mail.tm and Namedays Calendar 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 Namedays Calendar free for commercial use?
mail.tm has unclear commercial terms, and Namedays Calendar 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.