Skip to content
thenetworkery

Network report

Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.

IP address, prefix or AS number

AS50642 · 

curl -s "https://thenetworkery.com/api/v1/network-report?query=AS50642"
JSON Docs

Warning: AS50642 (DNCC DNCC GmbH) announces 3 IPv4 and 1 IPv6 prefixes. 3 warnings

AS pageAS50642
HolderDNCC DNCC GmbH
AllocationRIPE NCC, Germany (DE), allocated 2016-01-15
Prefixes (IPv4 / IPv6)3 / 1
RPKI valid0% (0 / 4)
Upstreams and peers1

What to fix

  1. Warning

    4 of 4 announced prefixes have no ROA (RPKI not found): 185.134.44.0/22, 185.134.46.0/24, 185.134.47.0/24, 2a06:ed00::/29.

    Without a ROA, networks cannot tell your routes from a hijack.

    Fix: Create a ROA for each at your RIR portal, with origin AS50642 and a max length equal to the prefix length:

    185.134.44.0/22 AS50642 max-length /22
185.134.46.0/24 AS50642 max-length /24
185.134.47.0/24 AS50642 max-length /24
2a06:ed00::/29 AS50642 max-length /29

    Open in RPKI / ROA validator Guide

  2. Warning

    2 of 4 announced prefixes have no IRR route object: 185.134.47.0/24, 185.134.46.0/24.

    Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.

    Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS50642 in your RIR’s IRR database (or RADB).

    route: 185.134.47.0/24
origin: AS50642

route: 185.134.46.0/24
origin: AS50642

    Open in ASN & BGP prefix lookup

  3. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI 4 of 4 announced prefixes have no ROA (RPKI not found): 185.134.44.0/22, 185.134.46.0/24, 185.134.47.0/24, 2a06:ed00::/29.
  • Pass: AS50642 announces 3 IPv4 and 1 IPv6 prefixes.
  • Warning: 4 of 4 announced prefixes have no ROA (RPKI not found): 185.134.44.0/22, 185.134.46.0/24, 185.134.47.0/24, 2a06:ed00::/29.
  • Warning: 2 of 4 announced prefixes have no IRR route object: 185.134.47.0/24, 185.134.46.0/24.
  • Info: One upstream or peer seen (AS28876): an outage there takes the whole network off the internet.
HolderDNCC DNCC GmbH
IPv4 prefixes3
IPv6 prefixes1
RPKI4 not found
Without IRR route object2
Downstream networks1
Routes to fix
PrefixRPKI
185.134.44.0/22 No ROA
185.134.46.0/24 No ROA
185.134.47.0/24 No ROA
2a06:ed00::/29 No ROA

Upstreams and peers seen to the left 1

AS28876 suec//dacor GmbH

Announced prefixes 4

185.134.44.0/22 185.134.46.0/24 185.134.47.0/24 2a06:ed00::/29

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration Found at rdap.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
NameDNCC
HandleAS50642
RangeAS50642
Statusactive
Registered2016-01-15T11:28:12Z
Last changed2018-09-04T11:43:55Z
Abuse contactjs@dncc.de
Allocation
Registry (RIR)RIPE NCC
CountryGermany (DE)
Delegated on2016-01-15
StatusAllocated
Delegated rangeAS50642

Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.

Contacts
RoleNameEmail
registrant de-datanetworks-1-mnt
registrant DNCC GmbH
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role js@dncc.de

Source: https://rdap.db.ripe.net/autnum/50642. Registration data from rdap.db.ripe.net, shown under its terms of use (terms): not for marketing or bulk collection. Personal contacts in this registry are not shown.

Open in WHOIS / RDAP lookup
PeeringDB PeeringDB did not answer: HTTP 404
  • Warning: PeeringDB did not answer: HTTP 404

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup