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

58.224.0.0/12 ·

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

Warning: 58.224.0.0/12 is announced by AS9318 (SKB-AS-KR). 11 warnings

Announced as58.224.0.0/12
Origin ASAS9318 SKB-AS-KR
HolderbroadNnet-KR
AllocationAPNIC, South Korea (KR), allocated 2005-06-27
Size1,048,576 addresses
Abuse contacthostmaster@nic.or.kr

What to fix

  1. Warning

    58.224.0.0/12 from AS9318 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 AS9318 and a max length equal to the prefix length.

    prefix: 58.224.0.0/12
    origin: AS9318
    max-length: 12

    Open in RPKI / ROA validator Guide

  2. Warning

    58.224.0.0/13 from AS9318 is RPKI not found: no ROA covers it. 58.224.0.0/13

    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 AS9318 and a max length equal to the prefix length.

    prefix: 58.224.0.0/13
    origin: AS9318
    max-length: 13

    Open in RPKI / ROA validator Guide

  3. Warning

    58.232.0.0/13 from AS9318 is RPKI not found: no ROA covers it. 58.232.0.0/13

    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 AS9318 and a max length equal to the prefix length.

    prefix: 58.232.0.0/13
    origin: AS9318
    max-length: 13

    Open in RPKI / ROA validator Guide

  4. Warning

    58.224.62.0/23 from AS9318 is RPKI not found: no ROA covers it. 58.224.62.0/23

    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 AS9318 and a max length equal to the prefix length.

    prefix: 58.224.62.0/23
    origin: AS9318
    max-length: 23

    Open in RPKI / ROA validator Guide

  5. Warning

    58.225.68.0/23 from AS9318 is RPKI not found: no ROA covers it. 58.225.68.0/23

    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 AS9318 and a max length equal to the prefix length.

    prefix: 58.225.68.0/23
    origin: AS9318
    max-length: 23

    Open in RPKI / ROA validator Guide

  6. Warning

    58.226.180.0/23 from AS9318 is RPKI not found: no ROA covers it. 58.226.180.0/23

    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 AS9318 and a max length equal to the prefix length.

    prefix: 58.226.180.0/23
    origin: AS9318
    max-length: 23

    Open in RPKI / ROA validator Guide

  7. Warning

    58.227.2.0/23 from AS9318 is RPKI not found: no ROA covers it. 58.227.2.0/23

    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 AS9318 and a max length equal to the prefix length.

    prefix: 58.227.2.0/23
    origin: AS9318
    max-length: 23

    Open in RPKI / ROA validator Guide

  8. Warning

    58.227.216.0/23 from AS9318 is RPKI not found: no ROA covers it. 58.227.216.0/23

    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 AS9318 and a max length equal to the prefix length.

    prefix: 58.227.216.0/23
    origin: AS9318
    max-length: 23

    Open in RPKI / ROA validator Guide

  9. Warning

    58.229.98.0/23 from AS9318 is RPKI not found: no ROA covers it. 58.229.98.0/23

    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 AS9318 and a max length equal to the prefix length.

    prefix: 58.229.98.0/23
    origin: AS9318
    max-length: 23

    Open in RPKI / ROA validator Guide

  10. Warning

    58.229.116.0/23 from AS9318 is RPKI not found: no ROA covers it. 58.229.116.0/23

    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 AS9318 and a max length equal to the prefix length.

    prefix: 58.229.116.0/23
    origin: AS9318
    max-length: 23

    Open in RPKI / ROA validator Guide

  11. Warning

    58.238.84.0/23 from AS9318 is RPKI not found: no ROA covers it. 58.238.84.0/23

    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 AS9318 and a max length equal to the prefix length.

    prefix: 58.238.84.0/23
    origin: AS9318
    max-length: 23

    Open in RPKI / ROA validator Guide

Checks

Routing and RPKI 58.224.0.0/12 from AS9318 is RPKI not found: no ROA covers it.
  • Pass: Announced as 58.224.0.0/12 by AS9318.
  • Warning: 58.224.0.0/12 from AS9318 is RPKI not found: no ROA covers it.
  • Warning: 58.224.0.0/13 from AS9318 is RPKI not found: no ROA covers it. 58.224.0.0/13
  • Warning: 58.232.0.0/13 from AS9318 is RPKI not found: no ROA covers it. 58.232.0.0/13
  • Warning: 58.224.62.0/23 from AS9318 is RPKI not found: no ROA covers it. 58.224.62.0/23
  • Warning: 58.225.68.0/23 from AS9318 is RPKI not found: no ROA covers it. 58.225.68.0/23
  • Warning: 58.226.180.0/23 from AS9318 is RPKI not found: no ROA covers it. 58.226.180.0/23
  • Warning: 58.227.2.0/23 from AS9318 is RPKI not found: no ROA covers it. 58.227.2.0/23
  • Warning: 58.227.216.0/23 from AS9318 is RPKI not found: no ROA covers it. 58.227.216.0/23
  • Warning: 58.229.98.0/23 from AS9318 is RPKI not found: no ROA covers it. 58.229.98.0/23
  • Warning: 58.229.116.0/23 from AS9318 is RPKI not found: no ROA covers it. 58.229.116.0/23
  • Warning: 58.238.84.0/23 from AS9318 is RPKI not found: no ROA covers it. 58.238.84.0/23
  • Pass: Seen by 100% of RIPE RIS peers.
