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

211.61.0.0/18 ·

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

Warning: 211.61.0.0/18 is announced by AS9316 (DACOM-PUBNETPLUS-AS-KR-KR). 12 warnings

Announced as211.61.0.0/18
Origin ASAS9316 DACOM-PUBNETPLUS-AS-KR-KR
HolderPUBNETPLUS-KR
AllocationAPNIC, South Korea (KR), allocated 2000-02-16
Size16,384 addresses
Abuse contacthostmaster@nic.or.kr

What to fix

  1. Warning

    211.61.0.0/18 from AS9316 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 AS9316 and a max length equal to the prefix length.

    prefix: 211.61.0.0/18
    origin: AS9316
    max-length: 18

    Open in RPKI / ROA validator Guide

  2. Warning

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

    prefix: 211.61.4.0/24
    origin: AS17585
    max-length: 24

    Open in RPKI / ROA validator Guide

  3. Warning

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

    prefix: 211.61.5.0/24
    origin: AS17585
    max-length: 24

    Open in RPKI / ROA validator Guide

  4. Warning

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

    prefix: 211.61.16.0/24
    origin: AS55632
    max-length: 24

    Open in RPKI / ROA validator Guide

  5. Warning

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

    prefix: 211.61.17.0/24
    origin: AS23579
    max-length: 24

    Open in RPKI / ROA validator Guide

  6. Warning

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

    prefix: 211.61.19.0/24
    origin: AS23579
    max-length: 24

    Open in RPKI / ROA validator Guide

  7. Warning

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

    prefix: 211.61.20.0/24
    origin: AS23579
    max-length: 24

    Open in RPKI / ROA validator Guide

  8. Warning

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

    prefix: 211.61.21.0/24
    origin: AS23579
    max-length: 24

    Open in RPKI / ROA validator Guide

  9. Warning

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

    prefix: 211.61.22.0/24
    origin: AS23579
    max-length: 24

    Open in RPKI / ROA validator Guide

  10. Warning

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

    prefix: 211.61.23.0/24
    origin: AS23579
    max-length: 24

    Open in RPKI / ROA validator Guide

  11. Warning

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

    prefix: 211.61.24.0/24
    origin: AS23579
    max-length: 24

    Open in RPKI / ROA validator Guide

  12. Warning

    Reverse DNS is not delegated for 211.61.0.0/18, so its addresses have no PTR records.

    Mail receivers look up the PTR of the sending address and reject or spam-score mail without one; traceroutes and logs show bare numbers.

    Fix: Create the reverse zones (domain objects for in-addr.arpa or ip6.arpa) at your RIR, pointing at your nameservers, or ask your provider to set PTR records.

    Open in DNS lookup

Checks

Routing and RPKI 211.61.0.0/18 from AS9316 is RPKI not found: no ROA covers it.
  • Pass: Announced as 211.61.0.0/18 by AS9316.
  • Warning: 211.61.0.0/18 from AS9316 is RPKI not found: no ROA covers it.
  • Warning: 211.61.4.0/24 from AS17585 is RPKI not found: no ROA covers it. 211.61.4.0/24
  • Warning: 211.61.5.0/24 from AS17585 is RPKI not found: no ROA covers it. 211.61.5.0/24
  • Warning: 211.61.16.0/24 from AS55632 is RPKI not found: no ROA covers it. 211.61.16.0/24
  • Warning: 211.61.17.0/24 from AS23579 is RPKI not found: no ROA covers it. 211.61.17.0/24
  • Warning: 211.61.19.0/24 from AS23579 is RPKI not found: no ROA covers it. 211.61.19.0/24
  • Warning: 211.61.20.0/24 from AS23579 is RPKI not found: no ROA covers it. 211.61.20.0/24
  • Warning: 211.61.21.0/24 from AS23579 is RPKI not found: no ROA covers it. 211.61.21.0/24
  • Warning: 211.61.22.0/24 from AS23579 is RPKI not found: no ROA covers it. 211.61.22.0/24
  • Warning: 211.61.23.0/24 from AS23579 is RPKI not found: no ROA covers it. 211.61.23.0/24
  • Warning: 211.61.24.0/24 from AS23579 is RPKI not found: no ROA covers it. 211.61.24.0/24
  • Pass: Seen by 100% of RIPE RIS peers.
Route211.61.0.0/18
Origin ASAS9316 DACOM-PUBNETPLUS-AS-KR-KR - DACOM-PUBNETPLUS No ROA
IRR route objectsRADB
Visibility (RIS peers)320 / 320
First seen2000-08-18
More-specific routes 30
More-specific routeOrigin ASRPKI
211.61.4.0/24 AS17585 No ROA
211.61.5.0/24 AS17585 No ROA
211.61.16.0/24 AS55632 No ROA
211.61.17.0/24 AS23579 No ROA
211.61.19.0/24 AS23579 No ROA
211.61.20.0/24 AS23579 No ROA
211.61.21.0/24 AS23579 No ROA
211.61.22.0/24 AS23579 No ROA
211.61.23.0/24 AS23579 No ROA
211.61.24.0/24 AS23579 No ROA
211.61.27.0/24 AS55632
211.61.28.0/24 AS55632
211.61.29.0/24 AS17841
211.61.30.0/24 AS55632
211.61.32.0/24 AS55632
211.61.34.0/24 AS55632
211.61.38.0/24 AS55632
211.61.39.0/24 AS55632
211.61.40.0/24 AS38120
211.61.41.0/24 AS38120
211.61.42.0/24 AS38120
211.61.43.0/24 AS38120
211.61.48.0/24 AS9849
211.61.49.0/24 AS9849
211.61.50.0/24 AS9849
211.61.51.0/24 AS9849
211.61.60.0/24 AS38120
211.61.61.0/24 AS38120
211.61.62.0/24 AS38120
211.61.63.0/24 AS38120

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse DNS Reverse DNS is not delegated for 211.61.0.0/18, so its addresses have no PTR records.
  • Warning: Reverse DNS is not delegated for 211.61.0.0/18, so its addresses have no PTR records.
  • Info: Only the first 10 of 64 reverse zones were checked.
Reverse zones 64
ZoneNameservers
0.61.211.in-addr.arpa Not delegated
1.61.211.in-addr.arpa Not delegated
2.61.211.in-addr.arpa Not delegated
3.61.211.in-addr.arpa Not delegated
4.61.211.in-addr.arpa Not delegated
5.61.211.in-addr.arpa Not delegated
6.61.211.in-addr.arpa Not delegated
7.61.211.in-addr.arpa Not delegated
8.61.211.in-addr.arpa Not delegated
9.61.211.in-addr.arpa Not delegated
Open in DNS lookup
Registration Found at rdap.apnic.net.
  • Pass: Found at rdap.apnic.net.
NamePUBNETPLUS-KR
Handle211.61.0.0 - 211.61.63.255
Range211.61.0.0 – 211.61.63.255
CountryKR
Statusactive
Abuse contacthostmaster@nic.or.kr
Allocation
Registry (RIR)APNIC
CountrySouth Korea (KR)
Delegated on2000-02-16
StatusAllocated
Delegated range211.61.0.0/18 (211.61.0.0 – 211.61.63.255)

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

Contacts
RoleNameEmail
administrative IP Manager ipadm@lguplus.co.kr
technical IP Manager ipadm@lguplus.co.kr
abuse IRT-KRNIC-KR hostmaster@nic.or.kr

Source: https://rdap.apnic.net/ip/211.61.0.0/18. 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

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