{"tool":"network-report","status":"warn","input":{"query":"103.239.176.0/24"},"findings":[{"level":"warn","text":"103.239.176.0/24 is announced by AS10099 (UNICOM-Global).","title":"103.239.176.0/24 is announced by AS10099 (UNICOM-Global).","params":{"query":"103.239.176.0/24","origins":"AS10099 (UNICOM-Global)"}},{"level":"warn","text":"Reverse DNS is not delegated for 103.239.176.0/24, so its addresses have no PTR records.","title":"Reverse DNS is not delegated for 103.239.176.0/24, so its addresses have no PTR records.","params":{"prefix":"103.239.176.0/24","count":0,"checked":1,"total":"1"},"detail":"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."}],"data":{"query":"103.239.176.0/24","kind":"prefix","special":null,"allocation":{"rir":"apnic","registry":"APNIC","cc":"HK","country":"Hong Kong SAR China","date":"2014-08-07","status":"allocated","range":"103.239.176.0/22 (103.239.176.0 – 103.239.179.255)","opaque_id":"A91144C9","special":null},"verdict":{"level":"warn","title":":query is announced by :origins.","params":{"query":"103.239.176.0/24","origins":"AS10099 (UNICOM-Global)"}},"seconds":5.2999999999999998,"sections":{"routing":{"status":"pass","findings":[{"level":"pass","title":"Announced as :prefix by :origins.","params":{"prefix":"103.239.176.0/24","origins":"AS10099"}},{"level":"pass","title":":prefix from AS:asn is RPKI valid.","params":{"asn":10099,"prefix":"103.239.176.0/24"},"detail":"A ROA authorises this origin AS for this prefix length.","tool":["rpki",{"prefix":"103.239.176.0/24","asn":"10099"}],"guide":"create-rpki-roas"},{"level":"pass","title":"Seen by :pct% of RIPE RIS peers.","params":{"pct":100}},{"level":"info","title":"The ROA :roa allows announcements up to /:max.","params":{"roa":"103.239.176.0/22 AS10099","max":24},"detail":"A loose max length lets anyone forge your origin AS on more-specific routes that RPKI then calls valid (RFC 9319). Prefer a ROA per prefix you actually announce."}],"data":{"mode":"exact","prefix":"103.239.176.0/24","origins":[{"asn":10099,"irr":["APNIC","RADB"],"name":"UNICOM-Global - China Unicom Global"}],"rpki":[{"asn":10099,"prefix":"103.239.176.0/24","state":"valid"}],"seen":321,"total":321,"first_seen":"2014-09-10T16:00:00","covering":[],"more":[],"more_count":0,"roas":[{"asn":10099,"prefix":"103.239.176.0/22","max_length":24}]},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"103.239.176.0/24"},"summary":{"level":"pass","title":"Announced as :prefix by :origins.","params":{"prefix":"103.239.176.0/24","origins":"AS10099"}}},"reverse":{"status":"warn","findings":[{"level":"warn","title":"Reverse DNS is not delegated for :prefix, so its addresses have no PTR records.","params":{"prefix":"103.239.176.0/24","count":0,"checked":1,"total":"1"},"detail":"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."}],"data":{"zones":[{"zone":"176.239.103.in-addr.arpa","ns":[]}],"total":"1"},"title":"Reverse DNS","tool":"dns-lookup","tool_input":{"name":"176.239.103.in-addr.arpa","type":"NS"},"summary":{"level":"warn","title":"Reverse DNS is not delegated for :prefix, so its addresses have no PTR records.","params":{"prefix":"103.239.176.0/24","count":0,"checked":1,"total":"1"}}},"registration":{"status":"pass","findings":[{"level":"pass","title":"Found at :server.","params":{"server":"rdap.apnic.net"}}],"data":{"query":"103.239.176.0/24","looked_up":"103.239.176.0/24","kind":"ip","source":"https://rdap.apnic.net/ip/103.239.176.0/24","terms":"https://www.apnic.net/about-apnic/whois_search/about/termsofuse/","summary":{"Name":"UNICOM-HK","Handle":"103.239.176.0 - 103.239.177.255","Range":"103.239.176.0 – 103.239.177.255","Country":"HK","Status":"active","Registered":"2023-03-09T07:27:03Z","Last changed":"2023-03-09T07:27:23Z","Abuse contact":"wongnicholas@chinaunicom.cn"},"entities":[{"roles":["abuse"],"kind":"group","name":"IRT-UNICOM-HK","email":"wongnicholas@chinaunicom.cn"},{"roles":["administrative","technical"],"kind":"individual","name":"Nicholas Wong","email":"wongnicholas@chinaunicom.cn"}],"allocation":{"rir":"apnic","registry":"APNIC","cc":"HK","country":"Hong Kong SAR China","date":"2014-08-07","status":"allocated","range":"103.239.176.0/22 (103.239.176.0 – 103.239.179.255)","opaque_id":"A91144C9","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"103.239.176.0/24"},"summary":{"level":"pass","title":"Found at :server.","params":{"server":"rdap.apnic.net"}}},"peering":{"advisory":true,"status":"warn","findings":[{"level":"pass","title":"AS:asn is in PeeringDB as :name.","params":{"asn":10099,"name":"China Unicom Global"}},{"level":"info","title":"Peering policy: :policy.","params":{"policy":"Selective"},"detail":"Peers when the traffic exchange makes sense to them; contact them with your traffic figures."},{"level":"info","title":"Present at :ix internet exchanges with :ports ports (:capacity in total).","params":{"ix":28,"ports":29,"capacity":"1.1T"}},{"level":"warn","title":"No public NOC, policy or technical contact.","params":[],"detail":"Other networks use these addresses to set up peering and to reach you during an incident.","fix":"Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public."}],"data":{"asn":10099,"net":{"id":7268,"name":"China Unicom Global","aka":"China Unicom Global","website":"http://www.chinaunicomglobal.com","looking_glass":"","route_server":"","irr_as_set":"AS10099","info_type":"NSP","info_prefixes4":35000,"info_prefixes6":20000,"info_traffic":"1-5Tbps","info_ratio":"Balanced","info_scope":"Global","info_unicast":true,"info_ipv6":true,"info_never_via_route_servers":false,"ix_count":28,"fac_count":16,"policy_url":"","policy_general":"Selective","policy_locations":"Required - EU","policy_ratio":false,"policy_contracts":"Private Only","updated":"2026-10-19T20:02:30Z"},"ix_count":28,"capacity":1100000,"ix":[],"ix_total":29,"fac":[],"fac_total":16,"poc":[],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"10099"},"summary":{"level":"warn","title":"No public NOC, policy or technical contact.","params":[]}}},"fixes":[{"level":"warn","title":"Reverse DNS is not delegated for :prefix, so its addresses have no PTR records.","params":{"prefix":"103.239.176.0/24","count":0,"checked":1,"total":"1"},"detail":"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.","section":"reverse"}]},"url":"https://thenetworkery.com/tools/network-report?query=103.239.176.0%2F24"}