Route58.224.0.0/12
Origin ASAS9318 SKB-AS-KR - SK Broadband Co Ltd No ROA
IRR route objectsNTTCOM, RADB, REACH
Visibility (RIS peers)320 / 320
First seen2005-06-28
More-specific routes 44
More-specific routeOrigin ASRPKI
58.224.0.0/13 AS9318 No ROA
58.232.0.0/13 AS9318 No ROA
58.224.62.0/23 AS9318 No ROA
58.225.68.0/23 AS9318 No ROA
58.226.180.0/23 AS9318 No ROA
58.227.2.0/23 AS9318 No ROA
58.227.216.0/23 AS9318 No ROA
58.229.98.0/23 AS9318 No ROA
58.229.116.0/23 AS9318 No ROA
58.238.84.0/23 AS9318 No ROA
58.224.116.0/24 AS55615
58.224.117.0/24 AS55615
58.224.118.0/24 AS55615
58.224.119.0/24 AS55615
58.224.120.0/24 AS55615
58.224.123.0/24 AS55615
58.224.142.0/24 AS55615
58.224.160.0/24 AS55615
58.224.161.0/24 AS55615
58.224.162.0/24 AS55615
58.225.9.0/24 AS131094
58.225.10.0/24 AS9647
58.225.11.0/24 AS9647
58.225.179.0/24 AS23588
58.226.213.0/24 AS45399
58.227.74.0/24 AS45375
58.227.178.0/24 AS9966
58.227.185.0/24 AS9860
58.227.216.0/24 AS17574
58.227.217.0/24 AS54201
58.229.99.0/24 AS10062
58.229.119.0/24 AS45370
58.231.239.0/24 AS10188
58.232.45.0/24 AS9840
58.232.161.0/24 AS9860
58.232.233.0/24 AS152218
58.234.52.0/24 AS131834
58.234.133.0/24 AS131824
58.234.203.0/24 AS9850
58.235.102.0/24 AS23600
58.235.227.0/24 AS38088
58.235.239.0/24 AS38088
58.238.84.0/24 AS10062
58.239.62.0/24 AS152230

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse DNS Reverse DNS is delegated for all 10 zones checked.
  • Pass: Reverse DNS is delegated for all 10 zones checked.
  • Info: Only the first 10 of 16 reverse zones were checked.
Reverse zones 16
ZoneNameservers
224.58.in-addr.arpa b.dns.kr, c.dns.kr, d.dns.kr, e.dns.kr, f.dns.kr, g.dns.kr
225.58.in-addr.arpa b.dns.kr, c.dns.kr, d.dns.kr, e.dns.kr, f.dns.kr, g.dns.kr
226.58.in-addr.arpa b.dns.kr, c.dns.kr, d.dns.kr, e.dns.kr, f.dns.kr, g.dns.kr
227.58.in-addr.arpa b.dns.kr, c.dns.kr, d.dns.kr, e.dns.kr, f.dns.kr, g.dns.kr
228.58.in-addr.arpa b.dns.kr, c.dns.kr, d.dns.kr, e.dns.kr, f.dns.kr, g.dns.kr
229.58.in-addr.arpa b.dns.kr, c.dns.kr, d.dns.kr, e.dns.kr, f.dns.kr, g.dns.kr
230.58.in-addr.arpa b.dns.kr, c.dns.kr, d.dns.kr, e.dns.kr, f.dns.kr, g.dns.kr
231.58.in-addr.arpa b.dns.kr, c.dns.kr, d.dns.kr, e.dns.kr, f.dns.kr, g.dns.kr
232.58.in-addr.arpa b.dns.kr, c.dns.kr, d.dns.kr, e.dns.kr, f.dns.kr, g.dns.kr
233.58.in-addr.arpa b.dns.kr, c.dns.kr, d.dns.kr, e.dns.kr, f.dns.kr, g.dns.kr
Open in DNS lookup
Registration Found at rdap.apnic.net.
  • Pass: Found at rdap.apnic.net.
NamebroadNnet-KR
Handle58.224.0.0 - 58.239.255.255
Range58.224.0.0 – 58.239.255.255
CountryKR
Statusactive
Abuse contacthostmaster@nic.or.kr
Allocation
Registry (RIR)APNIC
CountrySouth Korea (KR)
Delegated on2005-06-27
StatusAllocated
Delegated range58.224.0.0/12 (58.224.0.0 – 58.239.255.255)

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, administrative IP Manager ip-adm@skbroadband.com

Source: https://rdap.apnic.net/ip/58.224.0.0/12. 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 No public NOC, policy or technical contact.
  • Pass: AS9318 is in PeeringDB as SK Broadband.
  • Info: Peering policy: Selective.
  • Info: Present at 15 internet exchanges with 20 ports (2.5T in total).
  • Warning: No public NOC, policy or technical contact.

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

NetworkSK Broadband (SK Broadband (Old - Hanaro Telecom))
AS numberAS9318
TypeCable/DSL/ISP, Global
Websitehttp://www.skbroadband.com/
IRR as-setAS-SKBROADBAND
Prefixes (IPv4 / IPv6)100000 / 10000
Traffic1-5Tbps, Balanced
Peering policySelective
LocationsPreferred
Ratio requiredNo
ContractsRequired
Last updated2026-11-10

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup