Footer Year Update vs mailboxlayer

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms131316
P95 · ms3292634
AuthnoneapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Footer Year Update vs mailboxlayer: common questions

Which is more reliable, Footer Year Update or mailboxlayer?

Both are neck-and-neck — Footer Year Update and mailboxlayer each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Footer Year Update or mailboxlayer?

Footer Year Update has the lower median latency in our checks — Footer Year Update responds in 131 ms versus mailboxlayer at 316 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 Footer Year Update and mailboxlayer need an API key?

Footer Year Update needs no key, while mailboxlayer requires a free API key. If you want to start calling without signup, reach for Footer Year Update first.

Can I call Footer Year Update and mailboxlayer from the browser?

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

Are Footer Year Update and mailboxlayer free for commercial use?

Footer Year Update has unclear commercial terms, and mailboxlayer 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.