ItsThisForThat vs Nationalize.io

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedKeyless usage limited (x-rate-limit-limit: 25 observed); 2,500 names/mo with a free key
Rate limitUnpublished (docs ask you not to hammer it)Keyless cap 25 per x-rate-limit-limit header; remaining/reset exposed in response headers
In directory since2026-07-052026-07-05
operationalpartialdownno data

ItsThisForThat vs Nationalize.io: common questions

Which is more reliable, ItsThisForThat or Nationalize.io?

On our scheduled checks, Nationalize.io leads on measured uptime — ItsThisForThat at —% versus Nationalize.io at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do ItsThisForThat and Nationalize.io need an API key?

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

Can I call ItsThisForThat and Nationalize.io from the browser?

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

Are ItsThisForThat and Nationalize.io free for commercial use?

ItsThisForThat has unclear commercial terms, and Nationalize.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.