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.
Checking routing, RPKI, reverse DNS, blocklists and the registry. This usually takes 3 to 10 seconds.
61.141.239.0/24 ·
Warning: 61.141.239.0/24 is announced by AS4809 (CHINATELECOM-CORE-WAN-CN2). 2 warnings
| Announced as | 61.141.239.0/24 |
|---|---|
| Origin AS | AS4809 CHINATELECOM-CORE-WAN-CN2 |
| Holder | CHINANET-GD |
| Allocation | APNIC, China (CN), allocated 1999-06-24 |
| Size | 256 addresses |
| Abuse contact | anti-spam@chinatelecom.cn |
What to fix
-
Warning
No IRR route object for 61.141.239.0/24 with origin AS4809.
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: 61.141.239.0/24 origin: AS4809
-
Warning
Reverse DNS is not delegated for 61.141.239.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.
Checks
Routing and RPKI No IRR route object for 61.141.239.0/24 with origin AS4809.
- Pass: Announced as 61.141.239.0/24 by AS4809.
- Pass: 61.141.239.0/24 from AS4809 is RPKI valid.
- Warning: No IRR route object for 61.141.239.0/24 with origin AS4809.
- Pass: Seen by 100% of RIPE RIS peers.
| Route | 61.141.239.0/24 |
|---|---|
| Origin AS | AS4809 CHINATELECOM-CORE-WAN-CN2 - China Telecom Next Generation Carrier Network RPKI valid |
| Visibility (RIS peers) | 319 / 319 |
| First seen | 2026-11-04 |
| Covering prefixes | 61.140.0.0/14 |
| ROA prefix | Max length | Origin AS |
|---|---|---|
| 61.141.239.0/24 | /24 | AS4809 |
Source: RIPEstat (RIPE NCC RIS, Routinator)
Open in ASN & BGP prefix lookupReverse DNS Reverse DNS is not delegated for 61.141.239.0/24, so its addresses have no PTR records.
- Warning: Reverse DNS is not delegated for 61.141.239.0/24, so its addresses have no PTR records.
| Zone | Nameservers |
|---|---|
| 239.141.61.in-addr.arpa | Not delegated |
Registration Found at rdap.apnic.net.
- Pass: Found at rdap.apnic.net.
| Name | CHINANET-GD |
|---|---|
| Handle | 61.140.0.0 - 61.146.255.255 |
| Range | 61.140.0.0 – 61.146.255.255 |
| Country | CN |
| Status | active |
| Registered | 2008-09-04T06:56:14Z |
| Last changed | 2021-06-15T08:05:54Z |
| Abuse contact | anti-spam@chinatelecom.cn |
| Registry (RIR) | APNIC |
|---|---|
| Country | China (CN) |
| Delegated on | 1999-06-24 |
| Status | Allocated |
| Delegated range | 61.140.0.0/14 (61.140.0.0 – 61.143.255.255) |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| abuse | IRT-CHINANET-CN | anti-spam@chinatelecom.cn |
| technical | IPMASTER CHINANET-GD | abuse_gdicnoc@163.com |
| administrative | Chinanet Hostmaster | anti-spam@chinatelecom.cn |
Source: https://rdap.apnic.net/ip/61.141.239.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 lookupPeeringDB AS4809 is in PeeringDB as China Telecom / CN2.
- Pass: AS4809 is in PeeringDB as China Telecom / CN2.
- Info: Peering policy: Selective.
- Info: Present at 2 internet exchanges with 2 ports (20G in total).
About the network that announces this space, so not in the fix list.
| Network | China Telecom / CN2 |
|---|---|
| AS number | AS4809 |
| Type | NSP, Global |
| Website | http://en.chinatelecom.com.cn/ |
| IRR as-set | AS-CN2 |
| Prefixes (IPv4 / IPv6) | 20000 / 3000 |
| Traffic | 100-200Gbps, Balanced |
| Peering policy | Selective |
| Locations | Preferred |
| Ratio required | No |
| Contracts | Private Only |
| Last updated | 2025-04-09 |
| NOC | noc@chinatelecomglobal.com |
|---|
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup