Magyar Telekom IP Ranges
Magyar Telekom is the Hungarian fixed and mobile operator whose routing records still carry the older T-Com and T-Online brand names. Its public internet traffic originates from AS5483, registered with RIPE under the organisation object ORG-HTM1-RIPE and described in the registry as a public internet access provider in Budapest. The allocations behind it date themselves in the netname, and here the date is real: 84.0.0.0/14 is HU-HTC-20040917 on an object created 17 September 2004, and 46.107.0.0/16 is HU-HTC-20100720 on one created 20 July 2010.
- Provider
- Magyar Telekom
- Primary ASN
- AS5483
- Category
- ISP
- Headquarters
- Budapest, Hungary
- Announced IPv4 prefixes
- 114
- Registry
- RIPE
Known IP ranges
These prefixes are currently announced to the global routing table by AS5483 (MAGYAR-TELEKOM-MAIN-AS Magyar Telekom Plc.). Prefix sets change over time - use WHOIS Lookup for the authoritative record on any specific address.
84.0.0.0/14
188.156.0.0/15
81.182.0.0/15
78.92.0.0/16
195.228.0.0/16
46.139.0.0/16
158.249.0.0/16
145.236.0.0/16
31.46.0.0/16
46.107.0.0/16
2001:4c48::/29
2a00:1110::/29
2001:4c48::/32 (IPv6)
What does a Magyar Telekom IP mean in a privacy test?
An address that answers under telekom.hu is a Hungarian access line, and the reverse name says which kind before you look anything else up. The operator writes the address into the PTR as eight uppercase hex digits, so 78.92.200.40 comes back as 4E5CC828.dsl.pool.telekom.hu and 31.46.100.100 as 1F2E6464.catv.pool.telekom.hu. Decode those digits: if they do not reproduce the address you are testing, the name is stale or forged rather than the operator's own. A third form, prefixed mlln and living under fixip.t-online.hu, marks a subscriber paying for an address that stays put, which makes it a far stronger identifier than a pool name. Pool addresses are recycled, so two sightings of the same pool name are not two sightings of the same household, and some blocks are unnamed entirely - every address sampled in 158.249.0.0/16 returned nothing.
Where Magyar Telekom states its own network policy
The machine-readable statement lives in the RIPE database rather than on telekom.hu. The aut-num object for AS5483 carries the working addresses in its remarks: lines - noc.ip@telekom.hu for the network, abuse@telekom.hu for complaints, peering@net.telekom.hu for interconnection - plus one operational note, that route flap damping is applied. The PeeringDB entry files the company as an NSP with a selective peering policy and points at the IRR object RIPE::AS-MAGYARTELEKOM.
That IRR object is where people go wrong. Described only as Hungarian Telekom ASes, it is not a list of Magyar Telekom's own addresses: it carries 218 members, among them AS-TELECOMROMANIA, AS-BEOTELNET, AS-ORIONTELEKOM and AS-SEVLUSH, because the set enumerates every network the company announces routes for, including operators in Romania, Serbia and Ukraine. To settle whether one address is the operator's own, open the RIPE inetnum: its blocks show org: ORG-HTM1-RIPE and a netname of the shape HU-HTC- plus a date which, on 84.0.0.0/14 and 46.107.0.0/16 alike, matches the object's own created field to the day. No geofeed: attribute appeared on any allocation examined here, so there is no operator-published city for these blocks.
Subscriber pool, paid fixed address, or Telekom's own hardware
Three naming families divide the space. Access lines take the hex form under two zones, 4E5CC828.dsl.pool.telekom.hu for a copper or fibre line and BC9CC81E.catv.pool.telekom.hu for a cable one, and the zone rather than the block decides which: 195.228.50.50 answers as mllnC3E43232.fixip.t-online.hu while 195.228.100.7, inside the same /16, answers as C3E46407.dsl.pool.telekom.hu. The operator's own equipment is named in words instead of hex, under sp.net.telekom.hu - 84.1.2.3 resolves to asw0-tiszabercel.sp.net.telekom.hu, carrying a Hungarian place name where a subscriber line would carry an encoded address.
So the useful split is pool against fixed, not residential against business. A .pool. name is an address handed out and taken back, worth nothing as a way of recognising a returning visitor once the session ends. A fixip name is somebody paying to keep the address, and it is the one form here that points at a single subscriber rather than a rotation. Coverage is patchy in a way that carries no meaning of its own: inside 46.107.0.0/16 the addresses .100.100 and .200.7 returned hex names while .5.5 and .10.10 returned nothing, and 158.249.0.0/16 was silent at every address tried. Read a missing PTR as a hole in the operator's zone, not as a different class of customer.
Related tools
Frequently asked questions
What IP ranges does Magyar Telekom use?
The company announces its address space from AS5483 and registers it with RIPE under ORG-HTM1-RIPE. The blocks shown above are the largest currently in the routing table. To check any other address, look for a RIPE inetnum whose netname begins HU-HTC- followed by the date the block was allocated, such as HU-HTC-20040917 for 84.0.0.0/14.
Why does a Magyar Telekom IP appear in my privacy test?
An address that answers under telekom.hu is a Hungarian access line, and the reverse name says which kind before you look anything else up. The operator writes the address into the PTR as eight uppercase hex digits, so 78.92.200.40 comes back as 4E5CC828.dsl.pool.telekom.hu and 31.46.100.100 as 1F2E6464.catv.pool.telekom.hu. Decode those digits: if they do not reproduce the address you are testing, the name is stale or forged rather than the operator's own. A third form, prefixed mlln and living under fixip.t-online.hu, marks a subscriber paying for an address that stays put, which makes it a far stronger identifier than a pool name. Pool addresses are recycled, so two sightings of the same pool name are not two sightings of the same household, and some blocks are unnamed entirely - every address sampled in 158.249.0.0/16 returned nothing.
What does a name like 4E5CC828.dsl.pool.telekom.hu mean?
The eight characters are the four octets of the address written in uppercase hexadecimal: 4E, 5C, C8 and 28 are 78, 92, 200 and 40. The part after them names the pool the address came from, dsl.pool for copper and fibre lines and catv.pool for cable ones. If the hex does not decode back to the address you looked up, treat the name as unreliable.
Is an address under t-online.hu still Magyar Telekom?
Yes. The fixip.t-online.hu zone carries an older brand name the company has kept in its DNS, and the underlying blocks are registered to the same RIPE organisation, ORG-HTM1-RIPE. A name in that zone signals an address sold to stay with one subscriber rather than one drawn from a pool.
Does everything in AS-MAGYARTELEKOM sit in Hungary?
No. That IRR object lists the 218 networks Magyar Telekom announces routes for, and its members include Romanian, Serbian and Ukrainian AS-SETs. A prefix inside the set may be originated by one of those downstream networks rather than by AS5483, so the set is the wrong tool for deciding whether an address is Hungarian.