Whois & RDAP Lookup
PROXIED.COM Dedicated mobile proxies 4G/5G proxies · No caps Dedicated 4G/5G mobile proxies · Direct from trusted sellers Mobile 4G/5G · Dedicated, no sharing Uptime 99.9% · 10 countries Data Unlimited · No caps Customers 20K+ · No middlemen Free/trial Explore marketTry freeAS3320
RDAPHandleAS3320
NameDTAG
HolderDTAG-RR
Registered1970-01-01 00:00 UTC
Updated2020-12-11 15:33 UTC
RegistrantDTAG-RR
Admin ContactSebastian Becker
Phone+49 228 18123797
AddressDeutsche Telekom AG, Wolbecker Str. 268, 48155, Muenster, Deutschland
Tech ContactSebastian Becker
Phone+49 228 18123797
AddressDeutsche Telekom AG, Wolbecker Str. 268, 48155, Muenster, Deutschland
Abuse Contact[email protected]
Statusactive
Registry RDAPhttps://rdap.db.ripe.net
Raw WHOIS response
% This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See https://docs.db.ripe.net/terms-conditions.html % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to 'AS3209 - AS3353' as-block: AS3209 - AS3353 descr: RIPE NCC ASN block remarks: These AS Numbers are assigned to network operators in the RIPE NCC service region. mnt-by: RIPE-NCC-HM-MNT created: 2018-11-22T15:27:19Z last-modified: 2018-11-22T15:27:19Z source: RIPE % Information related to 'AS3320' % Abuse contact for 'AS3320' is '[email protected]' aut-num: AS3320 as-name: DTAG org: ORG-DTA2-RIPE descr: Internet service provider operations remarks: peering coordinators for AS3320: <[email protected]> remarks: abuse reports should be sent to the contacts listed in the registry entries for the IP address of the offending host system remarks: 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. remarks: the most important and helpful use of the IRR is to publish what a network will announce to peers and upstream # we are providing that by means of the AS-set AS3320:AS-DTAG which we have been keeping up to date all the time remarks: 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) import: from AS-ANY accept ANY # heavy abstraction hits! well, we are ... neither peering promiscuously nor accepting all junk routes offered... remarks: 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) remarks: in fact we apply route filters based on this for all neighbors - as far as feasible remarks: for data published through the RIPE routing registry we generate filters automatically remarks: we consider the integration of RIR and routing registry data and the application of RPSS authorization a great feature of the RIPE routing registry # unfortunately this benefit is not available with any other IRR database that we know of... and some of the IRR databases allow essentially any garbage to be registered without any control - making those databases quite useless... export: to AS3320:AS-CUSTOMERS announce ANY # but don't publish that list; in general - if they ask for less, we can do export: to AS-ANY announce AS3320:AS-DTAG # for peers and others... for backwards compatibility the older AS-DTAG will be kept around for some more time - defined using just members: AS3320:AS-DTAG please convert to AS3320:AS-DTAG if you are still using the old AS-DTAG remarks: 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) remarks: this will be sufficient to have our peers accept the routes remarks: in any case peers - and any network in the Internet - is free to apply some selective policy (e.g. prefix length based) # but we do not think that any such selective policy will be based on details of our routing policy omitted from this aut-num: object remarks: unfortunately some customers do not provide usable IRR data; we will NOT add to the uncontrolled garbage in the IRR by proxy registering in some database that requires no authorization remarks: we advise customers that routes without IRR registration and not covered by AS3320:AS-DTAG may receive less than full support by some of our peer networks and other parts of the Internet remarks: ============================================================== IPv6 we do/publish essentially the same like for IPv4 mp-import: afi ipv6.unicast from AS-ANY accept ANY # heavy abstraction... neither peering promiscuously nor accepting all junk routes offered... mp-export: afi ipv6.unicast to AS3320:AS-CUSTOMERS-V6 announce ANY # but don't publish that list; in general - if they ask for less, we can do mp-export: afi ipv6.unicast to AS-ANY announce AS3320:AS-DTAG-V6 # for peers and others... remarks: ============================================================== admin-c: SB15220-RIPE tech-c: SB15220-RIPE status: ASSIGNED mnt-by: RIPE-NCC-END-MNT mnt-by: DTAG-RR created: 1970-01-01T00:00:00Z last-modified: 2020-12-11T15:33:02Z source: RIPE organisation: ORG-DTA2-RIPE org-name: Deutsche Telekom AG country: DE reg-nr: District court Bonn HRB 6794 org-type: LIR address: Eduard-Schopf-Allee 1 address: D-28217 address: Bremen address: GERMANY phone: +4942151554041 phone: +4942151555165 fax-no: +494412344589 fax-no: +49391580100379 admin-c: DTAG-RIPE admin-c: SL7866-RIPE admin-c: EH4097-RIPE admin-c: SB15220-RIPE abuse-c: DTAG3-RIPE mnt-ref: RIPE-NCC-HM-MNT mnt-ref: DTAG-NIC mnt-by: RIPE-NCC-HM-MNT mnt-by: DTAG-NIC created: 2004-04-17T11:12:44Z last-modified: 2026-05-13T07:30:45Z source: RIPE # Filtered person: Sebastian Becker address: Deutsche Telekom AG address: Wolbecker Str. 268, 48155, Muenster, Deutschland phone: +49 228 18123797 nic-hdl: SB15220-RIPE mnt-by: DTAG-NIC mnt-by: DTAG-RR created: 2011-11-01T16:24:28Z last-modified: 2024-09-03T15:54:20Z source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.123 (DEXTER) % Query time: 746 msec % WHEN: Fri Jul 31 13:37:33 UTC 2026
Raw RDAP JSON (registry) https://rdap.db.ripe.net
{
"endAutnum": 3320,
"entities": [
{
"handle": "DTAG-RR",
"links": [
{
"href": "https://rdap.db.ripe.net/entity/DTAG-RR",
"rel": "self",
"value": "https://rdap.db.ripe.net/autnum/3320"
},
{
"href": "http://www.ripe.net/data-tools/support/documentation/terms",
"rel": "copyright",
"value": "http://www.ripe.net/data-tools/support/documentation/terms"
}
],
"objectClassName": "entity",
"roles": [
"registrant"
],
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"DTAG-RR"
],
[
"kind",
{},
"text",
"individual"
]
]
]
},
{
"handle": "ORG-DTA2-RIPE",
"links": [
{
"href": "https://rdap.db.ripe.net/entity/ORG-DTA2-RIPE",
"rel": "self",
"value": "https://rdap.db.ripe.net/autnum/3320"
},
{
"href": "http://www.ripe.net/data-tools/support/documentation/terms",
"rel": "copyright",
"value": "http://www.ripe.net/data-tools/support/documentation/terms"
}
],
"objectClassName": "entity",
"roles": [
"registrant"
],
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"Deutsche Telekom AG"
],
[
"kind",
{},
"text",
"org"
],
[
"adr",
{
"label": "Eduard-Schopf-Allee 1\nD-28217\nBremen\nGERMANY"
},
"text",
[
"",
"",
"",
"",
"",
"",
""
]
],
[
"tel",
{
"type": "voice"
},
"text",
"+4942151554041"
],
[
"tel",
{
"type": "voice"
},
"text",
"+4942151555165"
],
[
"tel",
{
"type": "fax"
},
"text",
"+494412344589"
],
[
"tel",
{
"type": "fax"
},
"text",
"+49391580100379"
]
]
]
},
{
"handle": "RIPE-NCC-END-MNT",
"links": [
{
"href": "https://rdap.db.ripe.net/entity/RIPE-NCC-END-MNT",
"rel": "self",
"value": "https://rdap.db.ripe.net/autnum/3320"
},
{
"href": "http://www.ripe.net/data-tools/support/documentation/terms",
"rel": "copyright",
"value": "http://www.ripe.net/data-tools/support/documentation/terms"
}
],
"objectClassName": "entity",
"roles": [
"registrant"
],
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"RIPE-NCC-END-MNT"
],
[
"kind",
{},
"text",
"individual"
],
[
"org",
{},
"text",
"ORG-NCC1-RIPE"
]
]
]
},
{
"handle": "SB15220-RIPE",
"links": [
{
"href": "https://rdap.db.ripe.net/entity/SB15220-RIPE",
"rel": "self",
"value": "https://rdap.db.ripe.net/autnum/3320"
},
{
"href": "http://www.ripe.net/data-tools/support/documentation/terms",
"rel": "copyright",
"value": "http://www.ripe.net/data-tools/support/documentation/terms"
}
],
"objectClassName": "entity",
"roles": [
"administrative",
"technical"
],
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"Sebastian Becker"
],
[
"kind",
{},
"text",
"individual"
],
[
"adr",
{
"label": "Deutsche Telekom AG\nWolbecker Str. 268, 48155, Muenster, Deutschland"
},
"text",
[
"",
"",
"",
"",
"",
"",
""
]
],
[
"tel",
{
"type": "voice"
},
"text",
"+49 228 18123797"
]
]
]
},
{
"entities": [
{
"handle": "DTAG-NIC",
"links": [
{
"href": "https://rdap.db.ripe.net/entity/DTAG-NIC",
"rel": "self",
"value": "https://rdap.db.ripe.net/autnum/3320"
},
{
"href": "http://www.ripe.net/data-tools/support/documentation/terms",
"rel": "copyright",
"value": "http://www.ripe.net/data-tools/support/documentation/terms"
}
],
"objectClassName": "entity",
"roles": [
"registrant"
],
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"DTAG-NIC"
],
[
"kind",
{},
"text",
"individual"
]
]
]
},
{
"handle": "DTAG1-RIPE",
"links": [
{
"href": "https://rdap.db.ripe.net/entity/DTAG1-RIPE",
"rel": "self",
"value": "https://rdap.db.ripe.net/autnum/3320"
},
{
"href": "http://www.ripe.net/data-tools/support/documentation/terms",
"rel": "copyright",
"value": "http://www.ripe.net/data-tools/support/documentation/terms"
}
],
"objectClassName": "entity",
"roles": [
"administrative",
"technical"
],
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"DTAG Internet Routing Registry"
],
[
"kind",
{},
"text",
"group"
],
[
"adr",
{
"label": "Deutsche Telekom Service GmbH\nInternet Services\nEduard-Schopf-Allee 1\nDE 28217 Bremen"
},
"text",
[
"",
"",
"",
"",
"",
"",
""
]
]
]
]
}
],
"handle": "DTAG3-RIPE",
"objectClassName": "entity",
"roles": [
"abuse"
],
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"Deutsche Telekom LIR Abuse Contact"
],
[
"kind",
{},
"text",
"group"
],
[
"adr",
{
"label": "Deutsche Telekom AG"
},
"text",
[
"",
"",
"",
"",
"",
"",
""
]
],
[
"email",
{
"type": "abuse"
},
"text",
"[email protected]"
]
]
]
}
],
"events": [
{
"eventAction": "registration",
"eventDate": "1970-01-01T00:00:00Z"
},
{
"eventAction": "last changed",
"eventDate": "2020-12-11T15:33:02Z"
}
],
"handle": "AS3320",
"links": [
{
"href": "https://rdap.db.ripe.net/autnums/rirSearch1/rdap-up/AS3320",
"rel": "rdap-up",
"type": "application/rdap+json",
"value": "https://rdap.db.ripe.net/autnum/3320"
},
{
"href": "https://rdap.db.ripe.net/autnums/rirSearch1/rdap-up/AS3320?status=active",
"rel": "rdap-up rdap-active",
"type": "application/rdap+json",
"value": "https://rdap.db.ripe.net/autnum/3320"
},
{
"href": "https://rdap.db.ripe.net/autnums/rirSearch1/rdap-down/AS3320",
"rel": "rdap-down",
"type": "application/rdap+json",
"value": "https://rdap.db.ripe.net/autnum/3320"
},
{
"href": "https://rdap.db.ripe.net/autnums/rirSearch1/rdap-top/AS3320",
"rel": "rdap-top",
"type": "application/rdap+json",
"value": "https://rdap.db.ripe.net/autnum/3320"
},
{
"href": "https://rdap.db.ripe.net/autnums/rirSearch1/rdap-top/AS3320?status=active",
"rel": "rdap-top rdap-active",
"type": "application/rdap+json",
"value": "https://rdap.db.ripe.net/autnum/3320"
},
{
"href": "https://rdap.db.ripe.net/autnums/rirSearch1/rdap-bottom/AS3320",
"rel": "rdap-bottom",
"type": "application/rdap+json",
"value": "https://rdap.db.ripe.net/autnum/3320"
},
{
"href": "https://rdap.db.ripe.net/autnum/3320",
"rel": "self",
"type": "application/rdap+json",
"value": "https://rdap.db.ripe.net/autnum/3320"
},
{
"href": "http://www.ripe.net/data-tools/support/documentation/terms",
"rel": "copyright",
"value": "http://www.ripe.net/data-tools/support/documentation/terms"
}
],
"name": "DTAG",
"notices": [
{
"description": [
"This output has been filtered."
],
"title": "Filtered"
},
{
"description": [
"If you see inaccuracies in the results, please visit:"
],
"links": [
{
"href": "https://www.ripe.net/contact-form?topic=ripe_dbm\u0026show_form=true",
"rel": "inaccuracy-report",
"type": "text/html",
"value": "https://rdap.db.ripe.net/autnum/3320"
}
],
"title": "Whois Inaccuracy Reporting"
},
{
"description": [
"Objects returned came from source",
"RIPE"
],
"title": "Source"
},
{
"description": [
"This is the RIPE Database query service. The objects are in RDAP format."
],
"links": [
{
"href": "http://www.ripe.net/db/support/db-terms-conditions.pdf",
"rel": "terms-of-service",
"type": "application/pdf",
"value": "https://rdap.db.ripe.net/autnum/3320"
}
],
"title": "Terms and Conditions"
}
],
"objectClassName": "autnum",
"port43": "whois.ripe.net",
"rdapConformance": [
"nro_rdap_profile_asn_flat_0",
"rirSearch1",
"autnums",
"cidr0",
"rdap_level_0",
"nro_rdap_profile_0",
"redacted"
],
"redacted": [
{
"method": "removal",
"name": {
"description": "Personal e-mail information"
},
"prePath": "$.entities[?(@.handle=='ORG-DTA2-RIPE')].vcardArray[1][?(@[0]=='e-mail')]",
"reason": {
"description": "Personal data"
}
},
{
"method": "removal",
"name": {
"description": "Personal e-mail information"
},
"prePath": "$.entities[?(@.handle=='SB15220-RIPE')].vcardArray[1][?(@[0]=='e-mail')]",
"reason": {
"description": "Personal data"
}
},
{
"method": "removal",
"name": {
"description": "Personal e-mail information"
},
"prePath": "$.entities[?(@.handle=='DTAG3-RIPE')].vcardArray[1][?(@[0]=='e-mail')]",
"reason": {
"description": "Personal data"
}
}
],
"remarks": [
{
"description": [
"Internet service provider operations",
"peering coordinators for AS3320: \[email protected]\u003e",
"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",
"in any case peers - and any network in the Internet - is free to apply some selective policy (e.g. prefix length based)",
"unfortunately some customers do not provide usable IRR data; we will NOT add to the uncontrolled garbage in the IRR by proxy registering in some database that requires no authorization",
"we advise customers that routes without IRR registration and not covered by AS3320:AS-DTAG may receive less than full support by some of our peer networks and other parts of the Internet",
"============================================================== IPv6 we do/publish essentially the same like for IPv4",
"=============================================================="
]
}
],
"startAutnum": 3320,
"status": [
"active"
]
}Frequently asked questions
What is WHOIS?
WHOIS is a public directory that answers "who is responsible for this?" for domains, IP ranges and ASNs. It lists registration dates, the registrar, nameservers and contacts.
What is RDAP, and how does it differ?
RDAP is the modern replacement for WHOIS. It returns the same records in a structured, consistent format. We query RDAP first and fall back to classic WHOIS text when a registry has not adopted it yet.
What is the difference between a registrar and a registrant?
The registrar is the company you register and manage a domain through, such as xTom or GoDaddy. The registrant is the person or organization that actually holds the domain.
What are nameservers?
Nameservers answer DNS questions for a domain and decide which IP addresses the name resolves to. They also show which DNS provider the domain uses.
What is DNSSEC?
DNSSEC adds cryptographic signatures to DNS answers so they cannot be quietly altered in transit. "Signed" means the domain has it enabled, "unsigned" means it does not.
Why is the contact information redacted?
Privacy laws such as GDPR require registrars to hide most personal details in public records. The abuse contact is usually still shown, so a domain or network can be reported when something goes wrong.