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

59.153.92.0/22 ·

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

Problem: 59.153.92.0/22 is announced by AS4812 (CHINANET-SH-AP). 1 problem · 2 warnings

Announced as59.153.92.0/22
Origin ASAS4812 CHINANET-SH-AP
HolderCenturyHonour
AllocationAPNIC, China (CN), allocated 2015-10-19
Size1,024 addresses

What to fix

  1. Problem

    59.153.94.0/23 from AS4811 is RPKI invalid: no ROA authorises this origin. 59.153.94.0/23

    ROAs for this space name AS4812. Networks that filter will drop the route – the usual cause of an outage after moving to a new provider or adding DDoS protection.

    Fix: Create a ROA for AS4811 (keep the old one until the move is finished), or stop announcing the route from this AS.

    prefix: 59.153.94.0/23
    origin: AS4811
    max-length: 23

    Open in RPKI / ROA validator Guide

  2. Warning

    Reverse DNS is not delegated for 59.153.92.0/22, 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

  3. Warning

    No abuse contact is published for 59.153.92.0/22.

    Other networks send reports of spam, attacks and hacked machines to the abuse contact. Without one, reports go nowhere and blocklists may list the whole range.

    Fix: Add an abuse contact to the registration: abuse-c in the RIPE database, an Abuse POC at ARIN, an abuse mailbox (IRT) at APNIC, AFRINIC or LACNIC.

    Open in WHOIS / RDAP lookup

Checks

Routing and RPKI 59.153.94.0/23 from AS4811 is RPKI invalid: no ROA authorises this origin.
  • Pass: Announced as 59.153.92.0/22 by AS4812.
  • Pass: 59.153.92.0/22 from AS4812 is RPKI valid.
  • Pass: 59.153.92.0/23 from AS4811 is RPKI valid. 59.153.92.0/23
  • Problem: 59.153.94.0/23 from AS4811 is RPKI invalid: no ROA authorises this origin. 59.153.94.0/23
  • Pass: Seen by 100% of RIPE RIS peers.
  • Info: The ROA 59.153.92.0/22 AS4812 allows announcements up to /32.
Route59.153.92.0/22
Origin ASAS4812 CHINANET-SH-AP - China Telecom (Group) RPKI valid
IRR route objectsRADB
Visibility (RIS peers)319 / 320
First seen2017-02-27
More-specific routes 2
More-specific routeOrigin ASRPKI
59.153.92.0/23 AS4811 RPKI valid
59.153.94.0/23 AS4811 RPKI invalid
ROAs covering this prefix
ROA prefixMax lengthOrigin AS
59.153.92.0/22 /32 AS4812

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse DNS Reverse DNS is not delegated for 59.153.92.0/22, so its addresses have no PTR records.
  • Warning: Reverse DNS is not delegated for 59.153.92.0/22, so its addresses have no PTR records.
Reverse zones 4
ZoneNameservers
92.153.59.in-addr.arpa Not delegated
93.153.59.in-addr.arpa Not delegated
94.153.59.in-addr.arpa Not delegated
95.153.59.in-addr.arpa Not delegated
Open in DNS lookup
Registration No abuse contact is published for 59.153.92.0/22.
  • Pass: Found at rdap.apnic.net.
  • Warning: No abuse contact is published for 59.153.92.0/22.
NameCenturyHonour
Handle59.153.92.0 - 59.153.95.255
Range59.153.92.0 – 59.153.95.255
CountryCN
Statusactive
Registered2015-10-19T08:24:33Z
Last changed2023-11-28T00:58:21Z
Allocation
Registry (RIR)APNIC
CountryChina (CN)
Delegated on2015-10-19
StatusAllocated
Delegated range59.153.92.0/22 (59.153.92.0 – 59.153.95.255)

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

Contacts
RoleNameEmail
technical Shao Yihao Shao@honour100.net
administrative Shao Rong marcshaw@honour100.net

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