DomainDb Info vs GitHub REST API

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms234568
P95 · ms16352671
Authnonenone
CORSnoyes
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

DomainDb Info vs GitHub REST API: common questions

Which is more reliable, DomainDb Info or GitHub REST API?

Both are neck-and-neck — DomainDb Info and GitHub REST API 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 GitHub REST API?

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

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

Can I call DomainDb Info and GitHub REST API from the browser?

Only GitHub REST API 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 GitHub REST API free for commercial use?

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