Seen 15317 times between November 30th, 2016 and January 26th, 2020.

General Info

Geo Germany (DE) —
AS AS3320 - DTAG Internet service provider operations, DE
Note: An IP might be announced by multiple ASs. This is not shown.
Registrar RIPENCC

Recent Screenshots

Direct hits
Summary of pages hosted on this ASN

IPs | 2265x 2003:2:2:15:80:150:6:143 | 1659x | 516x | 425x 2003:2:2:15:80:150:6:138 | 342x | 186x | 70x | 62x | 53x | 51x

Domains | 540x | 516x | 425x | 345x | 186x | 143x | 134x | 125x | 88x | 88x

Recent scans (9110 total) Show all

URL Submitted 2 hours ago 2 hours ago 2 hours ago 2 hours ago 2 hours ago

Incoming hits
Summary of pages that talked to this ASN

ASNs AS12665 | 1410x AS15598 | 953x AS21069 | 483x AS13335 | 408x AS46606 | 225x AS20013 | 219x AS61157 | 203x AS24940 | 169x AS34086 | 122x AS26496 | 96x

IPs | 1408x | 945x | 483x | 120x 2606:4700::6810:a1e3 | 110x 2606:4700::6810:a0e3 | 94x | 93x 2a02:cbf7:1:0:62:138:239:100 | 77x 2a02:cbf7::62:138:238:100 | 69x | 68x

Domains | 1408x | 945x | 483x | 204x | 178x | 96x | 75x | 68x | 65x | 56x

Countries DE | 3090x US | 1520x CH | 486x FI | 104x GB | 104x NL | 91x RU | 82x IN | 75x AU | 70x CA | 47x

Recent scans (6207 total) Show all

URL Submitted 16 hours ago 2 days ago 2 days ago 2 days ago 2 days ago

Recent screenshots
Screenshots of pages hosted on this ASN

Related infrastructure
Summary of infrastructure which pages hosted on this ASN frequently talked to

ASNs AS3320 | 9110x AS15169 | 2744x AS20940 | 1811x AS14413 | 1657x AS32934 | 1602x AS16509 | 917x AS13335 | 262x AS20446 | 242x AS15133 | 202x AS54113 | 193x AS16625 | 175x AS13414 | 174x AS8068 | 171x AS54825 | 138x AS24940 | 133x AS13238 | 126x AS12731 | 125x AS60955 | 84x AS196819 | 83x AS6724 | 81x

IPs | 2265x 2003:2:2:15:80:150:6:143 | 1683x 2a03:2880:f21c:81c4:face:b00c:0:43fe | 1374x 2a05:f500:10:101::b93f:9105 | 964x 2a05:f500:10:101::b93f:9101 | 940x 2a00:1450:4001:806::2008 | 914x 2a00:1450:4001:808::200e | 729x 2a05:f500:11:101::b93f:9005 | 676x 2a00:1450:4001:808::2008 | 605x 2a05:f500:11:101::b93f:9001 | 573x 2a00:1450:4001:821::200e | 527x | 516x 2a02:26f0:6c00:2bf::3adf | 500x 2a02:26f0:6c00:293::3adf | 427x | 425x 2003:2:2:15:80:150:6:138 | 345x 2a02:26f0:10c:399::3adf | 326x 2a02:26f0:10c:38f::3adf | 310x 2003:2:2:15:80:150:6:190 | 301x 2a00:1450:4001:81b::200e | 211x

Domains | 2238x | 2063x | 1913x | 1663x | 1654x | 1617x | 1476x | 857x | 786x | 711x | 540x | 516x | 509x | 433x | 425x | 409x | 398x | 397x | 345x | 314x

Related screenshots
Screenshots of pages that talked to this ASN

WHOIS for AS3320

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

aut-num:        AS3320
as-name:        DTAG
org:            ORG-DTA2-RIPE
descr:          Internet service provider operations
remarks:        peering coordinators for AS3320:  <>
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)

                from AS-ANY # neither peering promiscuously
                accept ANY # 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...

                announce ANY # in general - if they ask for less, we can do

                announce AS3320:AS-DTAG
                #   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
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

                from AS-ANY # neither peering promiscuously
                accept ANY # nor accepting all junk routes offered...

                to   AS3320:AS-CUSTOMERS-V6 # but don't publish that list;
                announce ANY # in general - if they ask for less, we can do

                to   AS-ANY   # for peers and others...
                announce AS3320:AS-DTAG-V6
remarks:        ==============================================================
admin-c:        RV32
tech-c:         RV32
status:         ASSIGNED
mnt-by:         RIPE-NCC-END-MNT
tech-c:         BP32-RIPE
mnt-by:         DTAG-RR
created:        1970-01-01T00:00:00Z
last-modified:  2017-11-15T09:13:45Z
source:         RIPE

organisation:   ORG-DTA2-RIPE
org-name:       Deutsche Telekom AG
org-type:       LIR
address:        Eduard-Schopf-Allee 1
address:        D-28217
address:        Bremen
address:        GERMANY
phone:          +4942151555165
fax-no:         +494412344589
admin-c:        DTAG-RIPE
admin-c:        UR661-RIPE
admin-c:        SL7866-RIPE
admin-c:        VZ56-RIPE
admin-c:        REIS1-RIPE
admin-c:        HI56-RIPE
admin-c:        EH4097-RIPE
admin-c:        MBT1-RIPE
admin-c:        BP32-RIPE
admin-c:        LB470-RIPE
admin-c:        RV32
admin-c:        SB15220-RIPE
admin-c:        KUNO2-RIPE
admin-c:        HB3076-RIPE
admin-c:        LF1459-RIPE
admin-c:        KB6787-RIPE
admin-c:        CP12467-RIPE
admin-c:        DS22814-RIPE
admin-c:        ILKA2-RIPE
admin-c:        SL13187-RIPE
admin-c:        JS21561-RIPE
admin-c:        IRIS3-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:  2019-12-02T11:41:14Z
source:         RIPE # Filtered

person:         Berthold Paffrath
address:        Deutsche Telekom AG, Internet Services
address:        Postfach 2767
address:        D-48014 Muenster
phone:          +49 251 910 351
fax-no:         +49 251 910 399
nic-hdl:        BP32-RIPE
mnt-by:         DTAG-RR
created:        1970-01-01T00:00:00Z
last-modified:  2001-09-21T23:34:28Z
source:         RIPE # Filtered

person:         Ruediger Volk
address:        Deutsche Telekom AG, Zentrum IOT
address:        Postfach 2767
address:        D-48014 Muenster
phone:          +49 251 910 351
fax-no:         +49 251 910 399
nic-hdl:        RV32
mnt-by:         DTAG-RR
created:        1970-01-01T00:00:00Z
last-modified:  2001-09-21T23:34:30Z
source:         RIPE # Filtered

Debug — Elasticsearch took 1385ms + 644ms