Disify vs mailboxlayer

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

Uptime · 30d
Uptime · 90d42.2%100%
Uptime · 30d28.3%100%
P50 · ms1075316
P95 · ms16792634
AuthnoneapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limit30 req/window · 21 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Disify vs mailboxlayer: common questions

Which is more reliable, Disify or mailboxlayer?

On our scheduled checks, mailboxlayer leads on measured uptime — Disify at 42.2% versus mailboxlayer at 100% 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, Disify or mailboxlayer?

mailboxlayer has the lower median latency in our checks — Disify responds in 1075 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 Disify and mailboxlayer need an API key?

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

Can I call Disify and mailboxlayer from the browser?

Neither sends browser-friendly CORS headers reliably, so call Disify 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 Disify and mailboxlayer free for commercial use?

Disify 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.