LectServe vs mailboxlayer

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms786316
P95 · ms16332634
AuthnoneapiKey
CORSyesno
HTTPSnoyes
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

LectServe vs mailboxlayer: common questions

Which is more reliable, LectServe or mailboxlayer?

On our scheduled checks, mailboxlayer leads on measured uptime — LectServe at 99.02% 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, LectServe or mailboxlayer?

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

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

Can I call LectServe and mailboxlayer from the browser?

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

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