# How to verify that a German mobile proxy is really on O2, Vodafone or 1&1

Source: https://ipvolt.com/blog/verify-german-mobile-proxy-carrier
Markdown: https://ipvolt.com/blog/verify-german-mobile-proxy-carrier.md

[Home](https://ipvolt.com/index.md) / [Blog](https://ipvolt.com/blog.md) / German Mobile Proxy: How to Verify O2, Vodafone or 1&1

Category: Analysis
Published: 2026-11-12
Updated: 2026-11-12
Author: ipvolt
Reading time: 10 minutes
Tags: proxies, choosing

Check a German mobile proxy's carrier with public records: get the exit IP, look up its ASN in RDAP and PeeringDB, and compare it with O2, Vodafone and 1&1.

## Short answer

Get the proxy's exit IP, look up which autonomous system (ASN) announces it, and compare that number with the carrier's row in the table below: AS6805 for O2, AS3209 for Vodafone, AS8881 for 1&1's registered access ranges. A match shows the address belongs to that operator's network. It doesn't show a phone or a SIM card, because all three networks also carry fixed lines. An ASN that belongs to a hosting company, or to a company other than these three, means the proxy isn't on the carrier it names.

ipvolt sells [Germany mobile proxies](/proxies/germany) on O2, Vodafone and 1&1, so those are the three carriers covered here. What this post is based on:

- **Public records only**, looked up on 12 November 2026: the RIPE database, RDAP, PeeringDB, the carriers' own pages and RFCs.
- **No proxy.** We rented and used no proxy device for this post. The table says what the registries say, not what a device showed.
- **The general method** is in [how to check if a proxy is really mobile or residential](/blog/check-if-proxy-is-mobile-or-residential), which ran these checks on a live mobile line and a datacenter IP. This post adds the German carriers.
- **The data.** Every lookup and its time is in the [records file](/downloads/verify-german-mobile-proxy-carrier/records.json). Sample addresses are cut to /24 there and here.

## The table: German carriers and their ASNs

| Brand | Network operator | ASN | Registered name and holder | PeeringDB type | Sources | Checked |
| --- | --- | --- | --- | --- | --- | --- |
| O2 | Telefónica Germany | AS6805 | TDDE-ASN1, Telefonica Germany GmbH & Co.OHG | NSP | [RDAP](https://rdap.db.ripe.net/autnum/6805), [PeeringDB](https://www.peeringdb.com/asn/6805) | 12 Nov 2026 |
| Vodafone | Vodafone | AS3209 | VODANET, Vodafone GmbH | Cable/DSL/ISP | [RDAP](https://rdap.db.ripe.net/autnum/3209), [PeeringDB](https://www.peeringdb.com/asn/3209) | 12 Nov 2026 |
| 1&1 | 1&1 Mobilfunk, with Vodafone antennas where its own network is missing | AS8881 (not confirmed for mobile, see below) | VERSATEL, 1&1 Versatel GmbH | Cable/DSL/ISP | [RDAP](https://rdap.db.ripe.net/autnum/8881), [PeeringDB](https://www.peeringdb.com/asn/8881) | 12 Nov 2026 |

The operator column follows the [Bundesnetzagentur](https://www.bundesnetzagentur.de/DE/Fachthemen/Telekommunikation/Marktdaten/Mobilfunkteilnehmer/start.html), whose subscriber table (dated 10 September 2026) lists Telekom, Vodafone, Telefónica and 1&1 Mobilfunk as network operators and notes "D2-Netz = Vodafone" and "E2-Netz = Telefónica Germany (Marke o2)". All three ASNs are registered with the RIPE NCC: IANA's [bootstrap file](https://data.iana.org/rdap/asn.json) sends each of them to RIPE's RDAP server, and each holder's organisation record there gives the country DE.

What the registry adds for each carrier:

- **O2.** Telefónica names some ranges inside AS6805 by purpose. [176.0.0.0/16](https://rdap.db.ripe.net/ip/176.0.0.0/16) is registered as MOBILE-POOL-NET and [46.114.0.0/16](https://rdap.db.ripe.net/ip/46.114.0.0/16) as MOBILE-NATPOOL-NET. An exit IP in a range named like that is the best registry evidence there is for an O2 mobile line. A second ASN, [AS13184](https://rdap.db.ripe.net/autnum/13184) (HANSENET), is also registered to Telefónica Germany; its record says "AS13184 will be merged to AS6805".
- **Vodafone.** The AS3209 record calls it the "International IP-Backbone of Vodafone". Inside it, [80.226.0.0/19](https://rdap.db.ripe.net/ip/80.226.0.0/19) is described as "Mobile APN NAT Pool", and the block from 80.226.64.0 to 80.226.255.255 as "Mobile Internet Access (2G&3G)". Two more ASNs are registered to Vodafone companies under cable network names: AS31334 (KABELDEUTSCHLAND-AS, Vodafone GmbH) and AS20825 (UNITYMEDIA, Vodafone West GmbH).
- **1&1.** This row is the least certain, and the records explain why:
  - **Its own network.** 1&1 has run its own mobile network since 8 December 2023. On 11 November 2025 it announced that the move of its customers to that network was finished: "Alle 1&1 Kundinnen und Kunden nutzen nun das moderne 5G-Netz" ([1&1](https://unternehmen.1und1.de/o-ran-mobilfunknetz/2025/1-1-o-ran-groesste-kundenmigration-der-deutschen-mobilfunkgeschichte-abgeschlossen)). Before that it sold mobile service as a reseller on other operators' networks, so older articles may map 1&1 differently.
  - **Roaming.** Where its own network isn't available, customers connect "über Antennen unseres National-Roaming-Partners Vodafone" ([1&1 Netzcheck](https://mobile.1und1.de/netzcheck)).
  - **No mobile ASN on record.** On 12 November 2026 the RIPE database had no organisation called 1&1 Mobilfunk, and no ASN registered to 1&1 Telecom GmbH.
  - **What is on record.** Access ranges registered to 1&1 Telecom GmbH, such as [109.250.0.0/17](https://rdap.db.ripe.net/ip/109.250.0.0/17), are named ONEANDONE-ACCESS and carry the remark "routed by AS8881". AS8881 belongs to 1&1 Versatel GmbH. No record says which of these ranges serve mobile customers.
  - **So:** AS8881 is where the registry points for a 1&1 line. We did not confirm it on a 1&1 SIM.

## Step by step

### 1. Get the exit IP through the proxy

```bash
curl -s -x "http://USER:PASS@HOST:PORT" https://api.ipify.org
```

Put your proxy's username, password, host and port in place of the capitals; for SOCKS5, start the URL with `socks5h://`. The answer is the address the echo service saw, which is the exit IP. The proxy's own hostname or gateway address is not. If the address changes between two runs, look up each one.

The commands below use 203.0.113.7, an address reserved for documentation ([RFC 5737](https://www.rfc-editor.org/rfc/rfc5737)), and AS64496, a number reserved for documentation ([RFC 5398](https://www.rfc-editor.org/rfc/rfc5398)). Put your exit IP and its ASN in their place. They also use `jq` to cut the JSON down to the fields that matter.

### 2. Look up the ASN and the registered range

RIPEstat's [network-info call](https://stat.ripe.net/docs/data-api/api-endpoints/network-info) returns the announced prefix and the ASN that announces it. RDAP, the registries' JSON interface, returns the registered range and its name; the `ip/` and `autnum/` paths are defined in [RFC 9082](https://www.rfc-editor.org/rfc/rfc9082). RIPE's server answers for ranges registered with RIPE and redirects other queries to the right registry ([RIPE Database docs](https://docs.db.ripe.net/How-to-Query-the-RIPE-Database/Registration-Data-Access-Protocol/)), which is why the commands pass `-L`.

```bash
curl -s "https://stat.ripe.net/data/network-info/data.json?resource=203.0.113.7" | jq -c '.data'
curl -sL "https://rdap.db.ripe.net/ip/203.0.113.7" | jq '{handle, name, country, type, remarks: [.remarks[]?.description[]]}'
```

We ran both on two real addresses on 12 November 2026. The first is a carrier address: 176.0.10.x, inside Telefónica Germany's publicly announced range 176.0.0.0/13.

```text
{"asns":["6805"],"prefix":"176.0.0.0/13"}
{
  "handle": "176.0.0.0 - 176.0.255.255",
  "name": "MOBILE-POOL-NET",
  "country": "DE",
  "type": "ASSIGNED PA",
  "remarks": [
    "Telefonica Germany GmbH & Co. OHG",
    "Georg-Brauchle-Ring 50",
    "80992 Muenchen"
  ]
}
```

The second is a datacenter address: our lab server's own cloud IP, 204.168.249.x.

```text
{"asns":["24940"],"prefix":"204.168.128.0/17"}
{
  "handle": "204.168.240.0 - 204.168.255.255",
  "name": "CLOUD-HEL1",
  "country": "FI",
  "type": "ASSIGNED PA",
  "remarks": [
    "INFRA-AW"
  ]
}
```

Then ask who holds the ASN:

```bash
curl -sL "https://rdap.db.ripe.net/autnum/64496" | jq '{handle, name, holder: [.entities[] | select(.handle | startswith("ORG-")) | .vcardArray[1][] | select(.[0] == "fn") | .[3]]}'
```

For AS6805 and AS24940 this returned:

```text
{
  "handle": "AS6805",
  "name": "TDDE-ASN1",
  "holder": [
    "Telefonica Germany GmbH & Co.OHG"
  ]
}
{
  "handle": "AS24940",
  "name": "HETZNER-AS",
  "holder": [
    "Hetzner Online GmbH"
  ]
}
```

### 3. Check the network type in PeeringDB

PeeringDB is where networks describe themselves to other networks. Its API answers without an account:

```bash
curl -s "https://www.peeringdb.com/api/net?asn=64496" | jq -c '.data[] | {name, aka, info_types, info_scope}'
```

For the same two ASNs:

```text
{"name":"Telefónica Germany GmbH & Co. OHG","aka":"former Telefonica Deutschland, former mediaWays GmbH","info_types":["NSP"],"info_scope":"Europe"}
{"name":"Hetzner Online","aka":"","info_types":["Content"],"info_scope":"Europe"}
```

The type is "self-declared and might be rarely updated" ([PeeringDB](https://docs.peeringdb.com/blog/network_type_what_why_how/)). None of the three German entries says mobile: Telefónica lists NSP, Vodafone and 1&1 Versatel list Cable/DSL/ISP. So PeeringDB can separate a carrier from a hosting or content network. It can't confirm a mobile line.

### 4. Compare with the table

- **The ASN is the carrier's row.** The address is in that operator's network. For O2 and Vodafone, also compare the range name from step 2 with the mobile ranges named above.
- **The ASN is a different one from the same group** (AS13184, AS31334, AS20825, or AS8560, covered below). It is registered to the group, but it isn't the ASN the mobile-labelled ranges are announced from. Ask the seller which network the SIM is on.
- **Any other ASN.** The proxy isn't on that carrier.

Reverse DNS is an optional fifth check:

```bash
dig -x 203.0.113.7 +short
```

We looked up one address in each named range on 12 November 2026. The last octet is masked:

| Range and registered name | Reverse DNS name |
| --- | --- |
| 176.0.0.0/16, MOBILE-POOL-NET (O2) | `dynamic-176-000-010-xxx.176.0.pool.telefonica.de` |
| 46.114.0.0/16, MOBILE-NATPOOL-NET (O2) | `dynamic-046-114-010-xxx.46.114.pool.telefonica.de` |
| 89.204.132.0/23, o2-Germany-Customer-NATPool-MUN | none |
| 80.226.0.0/19, Mobile APN NAT Pool (Vodafone) | `ip-80-226-1-x.vodafone-net.de` |
| 109.40.0.0/14, DE-D2VODAFONE-20220628 (Vodafone) | `ip-109-40-10-x.web.vodafone.de` |
| 109.250.0.0/17, ONEANDONE-ACCESS (1&1) | `i6DFA0Axx.versanet.de` |
| 185.235.232.0/23, ONEANDONE-ACCESS (1&1) | none |

`web.vodafone.de` is also the access point name Vodafone gives customers for mobile internet ([Vodafone](https://www.vodafone.de/featured/article/vodafone-apn-einstellungen-178757)). We found no page where the operators document these names, and each row is one address, so treat a name as a supporting detail and not as proof.

## The fast way: ipvolt's proxy checker

Paste the proxy into the free [proxy checker](/tools/proxy-checker) as `host:port:user:pass` or as a URL. It connects through the proxy to ipvolt's own endpoint and shows the result in one row. Read three fields:

- **Exit IP:** the address to look up.
- **ASN and network:** the AS number, the network's name from the DB-IP Lite database, and a network type. Compare the AS number with the table.
- **Location:** the city DB-IP Lite gives for the exit IP. The next section explains why the city can be off.

The checker only accepts proxies, so we ran its lookup code on the four sample addresses instead. It returned:

| Sample address | ASN and network |
| --- | --- |
| 176.0.10.x (O2 range) | AS6805 Telefonica Germany GmbH & Co.OHG · Carrier (mobile and fixed lines) (estimate) |
| 80.226.1.x (Vodafone range) | AS3209 Vodafone GmbH · Carrier (mobile and fixed lines) (estimate) |
| 109.250.10.x (1&1 range) | AS8881 1&1 Versatel GmbH · Internet provider (estimate) |
| 204.168.249.x (lab server) | AS24940 Hetzner Online GmbH · Hosting or data centre (estimate) |

The type is an estimate made from the ASN, as the label says. It does not test the device.

## What can look wrong and still be fine

- **A different German city.** Three free IP databases placed our two carrier samples like this on 12 November 2026:

  | Sample | ipinfo | DB-IP | IP2Location.io |
  | --- | --- | --- | --- |
  | 176.0.10.x (O2) | Berlin | Berlin | Strausberg, Brandenburg |
  | 80.226.1.x (Vodafone) | Bernburg, Saxony-Anhalt | Düsseldorf | Platz, Sachsen-Anhalt |

  The registry doesn't settle it. The MOBILE-POOL-NET record carries a Telefónica address in Munich, and RIPE says of the `country` attribute that "it cannot be used in any reliable way to map IP addresses to countries" ([RIPE Database docs](https://docs.db.ripe.net/RPSL-Object-Types/Descriptions-of-Primary-Objects/)).
- **An address shared with other subscribers.** A carrier-grade NAT (CGN) is a function "used to share the same IPv4 address among several subscribers" ([RFC 6888](https://www.rfc-editor.org/rfc/rfc6888)). [RFC 6598](https://www.rfc-editor.org/rfc/rfc6598) reserves 100.64.0.0/10 for the carrier's side of it. Both Telefónica and Vodafone register mobile ranges as NAT pools: MOBILE-NATPOOL-NET, o2-Germany-Customer-NATPool-MUN and "Mobile APN NAT Pool". For 1&1 we found no record either way.
- **Old company names.** Compare the AS number, not the name. All of these appear in the records for the three networks:
  - **Telefónica:** allocations named DE-MEDIAWAYS, and "former mediaWays GmbH" in PeeringDB.
  - **Vodafone:** DE-D2VODAFONE, DE-ARCOR and the AS name VODANET.
  - **1&1:** VERSATEL and `versanet.de`.
- **A fixed-line network type.** Vodafone and 1&1 Versatel list Cable/DSL/ISP because the same ASN carries their fixed lines. Telefónica also sells O2 home internet over fibre, cable, DSL and 4G/5G ([Telefónica](https://www.telefonica.de/network/fixed-network.html)).
- **A 1&1 line on Vodafone antennas.** 1&1's roaming sentence is about the radio link. It doesn't say which IP network the traffic leaves from, and we did not measure it.

## Signs it isn't a real mobile connection

1. **The ASN is registered to a hosting company.** Our lab server is in AS24940, HETZNER-AS, held by Hetzner Online GmbH. Its range is named CLOUD-HEL1 and its reverse DNS name is `static.x.249.168.204.clients.your-server.de`.
2. **PeeringDB lists the network as Content.** Hetzner's entry does. A hosting or content type doesn't fit a mobile carrier.
3. **The ASN belongs to another company or another registry.** The three holders are German companies with ASNs at the RIPE NCC. If RDAP redirects you to another registry, or names a holder that isn't in the table, the exit isn't in these networks.
4. **A "1&1" line in AS8560.** [AS8560](https://rdap.db.ripe.net/autnum/8560) is IONOS-AS, registered to IONOS SE. Its record calls it "the joint network for IONOS, Fasthosts, Arsys, 1&1 Mail and Media and 1&1 Telecom", and ipvolt's checker lists it as hosting. A 1&1 name in the record doesn't make it the mobile network.
5. **The right ASN but a pool with a different name.** In AS3209, our samples in 2.200.0.0/14 and 90.186.0.0/17 had names starting with `dslb-` under `pools.vodafone-ip.de`, unlike the names in the mobile-labelled ranges. That is a reason to ask the seller, not proof.

## What these checks can't tell you

- **The device.** An ASN describes a network. All three carry fixed lines too, so a matching ASN can't tell a phone from a home router.
- **Whether the labels are current.** Range names and PeeringDB types are whatever the holder wrote. The Vodafone range still described as "2G&3G" was last changed in January 2023.
- **1&1 mobile addresses.** No public record marks them, and we tested no 1&1 line.
- **Roaming.** Nothing here shows which antennas a line used.
- **How many people share the address.** A carrier NAT can't be seen from outside.
- **How a website will treat the address.** These checks say who the address is registered to and who announces it. They don't predict any site's decision.
- **Tomorrow's records.** The table is the registry's state on 12 November 2026. Look the ASN up again before you rely on it.

To test a line before you rely on it, use the checklist in [how to test a Germany proxy](/guides/germany-proxies). Carriers, prices and stock are on the [Germany mobile proxies](/proxies/germany) page.

**Check a proxy now:** paste it into ipvolt's free [proxy checker](/tools/proxy-checker), then compare the ASN it shows with the table above.

Need a German mobile IP on O2, Vodafone or 1&1? [Dedicated mobile proxies from $9 a day.](/mobile-proxies)

## Sources

- [Bundesnetzagentur: Teilnehmerentwicklung im Mobilfunk (network operators and network names)](https://www.bundesnetzagentur.de/DE/Fachthemen/Telekommunikation/Marktdaten/Mobilfunkteilnehmer/start.html)
- [RIPE database (RDAP): AS6805, TDDE-ASN1](https://rdap.db.ripe.net/autnum/6805)
- [RIPE database (RDAP): AS3209, VODANET](https://rdap.db.ripe.net/autnum/3209)
- [RIPE database (RDAP): AS8881, VERSATEL](https://rdap.db.ripe.net/autnum/8881)
- [PeeringDB: AS6805, Telefónica Germany GmbH & Co. OHG](https://www.peeringdb.com/asn/6805)
- [PeeringDB: AS3209, Vodafone Germany](https://www.peeringdb.com/asn/3209)
- [PeeringDB: AS8881, 1&1 Versatel Deutschland](https://www.peeringdb.com/asn/8881)
- [IANA: RDAP bootstrap file for AS numbers](https://data.iana.org/rdap/asn.json)
- [RIPE database (RDAP): 176.0.0.0/16, MOBILE-POOL-NET](https://rdap.db.ripe.net/ip/176.0.0.0/16)
- [RIPE database (RDAP): 46.114.0.0/16, MOBILE-NATPOOL-NET](https://rdap.db.ripe.net/ip/46.114.0.0/16)
- [RIPE database (RDAP): AS13184, HANSENET](https://rdap.db.ripe.net/autnum/13184)
- [RIPE database (RDAP): 80.226.0.0/19, Vodafone GmbH, Mobile APN NAT Pool](https://rdap.db.ripe.net/ip/80.226.0.0/19)
- [1&1: 1&1 O-RAN, größte Kundenmigration der deutschen Mobilfunkgeschichte abgeschlossen (11 November 2025)](https://unternehmen.1und1.de/o-ran-mobilfunknetz/2025/1-1-o-ran-groesste-kundenmigration-der-deutschen-mobilfunkgeschichte-abgeschlossen)
- [1&1 Netzcheck: Welches Mobilfunknetz nutzt 1&1?](https://mobile.1und1.de/netzcheck)
- [RIPE database (RDAP): 109.250.0.0/17, ONEANDONE-ACCESS](https://rdap.db.ripe.net/ip/109.250.0.0/17)
- [RFC 5737: IPv4 Address Blocks Reserved for Documentation](https://www.rfc-editor.org/rfc/rfc5737)
- [RFC 5398: Autonomous System (AS) Number Reservation for Documentation Use](https://www.rfc-editor.org/rfc/rfc5398)
- [RIPEstat Data API: network-info](https://stat.ripe.net/docs/data-api/api-endpoints/network-info)
- [RFC 9082: Registration Data Access Protocol (RDAP) Query Format](https://www.rfc-editor.org/rfc/rfc9082)
- [RIPE Database docs: Registration Data Access Protocol (RDAP)](https://docs.db.ripe.net/How-to-Query-the-RIPE-Database/Registration-Data-Access-Protocol/)
- [PeeringDB: Network Type: What's it for? How to use it?](https://docs.peeringdb.com/blog/network_type_what_why_how/)
- [Vodafone: APN-Einstellungen für Android und iPhone](https://www.vodafone.de/featured/article/vodafone-apn-einstellungen-178757)
- [RIPE Database docs: Descriptions of Primary Objects (the country attribute)](https://docs.db.ripe.net/RPSL-Object-Types/Descriptions-of-Primary-Objects/)
- [RFC 6888: Common Requirements for Carrier-Grade NATs (CGNs)](https://www.rfc-editor.org/rfc/rfc6888)
- [RFC 6598: IANA-Reserved IPv4 Prefix for Shared Address Space](https://www.rfc-editor.org/rfc/rfc6598)
- [Telefónica Deutschland: fixed network (O2 over fibre, cable, DSL and 4G/5G)](https://www.telefonica.de/network/fixed-network.html)
- [RIPE database (RDAP): AS8560, IONOS-AS](https://rdap.db.ripe.net/autnum/8560)

## Plug in your first proxy.

Mobile from $9 a day. Residential from $2.20 per GB.

[Buy mobile](https://ipvolt.com/dashboard/mobile)

[Buy residential](https://ipvolt.com/dashboard/residential)

## Related posts

- [How to Check if a Proxy Is Really Mobile or Residential](https://ipvolt.com/blog/check-if-proxy-is-mobile-or-residential.md) (Analysis, Nov 8, 2026, 12 min read): No single check proves a proxy is mobile or residential. We tested ASN, RDAP, PeeringDB, reverse DNS and IP databases on a mobile line and a datacenter IP.
- [How Many GB of Proxies Do You Need? Pages per GB, Measured](https://ipvolt.com/blog/how-many-gb-of-proxies-do-i-need.md) (Benchmark, Oct 5, 2026, 8 min read): We loaded 34 public pages three ways through a metering proxy. 1 GB fits about 44,000 HTML-only fetches, or about 900 full Playwright page loads.
- [Unlimited residential proxies: what they cost per GB](https://ipvolt.com/blog/unlimited-residential-proxies-cost-per-gb.md) (Comparison, Sep 27, 2026, 18 min read): Turn Mbps- and thread-based unlimited residential proxy plans into cost per GB, find the break-even with your per-GB rate, and check terms before you pay.

## Related guides

- [How to test a Germany proxy: networks, cities and regions](https://ipvolt.com/guides/germany-proxies.md): Evaluate Germany proxies with current carrier and roaming context, city-location limits, browser-language controls and a practical acceptance checklist.
- [Mobile vs residential proxies: build a useful evaluation](https://ipvolt.com/guides/mobile-vs-residential-proxies.md): Compare carrier and household exit networks for QA, keep browser emulation separate, and measure the capabilities your workflow actually needs.
- [Rotating vs sticky proxies: plan for session continuity](https://ipvolt.com/guides/rotating-vs-sticky-proxies.md): Choose rotation around the smallest complete workflow, distinguish exit affinity from cookies, and test what happens when a sticky session ends early.

## About ipvolt

Technical analysis from ipvolt.

Mobile from $9 a day. Residential from $2.20 per GB.