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

AS8794 ·

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

Warning: AS8794 (FAZ) announces 2 IPv4 and 1 IPv6 prefixes. 3 warnings

AS pageAS8794
HolderFAZ Frankfurter Allgemeine Zeitung GmbH
AllocationRIPE NCC, Germany (DE), allocated 1998-05-26
Prefixes (IPv4 / IPv6)2 / 1
RPKI valid0% (0 / 3)
Upstreams and peers2

What to fix

  1. Warning

    3 of 3 announced prefixes have no ROA (RPKI not found): 193.227.144.0/20, 193.227.159.0/24, 2001:678:b78::/48.

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

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

    193.227.144.0/20 AS8794 max-length /20
    193.227.159.0/24 AS8794 max-length /24
    2001:678:b78::/48 AS8794 max-length /48

    Open in RPKI / ROA validator Guide

  2. Warning

    1 of 3 announced prefixes have no IRR route object: 193.227.159.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 AS8794 in your RIR’s IRR database (or RADB).

    route: 193.227.159.0/24
    origin: AS8794

    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 3 of 3 announced prefixes have no ROA (RPKI not found): 193.227.144.0/20, 193.227.159.0/24, 2001:678:b78::/48.
  • Pass: AS8794 announces 2 IPv4 and 1 IPv6 prefixes.
  • Warning: 3 of 3 announced prefixes have no ROA (RPKI not found): 193.227.144.0/20, 193.227.159.0/24, 2001:678:b78::/48.
  • Warning: 1 of 3 announced prefixes have no IRR route object: 193.227.159.0/24.
  • Info: 2 upstreams and peers, 0 downstream networks seen.
HolderFAZ Frankfurter Allgemeine Zeitung GmbH
IPv4 prefixes2
IPv6 prefixes1
RPKI3 not found
Without IRR route object1
Downstream networks0
Routes to fix
PrefixRPKI
193.227.144.0/20 No ROA
193.227.159.0/24 No ROA
2001:678:b78::/48 No ROA

Upstreams and peers seen to the left 2

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.
NameFAZ
HandleAS8794
RangeAS8794
Statusactive
Registered2002-04-11T08:21:09Z
Last changed2018-12-11T12:47:19Z
Abuse contactm.gottfried@faz.de
Allocation
Registry (RIR)RIPE NCC
CountryGermany (DE)
Delegated on1998-05-26
StatusAllocated
Delegated rangeAS8794

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

Contacts
RoleNameEmail
registrant LNC-MNT
registrant Frankfurter Allgemeine Zeitung GmbH
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role m.gottfried@faz.de

Source: https://rdap.db.ripe.net/autnum/8794. 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