ddownload vs Hunter

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms365362
P95 · ms792859
AuthapiKeyapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ddownload vs Hunter: common questions

Which is more reliable, ddownload or Hunter?

Both are neck-and-neck — ddownload and Hunter 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, ddownload or Hunter?

Hunter has the lower median latency in our checks — ddownload responds in 365 ms versus Hunter at 362 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 ddownload and Hunter need an API key?

Both ask you to authenticate — ddownload uses an API key and Hunter uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call ddownload and Hunter from the browser?

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

Are ddownload and Hunter free for commercial use?

ddownload has unclear commercial terms, and Hunter 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.