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

124.68.136.0/21 ·

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

Warning: 124.68.136.0/21 is announced by AS400018 (CLOUD). 2 warnings

Announced as124.68.136.0/21
Origin ASAS400018 CLOUD
HolderCHINACOMM
AllocationAPNIC, China (CN), allocated 2006-08-16
Size2,048 addresses
Abuse contactipas@cnnic.cn

What to fix

  1. Warning

    124.68.136.0/21 from AS400018 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 AS400018 and a max length equal to the prefix length.

    prefix: 124.68.136.0/21
    origin: AS400018
    max-length: 21

    Open in RPKI / ROA validator Guide

  2. Warning

    Reverse DNS is not delegated for 124.68.136.0/21, 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 124.68.136.0/21 from AS400018 is RPKI not found: no ROA covers it.
  • Pass: Announced as 124.68.136.0/21 by AS400018.
  • Warning: 124.68.136.0/21 from AS400018 is RPKI not found: no ROA covers it.
  • Pass: Seen by 98% of RIPE RIS peers.
Route124.68.136.0/21
Origin ASAS400018 CLOUD - Africa cloud limited No ROA
IRR route objectsRADB
Visibility (RIS peers)315 / 320
First seen2026-08-17
Covering prefixes124.68.128.0/20

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse DNS Reverse DNS is not delegated for 124.68.136.0/21, so its addresses have no PTR records.
  • Warning: Reverse DNS is not delegated for 124.68.136.0/21, so its addresses have no PTR records.
Reverse zones 8
ZoneNameservers
136.68.124.in-addr.arpa Not delegated
137.68.124.in-addr.arpa Not delegated
138.68.124.in-addr.arpa Not delegated
139.68.124.in-addr.arpa Not delegated
140.68.124.in-addr.arpa Not delegated
141.68.124.in-addr.arpa Not delegated
142.68.124.in-addr.arpa Not delegated
143.68.124.in-addr.arpa Not delegated
Open in DNS lookup
Registration Found at rdap.apnic.net.
  • Pass: Found at rdap.apnic.net.
NameCHINACOMM
Handle124.68.128.0 - 124.68.255.255
Range124.68.128.0 – 124.68.255.255
CountryCN
Statusactive
Registered2015-11-06T09:26:01Z
Last changed2026-02-05T01:14:17Z
Abuse contactipas@cnnic.cn
Allocation
Registry (RIR)APNIC
CountryChina (CN)
Delegated on2006-08-16
StatusAllocated
Delegated range124.68.128.0/17 (124.68.128.0 – 124.68.255.255)

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

Contacts
RoleNameEmail
technical Li Ding gjc16888@outlook.com
abuse IRT-CNNIC-CN ipas@cnnic.cn

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