shipapis
StarSubmit an APISubmit API

Footer Year Update vs mail.tm

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

APIFooter Year UpdateNEW—mail.tmNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
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

Footer Year Update vs mail.tm: common questions

Which is more reliable, Footer Year Update or mail.tm?

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

Neither needs a paid key — Footer Year Update 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 Footer Year Update and mail.tm from the browser?

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

Are Footer Year Update and mail.tm free for commercial use?

Footer Year Update 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.