Autonomous system
AS13128 LIT-BERLIN-AS
Unclassified RIPE
Summary
ITDZ Berlin
government infrastructure enterprise
Contact handles built as a hierarchy: country, then sector, then federal state.
What it's used for
- The IT service centre of a German city-state government. 65,536 addresses in one IPv4 prefix, one IPv6 prefix, and ten observed BGP neighbours.
Notable
- The single prefix is
141.15.0.0/16, netnameBLNADM. - Its registry contacts are
DE-GOV-BE Admin,DE-GOV-BE TechandDE-GOV-BE Abuse Contact. - The IPv6 announcement is a
/32. - Three addresses were sampled and none returned a name.
Interesting
- Those contact handles are structured where almost every other record in this range is not: a country code, a sector, a state code, then a role. Read left to right they place the organisation in a national scheme, which means other German public bodies can be found by pattern rather than by name. Nothing in the registry requires or enforces this; someone imposed it.
BLNADMcompresses a city and a function into six characters, the older habit that the structured contacts replaced. Both conventions sit in the same record.- A whole /16 announced as one prefix through ten neighbours is a public-sector network built as a single addressing plan rather than assembled from whatever was available. Government allocations from this era were generous and are rarely subdivided afterwards.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
Recorded at 1 exchange in 1 country, largest first.
| Exchange | Location | Their address |
|---|---|---|
| Berlin Commercial Internet Exchange | Berlin, Germany | 193.178.185.150 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-26, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 1 prefixes · 65.54K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| DE | Germany | 2 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS13128- Registry name
- LIT-BERLIN-AS
- Registrant
- ITDZ-BLN-MNT
- Abuse contact
- Sub-LIR.Berlin@itdz-berlin.de
- Registered
- 2001-09-26
- Last changed
- 2021-12-07
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- IT-Dienstleistungszentrum Berlin
- Also known as
- ITDZ Berlin
- Scope
- Not Disclosed
- Traffic ratio
- Balanced
- Peering policy
- Open
- Present at
- 1 exchanges
- Website
- https://www.itdz-berlin.de
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 50% valid · 1 valid, 1 with no ROA
- ROAs
- 1 authorising AS13128
- ASPA
- no ASPA record
- IRR
- 100% registered · 2 of 2 announcements
- Route objects
- 14 naming AS13128
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 446 networks and 1,852 prefixes, as published 2026-10-27. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere