DomainDb Info vs JSONPlaceholder

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms234401
P95 · ms16351096
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished1000 req/window · 999 remaining · resets 1783509378
In directory since2026-07-052026-07-05
operationalpartialdownno data

DomainDb Info vs JSONPlaceholder: common questions

Which is more reliable, DomainDb Info or JSONPlaceholder?

Both are neck-and-neck — DomainDb Info and JSONPlaceholder 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, DomainDb Info or JSONPlaceholder?

DomainDb Info has the lower median latency in our checks — DomainDb Info responds in 234 ms versus JSONPlaceholder at 401 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 DomainDb Info and JSONPlaceholder need an API key?

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

Can I call DomainDb Info and JSONPlaceholder from the browser?

Only JSONPlaceholder is browser-friendly — it returns CORS headers over HTTPS. DomainDb Info needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are DomainDb Info and JSONPlaceholder free for commercial use?

DomainDb Info has unclear commercial terms, and JSONPlaceholder 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.