HackMyIP vs Postcodes.io

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms15733
P95 · ms2167328
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseUnverifiedService MIT-licensed; postcode data license unverified
Free tierCompletely free — no API key, no signupFree — no key required
Rate limit100 req/windowUnpublished (no key; fair use)
In directory since2026-07-052026-07-05
operationalpartialdownno data

HackMyIP vs Postcodes.io: common questions

Which is more reliable, HackMyIP or Postcodes.io?

Both are neck-and-neck — HackMyIP and Postcodes.io 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, HackMyIP or Postcodes.io?

Postcodes.io has the lower median latency in our checks — HackMyIP responds in 157 ms versus Postcodes.io at 33 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 HackMyIP and Postcodes.io need an API key?

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

Can I call HackMyIP and Postcodes.io from the browser?

Yes — both HackMyIP and Postcodes.io send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are HackMyIP and Postcodes.io free for commercial use?

HackMyIP allows commercial use on its free tier, and Postcodes.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.