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

91.217.58.0/23 ·

curl -s "https://thenetworkery.com/api/v1/network-report?query=91.217.58.0%2F23"
JSON Docs

Warning: 91.217.58.0/23 is announced by AS197251 (TEREWENKO-AS), AS6 (BULL-HN). 6 warnings

Announced as91.217.58.0/23
Origin ASAS197251 TEREWENKO-AS AS6 BULL-HN
HolderMNT-TEREWENKO
AllocationRIPE NCC, Ukraine (UA), assigned 2010-08-30
Size512 addresses
Abuse contactroot@klad.zp.ua

What to fix

  1. Warning

    More than one origin AS (MOAS).

    Sometimes intended (anycast, DDoS scrubbing), sometimes a hijack or leak. Check the origins are all yours.

    Open in ASN & BGP prefix lookup

  2. Warning

    91.217.58.0/23 from AS197251 is RPKI not found: no ROA covers it.

    Routes without a ROA are still accepted almost everywhere, but nothing protects them from a hijack.

    Fix: Create a ROA for this prefix with origin AS197251 and a max length equal to the prefix length.

    prefix: 91.217.58.0/23
    origin: AS197251
    max-length: 23

    Open in RPKI / ROA validator Guide

  3. Warning

    91.217.58.0/23 from AS6 is RPKI not found: no ROA covers it.

    Routes without a ROA are still accepted almost everywhere, but nothing protects them from a hijack.

    Fix: Create a ROA for this prefix with origin AS6 and a max length equal to the prefix length.

    prefix: 91.217.58.0/23
    origin: AS6
    max-length: 23

    Open in RPKI / ROA validator Guide

  4. Warning

    91.217.58.0/24 from AS197251 is RPKI not found: no ROA covers it. 91.217.58.0/24

    Routes without a ROA are still accepted almost everywhere, but nothing protects them from a hijack.

    Fix: Create a ROA for this prefix with origin AS197251 and a max length equal to the prefix length.

    prefix: 91.217.58.0/24
    origin: AS197251
    max-length: 24

    Open in RPKI / ROA validator Guide

  5. Warning

    91.217.59.0/24 from AS197251 is RPKI not found: no ROA covers it. 91.217.59.0/24

    Routes without a ROA are still accepted almost everywhere, but nothing protects them from a hijack.

    Fix: Create a ROA for this prefix with origin AS197251 and a max length equal to the prefix length.

    prefix: 91.217.59.0/24
    origin: AS197251
    max-length: 24

    Open in RPKI / ROA validator Guide

  6. Warning

    No IRR route object for 91.217.58.0/23 with origin AS6.

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

    Fix: Create a route object in your RIR’s IRR database (or RADB):

    route: 91.217.58.0/23
    origin: AS6

    Open in ASN & BGP prefix lookup

Checks

Routing and RPKI More than one origin AS (MOAS).
  • Pass: Announced as 91.217.58.0/23 by AS197251, AS6.
  • Warning: More than one origin AS (MOAS).
  • Warning: 91.217.58.0/23 from AS197251 is RPKI not found: no ROA covers it.
  • Warning: 91.217.58.0/23 from AS6 is RPKI not found: no ROA covers it.
  • Warning: 91.217.58.0/24 from AS197251 is RPKI not found: no ROA covers it. 91.217.58.0/24
  • Warning: 91.217.59.0/24 from AS197251 is RPKI not found: no ROA covers it. 91.217.59.0/24
  • Warning: No IRR route object for 91.217.58.0/23 with origin AS6.
  • Pass: Seen by 100% of RIPE RIS peers.
Route91.217.58.0/23
Origin ASAS197251 TEREWENKO-AS FOP TERESHCHENKO OLEKSANDR TROHUMOVICH No ROAAS6 BULL-HN - ATOS IT Solutions and Services, Inc. No ROA
IRR route objectsRIPE
Visibility (RIS peers)318 / 319
First seen2010-09-07
More-specific routes 2
More-specific routeOrigin ASRPKI
91.217.58.0/24 AS197251 No ROA
91.217.59.0/24 AS197251 No ROA

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse DNS Reverse DNS is delegated for all 2 zones checked.
  • Pass: Reverse DNS is delegated for all 2 zones checked.
Reverse zones 2
ZoneNameservers
58.217.91.in-addr.arpa ns.secondary.net.ua, ns2.klad.zp.ua
59.217.91.in-addr.arpa ns.secondary.net.ua, ns2.klad.zp.ua
Open in DNS lookup
Registration Found at rdap.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
NameAS-TEREWENKO
Handle91.217.58.0 - 91.217.59.255
Range91.217.58.0 – 91.217.59.255
CountryUA
Statusactive
Registered2010-08-30T15:53:37Z
Last changed2016-04-14T10:31:24Z
Abuse contactroot@klad.zp.ua
Allocation
Registry (RIR)RIPE NCC
CountryUkraine (UA)
Delegated on2010-08-30
StatusAssigned
Delegated range91.217.58.0/23 (91.217.58.0 – 91.217.59.255)

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

Contacts
RoleNameEmail
registrant MNT-TEREWENKO
registrant FOP TERESHCHENKO OLEKSANDR TROHUMOVICH
registrant RIPE-NCC-END-MNT
abuse KLAD.zp.ua administrator root@klad.zp.ua

Source: https://rdap.db.ripe.net/ip/91.217.58.0/23. 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

About the network that announces this space, so not in the fix list.

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup