{"tool":"network-report","status":"warn","input":{"query":"162.4.232.0/24"},"findings":[{"level":"warn","text":"162.4.232.0/24 is announced by AS141767 (CG-COMMUNICATION-AS-AP).","title":"162.4.232.0/24 is announced by AS141767 (CG-COMMUNICATION-AS-AP).","params":{"query":"162.4.232.0/24","origins":"AS141767 (CG-COMMUNICATION-AS-AP)"}},{"level":"warn","text":"Reverse DNS is not delegated for 162.4.232.0/24, so its addresses have no PTR records.","title":"Reverse DNS is not delegated for 162.4.232.0/24, so its addresses have no PTR records.","params":{"prefix":"162.4.232.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":"162.4.232.0/24","kind":"prefix","special":null,"allocation":{"rir":"apnic","registry":"APNIC","cc":"NP","country":"Nepal","date":"2026-06-10","status":"allocated","range":"162.4.232.0/23 (162.4.232.0 – 162.4.233.255)","opaque_id":"A9182C55","special":null},"verdict":{"level":"warn","title":":query is announced by :origins.","params":{"query":"162.4.232.0/24","origins":"AS141767 (CG-COMMUNICATION-AS-AP)"}},"seconds":4.0999999999999996,"sections":{"routing":{"status":"pass","findings":[{"level":"pass","title":"Announced as :prefix by :origins.","params":{"prefix":"162.4.232.0/24","origins":"AS141767"}},{"level":"pass","title":":prefix from AS:asn is RPKI valid.","params":{"asn":141767,"prefix":"162.4.232.0/24"},"detail":"A ROA authorises this origin AS for this prefix length.","tool":["rpki",{"prefix":"162.4.232.0/24","asn":"141767"}],"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":"162.4.232.0/23 AS141767","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":"162.4.232.0/24","origins":[{"asn":141767,"irr":["APNIC"],"name":"CG-COMMUNICATION-AS-AP - C G Communications Ltd"}],"rpki":[{"asn":141767,"prefix":"162.4.232.0/24","state":"valid"}],"seen":317,"total":317,"first_seen":"2026-06-14T16:00:00","covering":["162.4.232.0/23"],"more":[],"more_count":0,"roas":[{"asn":141767,"prefix":"162.4.232.0/23","max_length":24}]},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"162.4.232.0/24"},"summary":{"level":"pass","title":"Announced as :prefix by :origins.","params":{"prefix":"162.4.232.0/24","origins":"AS141767"}}},"reverse":{"status":"warn","findings":[{"level":"warn","title":"Reverse DNS is not delegated for :prefix, so its addresses have no PTR records.","params":{"prefix":"162.4.232.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":"232.4.162.in-addr.arpa","ns":[]}],"total":"1"},"title":"Reverse DNS","tool":"dns-lookup","tool_input":{"name":"232.4.162.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":"162.4.232.0/24","count":0,"checked":1,"total":"1"}}},"registration":{"status":"pass","findings":[{"level":"pass","title":"Found at :server.","params":{"server":"rdap.arin.net"}}],"data":{"query":"162.4.232.0/24","looked_up":"162.4.232.0/24","kind":"ip","source":"https://rdap.arin.net/registry/ip/162.4.232.0/24","terms":"https://www.arin.net/resources/registry/whois/tou/","summary":{"Name":"YANTRATECHNOLOGIES-NP","Handle":"162.4.232.0 - 162.4.233.255","Range":"162.4.232.0 – 162.4.233.255","Country":"NP","Status":"active","Registered":"2026-06-10T08:06:24Z","Last changed":"2026-06-10T08:06:39Z","Abuse contact":"info@yantratech.com.np"},"entities":[{"roles":["technical","administrative"],"kind":"group","name":"Yantra Technologies Pvt Ltd administrator","email":"info@yantratech.com.np"},{"roles":["abuse"],"kind":"group","name":"IRT-YANTRATECHNOLOGIES-NP","email":"info@yantratech.com.np"},{"roles":["registrant"],"kind":"org","name":"Yantra Technologies","email":"info@yantratech.com.np"}],"allocation":{"rir":"apnic","registry":"APNIC","cc":"NP","country":"Nepal","date":"2026-06-10","status":"allocated","range":"162.4.232.0/23 (162.4.232.0 – 162.4.233.255)","opaque_id":"A9182C55","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"162.4.232.0/24"},"summary":{"level":"pass","title":"Found at :server.","params":{"server":"rdap.arin.net"}}},"peering":{"advisory":true,"status":"warn","findings":[{"level":"pass","title":"AS:asn is in PeeringDB as :name.","params":{"asn":141767,"name":"C G Communications Pvt. Ltd"}},{"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":2,"ports":2,"capacity":"20.2G"}},{"level":"warn","title":"No IRR as-set is listed.","params":[],"detail":"Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.","fix":"Create an as-set in your RIR’s IRR database and add it to your PeeringDB record."}],"data":{"asn":141767,"net":{"id":27213,"name":"C G Communications Pvt. Ltd","aka":"CGNET","website":"https://cgnet.com.np/","looking_glass":"","route_server":"","irr_as_set":"","info_type":"","info_prefixes4":12,"info_prefixes6":12,"info_traffic":"","info_ratio":"Not Disclosed","info_scope":"Asia Pacific","info_unicast":true,"info_ipv6":true,"info_never_via_route_servers":false,"ix_count":2,"fac_count":0,"policy_url":"","policy_general":"Selective","policy_locations":"Not Required","policy_ratio":false,"policy_contracts":"Not Required","updated":"2025-03-07T06:04:42Z"},"ix_count":2,"capacity":20240,"ix":[],"ix_total":2,"fac":[],"fac_total":0,"poc":[{"role":"Technical","email":"peering@cgnet.com.np"},{"role":"NOC","email":"noc@cgnet.com.np"}],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"141767"},"summary":{"level":"warn","title":"No IRR as-set is listed.","params":[]}}},"fixes":[{"level":"warn","title":"Reverse DNS is not delegated for :prefix, so its addresses have no PTR records.","params":{"prefix":"162.4.232.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=162.4.232.0%2F24"}