shipapis
StarSubmit an APISubmit API

ddownload vs Genderize.io

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

APIddownloadREACHABLE100Genderize.ioHEALTHY62
Uptime · 30d
Uptime · 90d100%41.2%
Uptime · 30d100%36.7%
P50 · ms365632
P95 · ms7921060
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredKeyless usage limited (x-rate-limit-limit: 25 observed); 2,500 names/mo with a free key
Rate limitUnpublishedKeyless cap 25 per x-rate-limit-limit header; remaining/reset exposed in response headers
In directory since2026-07-052026-07-05
operationalpartialdownno data

ddownload vs Genderize.io: common questions

Which is more reliable, ddownload or Genderize.io?

On our scheduled checks, ddownload leads on measured uptime — ddownload at 100% versus Genderize.io at 41.2% 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, ddownload or Genderize.io?

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

Genderize.io needs no key, while ddownload requires a free API key. If you want to start calling without signup, reach for Genderize.io first.

Can I call ddownload and Genderize.io from the browser?

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

Are ddownload and Genderize.io free for commercial use?

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