Download websites that use IPinfo

About IPinfo

Geolocation usually happens where no visitor ever sees it, in a server-side call that turns an address into a country before the page is even rendered. IPinfo sells that call as an API, which creates an awkward starting point for a page like this one: the more professionally the service is integrated, the less likely we are to see it at all.

As of October 2026 we detect IPinfo on 54 sites, and the figure is a floor rather than a measure of adoption. What the count captures is browser-side usage, where the lookup runs in the visitor's own client and leaves a request in the page for a crawler to notice. IPinfo has offered the service since 2013 on a Freemium model, and a free tier is precisely what encourages a developer to drop a client-side call in for a quick country check, a currency switch, a redirect or a first crude fraud signal. Paid integrations tend to migrate server-side and out of view, so our sample skews toward the smaller and the more experimental.

The undercount runs in a specific direction and it is worth being explicit about which one. Careful implementations disappear from our view first, because a team that cares about latency, cost control and not leaking an API token moves the lookup to its own backend. Anyone using this list to rank vendors by adoption is therefore measuring integration style rather than market share.

Presence still carries real information. A site calling an IP intelligence API from the browser has decided that visitor location changes what the page should do, which implies regional pricing, content gating, a compliance banner or an abuse filter somewhere in the product. Deciding that is a purchase-shaped decision even when the current plan costs nothing.

For a competing data vendor the list is a set of accounts that have already accepted the premise and need convincing only on accuracy or price. For a compliance researcher the same domains mark sites that make location-dependent decisions, which is a useful starting population if you want to study how consistently those decisions are applied. A lookup on one domain answers whether that site calls the API. Only a list answers which sites do, and that is the form of the question that supports sizing a segment or sampling it.

We file IPinfo under Geolocation, which is a coarse fit. IP intelligence sits closer to infrastructure than to page measurement, and it usually runs beside a real analytics stack rather than replacing one. We hold no version or geographic breakdown for the service either, which is expected for a hosted API where every customer is on whatever the vendor shipped last.