RDAP / Whois lookup

Look up authoritative registration records for a domain, IP, network prefix or ASN. Subdomains are resolved to their registrable domain automatically.

AS3320

Record foundRIPE NCC

DTAG

RDAP is structured authoritative registration data. Registration records and contacts do not establish current routing, device location or network safety.

Queried at10/11/2026, 16:06:59Local authoritative snapshot

ASN profile Network topology BGP routes

Resource type: Autonomous system
Registry: RIPE NCC
Registration country / region: Not provided by registry
Registration status: Active
Registered at: 1/1/1970, 00:00:00
Last changed: 12/11/2020, 15:33:02

Resource rangeAS3320 – AS3320Autonomous system

Resource records1ASN count

Public contacts7Published by the registry

Registry events2Authoritative change record

Authoritative registration details

Registry handle: AS3320
Name: DTAG
Allocation type: Not provided by registry
Parent handle: Not provided by registry
Whois server: whois.ripe.net
Authoritative RDAP host: rdap.db.ripe.net

Address and number range

Resource range: AS3320 – AS3320
Address family: Not applicable
Resource records: Not applicable

Registration entities and contacts

Only public fields from the authoritative RDAP response are shown. Roles are assigned by the registry.

7 entities

Registrant

DTAG-RRDTAG-RR

Not provided by registry

Registrant

Deutsche Telekom AGORG-DTA2-RIPE

+4942151555165+4942151554041+49391580100379

Eduard-Schopf-Allee 1 · D-28217 · Bremen · GERMANY

Registrant

ORG-NCC1-RIPERIPE-NCC-END-MNT

Not provided by registry

AdministrativeTechnical

Sebastian BeckerSB15220-RIPE

+49 228 18123797

Deutsche Telekom AG · Wolbecker Str. 268, 48155, Muenster, Deutschland

Abuse

Deutsche Telekom LIR Abuse ContactDTAG3-RIPE

abuse@telekom.de

Deutsche Telekom AG

Registrant

DTAG-NICDTAG-NIC

Not provided by registry

AdministrativeTechnical

DTAG Internet Routing RegistryDTAG1-RIPE

Not provided by registry

Deutsche Telekom Service GmbH · Internet Services · Eduard-Schopf-Allee 1 · DE 28217 Bremen

Registration and change events

2 events

Event	Time (UTC)	Actor
Last changed	12/11/2020, 15:33:02	Not provided by registry
Registration	1/1/1970, 00:00:00	Not provided by registry

Terms and remarks

Registry notices are shown verbatim so their authoritative meaning is not altered.

5 notices

Registry noticeInternet service provider operations peering coordinators for AS3320: <peering@telekom.de> abuse reports should be sent to the contacts listed in the registry entries for the IP address of the offending host system We share the view that for many networks (including ours:-) only some abstraction of the actual routing policy should/can be published in the IRR. Right now we are abstracting to a very essential minimum. the most important and helpful use of the IRR is to publish what a network will announce to peers and upstream we encourage all our neighbors to define and maintain an AS-set to describe their announcements, and to register all the routes (and have their customers do so as well) we maintain a list of what our neighbors have told us about their announcements towards AS3320 - in terms of AS-set (preferred), AS number, route-set (and the IRR database used to publish) in fact we apply route filters based on this for all neighbors - as far as feasible for data published through the RIPE routing registry we generate filters automatically we consider the integration of RIR and routing registry data and the application of RPSS authorization a great feature of the RIPE routing registry customers are strongly encouraged to define and maintain an AS-set that we will include in the definition of AS3320:AS-DTAG (if we are told the name) this will be sufficient to have our peers accept the routes

FilteredThis output has been filtered.

Whois Inaccuracy ReportingIf you see inaccuracies in the results, please visit:

SourceObjects returned came from source RIPE

Terms and ConditionsThis is the RIPE Database query service. The objects are in RDAP format.

CHA.LA authoritative RDAP snapshotIANA Bootstrap only locates the responsible registration service. Data comes from the corresponding RIR or domain registry and is cached locally by query target.Authoritative source: RIPE NCC · rdap.db.ripe.net