Hrvatski Telekom IP Ranges
Hrvatski Telekom is the Croatian fixed and mobile operator entered in the RIPE database as Hrvatski Telekom d.d. of Kruge 26, Zagreb, under the organisation object ORG-HA7-RIPE and company registration number 080266256. Its traffic originates from AS5391, abbreviated T-HT in the registry and described there as Croatian Telecom Inc., on an aut-num created 10 May 2002 and maintained under HPT-MNT, a maintainer prefix older than the current brand. Its blocks are netnamed HR-HPTNET plus a date: 93.136.0.0/13 carries HR-HPTNET-20080423 on a record created 23 April 2008.
- Provider
- Hrvatski Telekom
- Primary ASN
- AS5391
- Category
- ISP
- Headquarters
- Zagreb, Croatia
- Announced IPv4 prefixes
- 47
- Registry
- RIPE
Known IP ranges
These prefixes are currently announced to the global routing table by AS5391 (T-HT Hrvatski Telekom d.d.). Prefix sets change over time - use WHOIS Lookup for the authoritative record on any specific address.
93.140.0.0/16
93.139.0.0/16
78.2.0.0/16
93.137.0.0/16
78.3.0.0/16
93.141.0.0/16
89.172.0.0/16
83.131.0.0/16
93.142.0.0/16
93.138.0.0/16
2a00:c30::/29
2a00:c30::/32 (IPv6)
What does a Hrvatski Telekom IP mean in a privacy test?
Almost every address on this network answers to a name in one shape: the four octets joined with dashes, under adsl.net.t-com.hr, so 93.138.50.50 comes back as 93-138-50-50.adsl.net.t-com.hr. Resist reading adsl as the access technology. That zone is stamped on blocks allocated long after copper stopped being the only thing the company sold, and it turns up identically on ranges from 78.1.0.0 through 93.142.0.0, so it identifies the operator and nothing else about the connection. Because the naming never varies, it will not separate a household from a business either, and it carries none of the static or fixed markers the Hungarian and Spanish incumbents write into their own zones. Coverage is also uneven inside a single block: in 93.140.0.0/16 the addresses .150.20, .180.9 and .200.50 resolved while .1.1, .60.6 and .100.100 returned nothing, which is a gap in the operator's DNS rather than a different class of customer.
Hrvatski Telekom's registry footprint, and where it has gone stale
Everything the company publishes about its addressing sits in RIPE. Allocations point at org: ORG-HA7-RIPE, are maintained under HPT-MNT, and take the netname HR-HPTNET- with a date appended - a useful signature when you are checking whether a Croatian block really belongs here. The role object THT8-RIPE is listed on the aut-num as administrative contact, technical contact and abuse contact at once, which is the address to use rather than any general enquiry form.
The PeeringDB record is worth reading with a sceptical eye. It gives the IRR object as RIPE::AS-HRHINET and the peering policy as restrictive, both current, but it also declares zero IPv6 prefixes while 2a00:c30::/29 has been allocated to the company since 2012 and is announced today - a reminder that a self-maintained directory entry can drift from the routing table. No RFC 8805 file is referenced from any of these records and no geofeed: attribute appears on the allocations, so nothing here places an individual block in a Croatian city.
The operator's own subscribers against the networks it carries
AS5391 is a transit hub as well as an access network, and the IRR object says so in its own description: AS-HRHINET is defined as the autonomous systems routed by Hrvatski Telekom d.d., not the ones it owns. Its 184 members include AS-HTERONET and AS-BIHNET-ALL in Bosnia and Herzegovina, AS-TELEKOM-SRPSKE, plus Croatian networks such as AS-ISKON, AS-OPTIMA and AS-VIP. Membership means the company announces routes for them; it does not make their addresses Croatian, nor does it make them Hrvatski Telekom's.
At the level of a single address the registry is less generous than the routing data. The large allocations are ALLOCATED PA to the operator with no customer broken out of them, so a lookup returns the company and stops there, and the uniform reverse name adds nothing to it. That leaves two checks worth doing: confirm the block carries org: ORG-HA7-RIPE and an HR-HPTNET- netname before treating it as this operator's, and confirm the prefix is actually originated by AS5391 rather than merely reachable through it, since a transit customer's space will look adjacent in a routing lookup but resolve to another company entirely.
Related tools
Frequently asked questions
What IP ranges does Hrvatski Telekom use?
The operator announces its space from AS5391 and registers it with RIPE under ORG-HA7-RIPE. The blocks listed above are the largest currently announced. Any other Croatian address can be checked against the RIPE inetnum, where this company's allocations carry a netname beginning HR-HPTNET- with a date attached.
Why does a Hrvatski Telekom IP turn up in my privacy test?
Almost every address on this network answers to a name in one shape: the four octets joined with dashes, under adsl.net.t-com.hr, so 93.138.50.50 comes back as 93-138-50-50.adsl.net.t-com.hr. Resist reading adsl as the access technology. That zone is stamped on blocks allocated long after copper stopped being the only thing the company sold, and it turns up identically on ranges from 78.1.0.0 through 93.142.0.0, so it identifies the operator and nothing else about the connection. Because the naming never varies, it will not separate a household from a business either, and it carries none of the static or fixed markers the Hungarian and Spanish incumbents write into their own zones. Coverage is also uneven inside a single block: in 93.140.0.0/16 the addresses .150.20, .180.9 and .200.50 resolved while .1.1, .60.6 and .100.100 returned nothing, which is a gap in the operator's DNS rather than a different class of customer.
Does adsl.net.t-com.hr mean the connection is on ADSL?
No. The zone name is applied across blocks allocated years after ADSL ceased to be the only product, and the same pattern appears on ranges throughout the operator's space. It identifies Hrvatski Telekom as the operator and tells you nothing about whether the line is copper, fibre or anything else.
Why do some Croatian addresses on this network have no reverse name?
Coverage of the zone is broad but uneven, and it varies inside a single block rather than between blocks. Sampling 93.140.0.0/16 returned names on .150.20, .180.9 and .200.50 and nothing on .1.1, .60.6 and .100.100. The absence is a hole in the operator's DNS rather than a sign that the address is used differently.
Is every network in AS-HRHINET part of Hrvatski Telekom?
No. That object describes itself as the autonomous systems routed by Hrvatski Telekom, and its 184 members include transit customers across the region such as HT Eronet and Telekom Srpske. To decide whether an address is the operator's own, check that the prefix is originated by AS5391 and that the RIPE record shows ORG-HA7-RIPE.