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.35.14.0/24 ·

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

Warning: 211.35.14.0/24 is announced by AS4766 (KIXS-AS-KR-KR). 3 warnings

Announced as211.35.14.0/24
Origin ASAS4766 KIXS-AS-KR-KR
HolderPUBNETPLUS-KR
AllocationAPNIC, South Korea (KR), allocated 1999-08-27
Size256 addresses
Abuse contacthostmaster@nic.or.kr

What to fix

  1. Warning

    211.35.14.0/24 from AS4766 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 AS4766 and a max length equal to the prefix length.

    prefix: 211.35.14.0/24
    origin: AS4766
    max-length: 24

    Open in RPKI / ROA validator Guide

  2. Warning

    No IRR route object for 211.35.14.0/24 with origin AS4766.

    Many networks build their prefix filters from IRR data; without a route object some of them drop the route.

    Fix: Create a route object in your RIR’s IRR database (or RADB):

    route: 211.35.14.0/24
    origin: AS4766

    Open in ASN & BGP prefix lookup

  3. Warning

    Reverse DNS is not delegated for 211.35.14.0/24, 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.35.14.0/24 from AS4766 is RPKI not found: no ROA covers it.
  • Pass: Announced as 211.35.14.0/24 by AS4766.
  • Warning: 211.35.14.0/24 from AS4766 is RPKI not found: no ROA covers it.
  • Warning: No IRR route object for 211.35.14.0/24 with origin AS4766.
  • Pass: Seen by 100% of RIPE RIS peers.
Route211.35.14.0/24
Origin ASAS4766 KIXS-AS-KR-KR - Korea Telecom No ROA
Visibility (RIS peers)319 / 319
First seen2021-12-29
Covering prefixes211.35.0.0/18

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse DNS Reverse DNS is not delegated for 211.35.14.0/24, so its addresses have no PTR records.
  • Warning: Reverse DNS is not delegated for 211.35.14.0/24, so its addresses have no PTR records.
Reverse zones 1
ZoneNameservers
14.35.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.35.0.0 - 211.35.31.255
Range211.35.0.0 – 211.35.31.255
CountryKR
Statusactive
Abuse contacthostmaster@nic.or.kr
Allocation
Registry (RIR)APNIC
CountrySouth Korea (KR)
Delegated on1999-08-27
StatusAllocated
Delegated range211.35.0.0/18 (211.35.0.0 – 211.35.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.35.14.0/24. 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: AS4766 is in PeeringDB as KT Corporation (Korea Telecom).
  • Info: Peering policy: Selective.
  • Info: Present at 14 internet exchanges with 14 ports (780G in total).
  • Warning: No public NOC, policy or technical contact.

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

NetworkKT Corporation (Korea Telecom) (KORNET)
AS numberAS4766
TypeCable/DSL/ISP, Global
Websitehttp://www.kt.com/eng/main.jsp
IRR as-setRADB::AS-KORNET
Prefixes (IPv4 / IPv6)35000 / 3000
Traffic20-50Tbps, Mostly Inbound
Peering policySelective
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2026-11-02

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup