PurgoMalum vs Yes No

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

Uptime · 30d
Uptime · 90d86.3%100%
Uptime · 30d85.0%100%
P50 · ms423692
P95 · ms48331165
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

PurgoMalum vs Yes No: common questions

Which is more reliable, PurgoMalum or Yes No?

On our scheduled checks, Yes No leads on measured uptime — PurgoMalum at 86.3% versus Yes No 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, PurgoMalum or Yes No?

PurgoMalum has the lower median latency in our checks — PurgoMalum responds in 423 ms versus Yes No at 692 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 PurgoMalum and Yes No need an API key?

Neither needs a paid key — PurgoMalum is callable with no signup, and Yes No is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call PurgoMalum and Yes No from the browser?

Yes — both PurgoMalum and Yes No send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are PurgoMalum and Yes No free for commercial use?

PurgoMalum has unclear commercial terms, and Yes No 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.