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.203.64.0/22 ·

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

Warning: 91.203.64.0/22 is announced by AS44895 (ANTENNA-GARANT-AS). 3 warnings

Announced as91.203.64.0/22
Origin ASAS44895 ANTENNA-GARANT-AS
HolderMTS-RYAZAN-FIX
AllocationRIPE NCC, Russia (RU), assigned 2008-03-27
Size1,024 addresses
Abuse contactabuse@mtu.ru

What to fix

  1. Warning

    91.203.64.0/22 from AS44895 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 AS44895 and a max length equal to the prefix length.

    prefix: 91.203.64.0/22
    origin: AS44895
    max-length: 22

    Open in RPKI / ROA validator Guide

  2. Warning

    91.203.65.0/24 from AS44895 is RPKI not found: no ROA covers it. 91.203.65.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 AS44895 and a max length equal to the prefix length.

    prefix: 91.203.65.0/24
    origin: AS44895
    max-length: 24

    Open in RPKI / ROA validator Guide

  3. Warning

    91.203.66.0/24 from AS44895 is RPKI not found: no ROA covers it. 91.203.66.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 AS44895 and a max length equal to the prefix length.

    prefix: 91.203.66.0/24
    origin: AS44895
    max-length: 24

    Open in RPKI / ROA validator Guide

Checks

Routing and RPKI 91.203.64.0/22 from AS44895 is RPKI not found: no ROA covers it.
  • Pass: Announced as 91.203.64.0/22 by AS44895.
  • Warning: 91.203.64.0/22 from AS44895 is RPKI not found: no ROA covers it.
  • Warning: 91.203.65.0/24 from AS44895 is RPKI not found: no ROA covers it. 91.203.65.0/24
  • Warning: 91.203.66.0/24 from AS44895 is RPKI not found: no ROA covers it. 91.203.66.0/24
  • Pass: Seen by 100% of RIPE RIS peers.
Route91.203.64.0/22
Origin ASAS44895 ANTENNA-GARANT-AS MTS PJSC No ROA
IRR route objectsRIPE
Visibility (RIS peers)320 / 321
First seen2008-04-11
More-specific routes 2
More-specific routeOrigin ASRPKI
91.203.65.0/24 AS44895 No ROA
91.203.66.0/24 AS44895 No ROA

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse DNS Reverse DNS is delegated for all 4 zones checked.
  • Pass: Reverse DNS is delegated for all 4 zones checked.
Reverse zones 4
ZoneNameservers
64.203.91.in-addr.arpa dns0.mts.ru, dns1.mts.ru, dns1.mtu.ru, dns2.mts-ws.net
65.203.91.in-addr.arpa dns0.mts.ru, dns1.mts.ru, dns1.mtu.ru, dns2.mts-ws.net
66.203.91.in-addr.arpa dns0.mts.ru, dns1.mts.ru, dns1.mtu.ru, dns2.mts-ws.net
67.203.91.in-addr.arpa dns0.mts.ru, dns1.mts.ru, dns1.mtu.ru, dns2.mts-ws.net
Open in DNS lookup
Registration Found at rdap.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
NameMTS-RYAZAN-NETWORK-2
Handle91.203.64.0 - 91.203.67.255
Range91.203.64.0 – 91.203.67.255
CountryRU
Statusactive
Registered2008-03-27T09:29:50Z
Last changed2018-10-11T09:22:18Z
Abuse contactabuse@mtu.ru
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2008-03-27
StatusAssigned
Delegated range91.203.64.0/22 (91.203.64.0 – 91.203.67.255)

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

Contacts
RoleNameEmail
registrant MTS-RYAZAN-FIX
registrant MTU-NOC
registrant MTS PJSC
registrant RIPE-NCC-END-MNT
abuse MTU Abuse-c Bender abuse@mtu.ru

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