Whois: Deutsche Telekom AG
| Hosting Company: | Deutsche Telekom AG  |
| Hosting ASN: | AS3320 |
| Hosting Address: | Group Information Security, SDA/Abuse,Deutsche Telekom Allee 9,DE 64295 Darmstadt,Deutsche Telekom AG,Darmstadt, Germany,Deutsche Telekom AG,Darmstadt, Germany, |
| Hosting Country: |  Germany, Darmstadt |
Deutsche Telekom AG ip ranges
| # | Range | CDIR | Ip count | Name | Location |
|---|---|---|---|---|---|
| 1 | 46.250.224.0 - 46.250.239.255 | 46.250.232.0/21 | 4,096 | YorkshireTech |  United Kingdom |
| 2 | 62.153.249.112 - 62.153.249.127 | 62.153.0.0/16 | 16 | ITM-SYSTEMS-GESCHER-NET | Germany |
| 3 | 62.154.222.208 - 62.154.222.215 | 62.154.0.0/15 | 8 | KLINKHAMMER-NUERNBERG-NET | Germany |
| 4 | 62.157.185.0 - 62.157.185.127 | 62.156.0.0/14 | 128 | VRG-OLDENBURG-NET | Germany |
| 5 | 79.192.0.0 - 79.244.191.255 | 79.192.0.0/10 | 3,457,024 | DTAG-DIAL24 | Germany, Darmstadt |
| 6 | 79.245.0.0 - 79.247.255.255 | 79.192.0.0/10 | 197,608 | DTAG-DIAL25 | Germany |
| 7 | 80.128.0.0 - 80.146.159.255 | 80.128.0.0/12 | 1,221,608 | DTAG-DIAL16 | Germany, Darmstadt |
| 8 | 80.152.128.0 - 80.153.255.255 | 80.152.0.0/14 | 98,304 | DTAG-STATIC04 | Germany |
| 9 | 80.156.226.64 - 80.156.226.95 | 80.156.0.0/16 | 32 | KURT-PIETSCH-AHAUS-NET | Germany |
| 10 | 84.128.0.0 - 84.135.255.255 | 84.128.0.0/10 | 524,288 | DTAG-DIAL19 | Germany, Darmstadt |
| 11 | 84.136.0.0 - 84.191.255.255 | 84.128.0.0/10 | 4,670,016 | DTAG-DIAL20 | Germany |
| 12 | 87.128.0.0 - 87.128.127.255 | 87.128.0.0/11 | 33,768 | DTAG-STATIC10 | Germany |
| 13 | 87.130.99.176 - 87.130.99.183 | 87.128.0.0/11 | 8 | THM-LEINEFELDEWORBIS-NET | Germany |
| 14 | 87.138.128.0 - 87.138.191.255 | 87.128.0.0/11 | 16,384 | DTAG-STATIC08 | Germany |
| 15 | 87.139.0.0 - 87.139.127.255 | 87.128.0.0/11 | 33,768 | DTAG-STATIC02 | Germany |
| 16 | 87.140.0.0 - 87.140.127.255 | 87.128.0.0/11 | 33,768 | DTAG-STATIC12 | Germany |
| 17 | 87.141.224.0 - 87.159.255.255 | 87.128.0.0/11 | 1,188,840 | DTAG-DIAL26 | Germany |
| 18 | 87.160.0.0 - 87.186.159.255 | 87.128.0.0/10 | 2,745,896 | DTAG-DIAL21 | Germany |
| 19 | 87.190.10.144 - 87.190.10.151 | 87.128.0.0/10 | 8 | PREMIER-INN-BERLIN-NET | Germany |
| 20 | 87.190.10.208 - 87.190.10.215 | 87.128.0.0/10 | 8 | UNI-KLINIK-GIESSEN-NET | Germany |
Deutsche Telekom AG domains (0 total)
| # | Name | IP | Rank | Updated |
|---|---|---|---|---|
| No results |
Deutsche Telekom AG users
| # | IP | OS | Browser | Updated |
|---|---|---|---|---|
| 1 | 2003:cf:f40:5a00:a54d:e5fb:140e:386a |  Windows 10 |
 Chrome 130.0 |
Last seen: 11.11.2024 |
| 2 | 87.191.47.214 |  Android |
Chrome 130.0 for Android |
Last seen: 03.11.2024 |
| 3 | 2003:d7:2717:f19d:3d64:966a:2eae:f5e1 | Windows 10 |
Chrome 130.0 |
Last seen: 02.11.2024 |
| 4 | 91.0.238.71 | Windows 10 |
Chrome 130.0 |
Last seen: 29.10.2024 |
| 5 | 2003:fb:ef21:cc10:b09c:b204:cd93:8e6f |  Linux |
Chrome 130.0 |
Last seen: 28.10.2024 |
| 6 | 2003:c5:bf11:b000:4c64:ae92:fc3d:9563 | Windows 10 |
 Opera 114 |
Last seen: 24.10.2024 |
| 7 | 2003:c0:9f10:766a:91:ebc8:bb0d:24de | Windows 10 |
Chrome 129.0 |
Last seen: 18.10.2024 |
| 8 | 2003:c8:972c:2513:a107:801d:2ce5:6c15 |  iPhone |
Chrome 129.0 for iOS |
Last seen: 15.10.2024 |
| 9 | 2003:ca:7f38:bb00:b1a6:a77c:7883:c6ed | Windows 10 |
 Firefox 131.0 |
