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

AS9317 ·

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

Warning: AS9317 (ITISNET-AS-KR) announces 51 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS9317
HolderITISNET-AS-KR - INHA UNIVERSITY
AllocationAPNIC, South Korea (KR), allocated 1998-06-03
Prefixes (IPv4 / IPv6)51 / 0
RPKI valid0% (0 / 51)
Upstreams and peers3

What to fix

  1. Warning

    No IPv6 prefixes announced.

    Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.

    Fix: Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.

    Open in ASN & BGP prefix lookup

  2. Warning

    10 of 51 announced prefixes have no ROA (RPKI not found): 165.246.0.0/16, 165.246.80.0/22, 165.246.84.0/22, 165.246.88.0/24, 165.246.89.0/24 (+5).

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

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

    165.246.0.0/16 AS9317 max-length /16
    165.246.80.0/22 AS9317 max-length /22
    165.246.84.0/22 AS9317 max-length /22
    165.246.88.0/24 AS9317 max-length /24
    165.246.89.0/24 AS9317 max-length /24
    165.246.101.0/24 AS9317 max-length /24
    165.246.102.0/24 AS9317 max-length /24
    165.246.106.0/24 AS9317 max-length /24
    165.246.107.0/24 AS9317 max-length /24
    165.246.116.0/22 AS9317 max-length /22

    Open in RPKI / ROA validator Guide

  3. Warning

    50 of 51 announced prefixes have no IRR route object: 165.246.224.0/22, 165.246.143.0/24, 165.246.116.0/22, 165.246.223.0/24, 165.246.123.0/24 (+45).

    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 AS9317 in your RIR’s IRR database (or RADB).

    route: 165.246.224.0/22
    origin: AS9317
    
    route: 165.246.143.0/24
    origin: AS9317
    
    route: 165.246.116.0/22
    origin: AS9317

    Open in ASN & BGP prefix lookup

  4. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS9317 announces 51 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 10 of 51 announced prefixes have no ROA (RPKI not found): 165.246.0.0/16, 165.246.80.0/22, 165.246.84.0/22, 165.246.88.0/24, 165.246.89.0/24 (+5).
  • Info: The RPKI state of 41 prefixes was not looked up (no ROA of AS9317 covers them; only the first 10 are checked).
  • Warning: 50 of 51 announced prefixes have no IRR route object: 165.246.224.0/22, 165.246.143.0/24, 165.246.116.0/22, 165.246.223.0/24, 165.246.123.0/24 (+45).
  • Info: 3 upstreams and peers, 0 downstream networks seen.
HolderITISNET-AS-KR - INHA UNIVERSITY
IPv4 prefixes51
IPv6 prefixes0
RPKI10 not found · 41 not looked up
Without IRR route object50
Downstream networks0
Routes to fix

Upstreams and peers seen to the left 3

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

Open in ASN & BGP prefix lookup
Registration Found at rdap.apnic.net.
  • Pass: Found at rdap.apnic.net.
NameITISNET-AS-KR
HandleAS9317
RangeAS9317
CountryKR
Statusactive
Abuse contacthostmaster@nic.or.kr
Allocation
Registry (RIR)APNIC
CountrySouth Korea (KR)
Delegated on1998-06-03
StatusAllocated
Delegated rangeAS9316 – AS9323

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

Contacts
RoleNameEmail
abuse IRT-KRNIC-KR hostmaster@nic.or.kr
technical AS Manager netadm@inha.ac.kr
administrative AS Manager netadm@inha.ac.kr

Source: https://rdap.apnic.net/autnum/9317. Registration data from rdap.apnic.net, shown under its terms of use (terms): not for marketing or bulk collection.

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