Catchdoms Security API vs YADG

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

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

Catchdoms Security API vs YADG: common questions

Which is more reliable, Catchdoms Security API or YADG?

On our scheduled checks, YADG leads on measured uptime — Catchdoms Security API at —% versus YADG 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 Catchdoms Security API and YADG need an API key?

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

Can I call Catchdoms Security API and YADG from the browser?

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

Are Catchdoms Security API and YADG free for commercial use?

Catchdoms Security API has unclear commercial terms, and YADG 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.