Last seen: 07.10.2024 |
| 10 | 2003:c7:7704:ea2e:93e0:326:1f6d:6428 | Android |
Chrome 129.0 for Android |
Last seen: 05.10.2024 |
| 11 | 80.130.83.74 | Windows 10 |
Chrome 129.0 |
Last seen: 30.09.2024 |
| 12 | 62.154.222.211 | Windows 10 |
Opera 113 |
Last seen: 24.09.2024 |
| 13 | 2003:f7:5f0d:6e00:1dbb:5053:e0b0:e5e7 | Windows 10 |
Firefox 130.0 |
Last seen: 16.09.2024 |
| 14 | 91.6.160.6 | Linux |
Firefox 115.0 |
Last seen: 15.09.2024 |
| 15 | 79.235.186.153 | Windows 10 |
Firefox 130.0 |
Last seen: 11.09.2024 |
| 16 | 2003:f8:c711:9800:c43b:7848:c99:bb62 | Windows 10 |
Firefox 130.0 |
Last seen: 09.09.2024 |
| 17 | 2003:c5:670b:96a:c414:74c1:7c22:1aaf | Windows 10 |
Firefox 130.0 |
Last seen: 07.09.2024 |
| 18 | 2003:c4:ff40:1600:a8f:73c6:d9a3:fcf2 | Linux |
Firefox 115.0 |
Last seen: 07.09.2024 |
| 19 | 2003:c5:3f18:d712:d5e9:f10e:6689:ae4a | Windows 10 |
Chrome 128.0 |
Last seen: 06.09.2024 |
| 20 | 2003:c2:4705:db00:8173:bfda:6588:b708 | Android |
Chrome 128.0 for Android |
Last seen: 05.09.2024 |
Whois AS3320
| info | % This is the RIPE Database query service.% The objects are in RPSL format.%% The RIPE Database is subject to Terms and Conditions.% To receive output for a database update, use the "-B" flag.% Information related to 'AS3209 - AS3353'% Information related to 'AS3320'% Abuse contact for 'AS3320' is '[email protected]'% This query was served by the RIPE Database Query Service version 1.103 (HEREFORD) |
| % See http | //www.ripe.net/db/support/db-terms-conditions.pdf |
| % Note | this output has been filtered. |
| as-block | AS3209 - AS3353 |
| descr | RIPE NCC ASN block Internet service provider operations |
| remarks | These AS Numbers are assigned to network operators in the RIPE NCC service region. peering coordinators for AS3320: 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 are providing that by means of the AS-set AS3320:AS-DTAG which we have been keeping up to date all the time 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 # 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... 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) # 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 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 ============================================================== |
| mnt-by | RIPE-NCC-HM-MNT RIPE-NCC-END-MNT DTAG-RR RIPE-NCC-HM-MNT DTAG-NIC DTAG-NIC DTAG-RR |
| created | 2018-11-22T15:27:19Z 1970-01-01T00:00:00Z 2004-04-17T11:12:44Z 2011-11-01T16:24:28Z |
| last-modified | 2018-11-22T15:27:19Z 2020-12-11T15:33:02Z 2022-05-06T07:50:31Z 2020-03-20T12:56:13Z |
| source | RIPE RIPE RIPE # Filtered RIPE # Filtered |
| aut-num | AS3320 |
| as-name | DTAG |
| org | ORG-DTA2-RIPE |
| import | from AS-ANY accept ANY # heavy abstraction hits! well, we are ... neither peering promiscuously nor accepting all junk routes offered... |
| export | to AS3320:AS-CUSTOMERS announce ANY # but don't publish that list; in general - if they ask for less, we can do 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 |
| 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 afi ipv6.unicast to AS-ANY announce AS3320:AS-DTAG-V6 # for peers and others... |
| admin-c | SB15220-RIPE DTAG-RIPE UR661-RIPE SL7866-RIPE VZ56-RIPE REIS1-RIPE EH4097-RIPE MBT1-RIPE LB470-RIPE SB15220-RIPE SB15220-RIPE KUNO2-RIPE HB3076-RIPE LF1459-RIPE KB6787-RIPE CP12467-RIPE DS22814-RIPE ILKA2-RIPE SL13187-RIPE JS21561-RIPE |
| tech-c | SB15220-RIPE |
| status | ASSIGNED |
| organisation | ORG-DTA2-RIPE |
| org-name | Deutsche Telekom AG |
| country | DE |
| org-type | LIR |
| address | Eduard-Schopf-Allee 1 D-28217 Bremen GERMANY Deutsche Telekom AG Gartenstrasse 217 DE 48147 Muenster Germany |
| phone | +4942151555165 +49 228 18123797 |
| fax-no | +494412344589 +49391580100379 |
| abuse-c | DTAG3-RIPE |
| mnt-ref | RIPE-NCC-HM-MNT DTAG-NIC |
| person | Sebastian Becker |
| nic-hdl | SB15220-RIPE |
