ipinfo.io Data for US Carrier IPs

ipinfo.io is where many developers go first when they want to know what an address is. Its free JSON response is short enough to read in one glance, and its paid data adds ASN type, carrier details and privacy detection. Because it is so easy to call, it ends up inside login flows, analytics pipelines and support tools. If you run a SpoofProxies line, the ipinfo record is a good plain description of what the world sees. Here is how to read each line of it for an AT&T, T-Mobile or Verizon address, and where the record stops.

The org line is the heart of it

The free response includes an org field that combines the autonomous system number with the name of the organisation that announces the range. For a carrier line this names the carrier's wireless network. On US carriers you will commonly see T-Mobile USA under AS21928, Verizon Wireless under the Cellco Partnership name on AS6167, and AT&T Mobility on AS20057, though ipinfo reports whatever is current for that range. This is the single most useful line for a site, because it separates wireless networks from hosting companies at a glance.

The ASN details product adds a type for the network, with values such as isp, hosting, business and education. A carrier range reads as isp. A hosting value would be a strong signal that your traffic is not leaving through the line at all, which is worth checking in your proxy settings before anything else.

Hostname, city and postal code

Many broadband addresses have a reverse DNS name that hints at a neighbourhood or a street cabinet. Mobile addresses often have no hostname, or a generic one that names the carrier and nothing else. That is normal for CGNAT pools and says nothing bad about the line. The city, region, postal code and coordinates in the response are ipinfo's estimate of where the address is used, and for mobile ranges they represent the area a carrier gateway serves. The time zone field is derived from that estimate and is the right value to copy into the browser or device you pair with the line.

Expect the city to shift a little between rotations inside a metro. Pools are regional, and neighbouring places may be attached to different parts of the pool.

The carrier and privacy products

ipinfo's carrier data returns the mobile carrier name along with its mobile country code and mobile network code for addresses it identifies as cellular. It exists for ad targeting and fraud work, and on our lines it is a quick way to confirm the carrier you picked at checkout. The privacy detection product returns separate booleans for vpn, proxy, tor, relay and hosting, and, where it can, the name of the service involved. On a carrier line the hosting and tor values should be false. The proxy value depends on what ipinfo has observed on that pool address, and like every vendor it can inherit a label from another device that used the same shared address.

The relay flag refers to privacy relays run by large platforms, such as operating-system-level private relay services. It should be false on our lines, since the traffic leaves straight from the carrier.

What developers do with it

Legitimate uses of ipinfo with a mobile line are mostly about testing your own product. A team building a signup flow can check that its code correctly treats a carrier address as a consumer connection and does not lump it in with data-centre traffic. A support team can confirm that a customer on a phone network sees the right regional price or language. An analytics team can verify that its geography reports are not treating mobile users as if they were all at one gateway. A dedicated line in each metro, with free moves between metros from the dashboard, makes those tests repeatable.

What you should not do is treat ipinfo output as something to optimise. It is a description. If a platform restricts an account, the record did not cause that, and a different record will not undo it.

The limits of a single response

ipinfo cannot tell how many phones are sharing the address, cannot see your browser, and cannot distinguish a dedicated proxy customer from an ordinary subscriber. Its data is updated frequently but is still a picture of what it last learned. Use it to confirm the network, carrier and region, then spend your attention on consistency where it actually shows: the same profile, the same metro, sensible hours.

Setting up a ipinfo.io proxy on SpoofProxies

1. Add a line in the dashboard and note the metro and carrier.
2. Copy the host, port, username and password into your HTTP or SOCKS5 client.
3. Request ipinfo.io through the line and confirm the org line names the carrier.
4. If you have access, check the ASN type, carrier and privacy fields as well.
5. Copy the time zone from the response into the paired browser or device.
6. Save the response as your baseline for that line.

ipinfo.io proxy questions