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.
Checking routing, RPKI, reverse DNS, blocklists and the registry. This usually takes 3 to 10 seconds.
91.203.64.0/22 ·
Warning: 91.203.64.0/22 is announced by AS44895 (ANTENNA-GARANT-AS). 3 warnings
| Announced as | 91.203.64.0/22 |
|---|---|
| Origin AS | AS44895 ANTENNA-GARANT-AS |
| Holder | MTS-RYAZAN-FIX |
| Allocation | RIPE NCC, Russia (RU), assigned 2008-03-27 |
| Size | 1,024 addresses |
| Abuse contact | abuse@mtu.ru |
What to fix
-
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
-
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
-
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
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.
| Route | 91.203.64.0/22 |
|---|---|
| Origin AS | AS44895 ANTENNA-GARANT-AS MTS PJSC No ROA |
| IRR route objects | RIPE |
| Visibility (RIS peers) | 320 / 321 |
| First seen | 2008-04-11 |
| More-specific route | Origin AS | RPKI |
|---|---|---|
| 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 lookupReverse DNS Reverse DNS is delegated for all 4 zones checked.
- Pass: Reverse DNS is delegated for all 4 zones checked.
| Zone | Nameservers |
|---|---|
| 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 |
Registration Found at rdap.db.ripe.net.
- Pass: Found at rdap.db.ripe.net.
| Name | MTS-RYAZAN-NETWORK-2 |
|---|---|
| Handle | 91.203.64.0 - 91.203.67.255 |
| Range | 91.203.64.0 – 91.203.67.255 |
| Country | RU |
| Status | active |
| Registered | 2008-03-27T09:29:50Z |
| Last changed | 2018-10-11T09:22:18Z |
| Abuse contact | abuse@mtu.ru |
| Registry (RIR) | RIPE NCC |
|---|---|
| Country | Russia (RU) |
| Delegated on | 2008-03-27 |
| Status | Assigned |
| Delegated range | 91.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.
| Role | Name | |
|---|---|---|
| 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 lookupPeeringDB 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