Disify vs Footer Year Update

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

Uptime · 30d
Uptime · 90d42.2%100%
Uptime · 30d28.3%100%
P50 · ms1075131
P95 · ms1679329
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limit30 req/window · 21 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Disify vs Footer Year Update: common questions

Which is more reliable, Disify or Footer Year Update?

On our scheduled checks, Footer Year Update leads on measured uptime — Disify at 42.2% versus Footer Year Update at 100% 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, Disify or Footer Year Update?

Footer Year Update has the lower median latency in our checks — Disify responds in 1075 ms versus Footer Year Update at 131 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 Disify and Footer Year Update need an API key?

Neither needs a paid key — Disify is callable with no signup, and Footer Year Update is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Disify and Footer Year Update from the browser?

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

Are Disify and Footer Year Update free for commercial use?

Disify has unclear commercial terms, and Footer Year Update 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.