> For the complete documentation index, see [llms.txt](https://docs.ipdunar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ipdunar.com/products/overview-1/asn-targeting.md).

# ASN targeting

For mobile workloads, ASN targeting is the **single most important parameter**. Many sites detect "this user is on cellular *and* on carrier X" — pinning the carrier is what turns a generic mobile IP into a trusted one.

## How to specify

Same syntax as residential:

```
ipdunar_s1a2b3c4d5e-type-mob-region-us-asn-6167
```

ASN is a decimal integer, no `AS` prefix.

## Carrier ASN reference (top markets)

| Country | Carrier                       | ASN    |
| ------- | ----------------------------- | ------ |
| US      | Verizon Wireless              | 6167   |
| US      | T-Mobile US                   | 21928  |
| US      | AT\&T Mobility                | 20057  |
| GB      | EE                            | 12576  |
| GB      | Vodafone UK                   | 12969  |
| GB      | Three UK                      | 60339  |
| DE      | Deutsche Telekom (Telekom DE) | 3320   |
| DE      | Vodafone DE                   | 3209   |
| DE      | Telefónica O2 DE              | 6805   |
| FR      | Orange                        | 3215   |
| FR      | SFR                           | 15557  |
| FR      | Bouygues Telecom              | 5410   |
| JP      | KDDI                          | 2516   |
| JP      | NTT Docomo                    | 9605   |
| JP      | SoftBank                      | 17676  |
| KR      | SK Telecom                    | 9318   |
| KR      | KT                            | 4766   |
| KR      | LG U+                         | 17858  |
| BR      | Vivo / Telefónica BR          | 26599  |
| BR      | TIM                           | 26615  |
| BR      | Claro                         | 28573  |
| IN      | Reliance Jio                  | 55836  |
| IN      | Bharti Airtel                 | 24560  |
| IN      | Vodafone Idea                 | 38266  |
| MX      | Telcel                        | 8151   |
| MX      | AT\&T MX                      | 32098  |
| CA      | Bell Mobility                 | 577    |
| CA      | Rogers                        | 812    |
| CA      | Telus                         | 6327   |
| AU      | Telstra                       | 1221   |
| AU      | Optus                         | 4804   |
| AU      | TPG / Vodafone AU             | 133612 |

For the complete live list per country, query:

```bash
curl -H "Authorization: Bearer API_KEY" \
     "https://api.ipdunar.com/v1/mobile/asns?region=us"
```

## Combining with other parameters

```
ipdunar_s1a2b3c4d5e-type-mob-region-us-asn-6167                              # US, Verizon
ipdunar_s1a2b3c4d5e-type-mob-region-us-state-ca-asn-6167                     # California Verizon
ipdunar_s1a2b3c4d5e-type-mob-region-us-asn-6167-session-x-sesstime-60        # Sticky Verizon session
```

`state` and `city` on top of `asn` often produce insufficient pool — see [Locations](https://docs.ipdunar.com/products/overview-1/locations.md).

## When to use ASN

For mobile, **almost always**. Specifically:

* Apps that show different content based on detected carrier
* Sites that bind anti-bot fingerprints to ASN
* A/B testing carrier-specific features
* Compliance testing (ensure feature works on all carriers in a market)

## When **not** to use ASN

Only when you genuinely need carrier diversity — e.g. measuring how a site behaves across all carriers in a country. Even then, prefer rotating the ASN per request rather than leaving it empty, so you can attribute results.

## Inspecting the chosen ASN

```
X-IPdunar-Exit-ASN: 6167
X-IPdunar-Exit-ASN-Name: Cellco Partnership d/b/a Verizon Wireless
```

The name field follows the operator's BGP registration — useful for log analysis when you don't memorize ASN-to-carrier mappings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ipdunar.com/products/overview-1/asn-targeting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
