{"tool":"network-report","status":"warn","input":{"query":"130.22.89.0/24"},"findings":[{"level":"warn","text":"130.22.89.0/24 is announced by AS27064 (DNIC-ASBLK-27032-27159).","title":"130.22.89.0/24 is announced by AS27064 (DNIC-ASBLK-27032-27159).","params":{"query":"130.22.89.0/24","origins":"AS27064 (DNIC-ASBLK-27032-27159)"}},{"level":"warn","text":"130.22.89.0/24 from AS27064 is RPKI not found: no ROA covers it.","title":"130.22.89.0/24 from AS27064 is RPKI not found: no ROA covers it.","params":{"asn":27064,"prefix":"130.22.89.0/24"},"detail":"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 AS27064 and a max length equal to the prefix length.","record":"prefix: 130.22.89.0/24\norigin: AS27064\nmax-length: 24"},{"level":"warn","text":"No IRR route object for 130.22.89.0/24 with origin AS27064.","title":"No IRR route object for 130.22.89.0/24 with origin AS27064.","params":{"prefix":"130.22.89.0/24","asn":27064,"object":"route"},"detail":"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):","record":"route: 130.22.89.0/24\norigin: AS27064"},{"level":"warn","text":"Reverse DNS is not delegated for 130.22.89.0/24, so its addresses have no PTR records.","title":"Reverse DNS is not delegated for 130.22.89.0/24, so its addresses have no PTR records.","params":{"prefix":"130.22.89.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":"130.22.89.0/24","kind":"prefix","special":null,"allocation":{"rir":"arin","registry":"ARIN","cc":"US","country":"United States","date":"1988-04-28","status":"allocated","range":"130.22.0.0/16 (130.22.0.0 – 130.22.255.255)","opaque_id":"45fe880b68a8f2850ebdcfdc57b4556c","special":null},"verdict":{"level":"warn","title":":query is announced by :origins.","params":{"query":"130.22.89.0/24","origins":"AS27064 (DNIC-ASBLK-27032-27159)"}},"seconds":5.0999999999999996,"sections":{"routing":{"status":"warn","findings":[{"level":"pass","title":"Announced as :prefix by :origins.","params":{"prefix":"130.22.89.0/24","origins":"AS27064"}},{"level":"warn","title":":prefix from AS:asn is RPKI not found: no ROA covers it.","params":{"asn":27064,"prefix":"130.22.89.0/24"},"detail":"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 AS:asn and a max length equal to the prefix length.","record":"prefix: 130.22.89.0/24\norigin: AS27064\nmax-length: 24","tool":["rpki",{"prefix":"130.22.89.0/24","asn":"27064"}],"guide":"create-rpki-roas"},{"level":"warn","title":"No IRR route object for :prefix with origin AS:asn.","params":{"prefix":"130.22.89.0/24","asn":27064,"object":"route"},"detail":"Many networks build their prefix filters from IRR data; without a route object some of them drop the route.","fix":"Create a :object object in your RIR’s IRR database (or RADB):","record":"route: 130.22.89.0/24\norigin: AS27064"},{"level":"pass","title":"Seen by :pct% of RIPE RIS peers.","params":{"pct":100}}],"data":{"mode":"exact","prefix":"130.22.89.0/24","origins":[{"asn":27064,"irr":[],"name":"DNIC-ASBLK-27032-27159 - United States Department of Defense (DoD)"}],"rpki":[{"asn":27064,"prefix":"130.22.89.0/24","state":"not-found"}],"seen":320,"total":321,"first_seen":"2025-05-10T00:00:00","covering":["130.22.0.0/16"],"more":[],"more_count":0,"roas":[]},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"130.22.89.0/24"},"summary":{"level":"warn","title":":prefix from AS:asn is RPKI not found: no ROA covers it.","params":{"asn":27064,"prefix":"130.22.89.0/24"}}},"reverse":{"status":"warn","findings":[{"level":"warn","title":"Reverse DNS is not delegated for :prefix, so its addresses have no PTR records.","params":{"prefix":"130.22.89.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":"89.22.130.in-addr.arpa","ns":[]}],"total":"1"},"title":"Reverse DNS","tool":"dns-lookup","tool_input":{"name":"89.22.130.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":"130.22.89.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":"130.22.89.0/24","looked_up":"130.22.89.0/24","kind":"ip","source":"https://rdap.arin.net/registry/ip/130.22.89.0/24","terms":"https://www.arin.net/resources/registry/whois/tou/","summary":{"Name":"SCWAN3","Handle":"NET-130-22-0-0-2","Range":"130.22.0.0 – 130.22.255.255","Status":"active","Registered":"2025-08-27T16:01:17-04:00","Last changed":"2025-08-27T16:01:17-04:00","Abuse contact":"disa.columbus.ns.mbx.arin-registrations@mail.mil"},"entities":[{"roles":["registrant"],"kind":"org","name":"DoD Network Information Center","email":null}],"allocation":{"rir":"arin","registry":"ARIN","cc":"US","country":"United States","date":"1988-04-28","status":"allocated","range":"130.22.0.0/16 (130.22.0.0 – 130.22.255.255)","opaque_id":"45fe880b68a8f2850ebdcfdc57b4556c","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"130.22.89.0/24"},"summary":{"level":"pass","title":"Found at :server.","params":{"server":"rdap.arin.net"}}},"peering":{"advisory":true,"status":"warn","findings":[{"level":"warn","title":"PeeringDB did not answer: :error","params":{"error":"HTTP 404"},"fix":"Try again in a minute."}],"data":{"asn":27064,"error":"HTTP 404","ix":[],"fac":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"27064"},"summary":{"level":"warn","title":"PeeringDB did not answer: :error","params":{"error":"HTTP 404"}}}},"fixes":[{"level":"warn","title":":prefix from AS:asn is RPKI not found: no ROA covers it.","params":{"asn":27064,"prefix":"130.22.89.0/24"},"detail":"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 AS:asn and a max length equal to the prefix length.","record":"prefix: 130.22.89.0/24\norigin: AS27064\nmax-length: 24","tool":["rpki",{"prefix":"130.22.89.0/24","asn":"27064"}],"guide":"create-rpki-roas","section":"routing"},{"level":"warn","title":"No IRR route object for :prefix with origin AS:asn.","params":{"prefix":"130.22.89.0/24","asn":27064,"object":"route"},"detail":"Many networks build their prefix filters from IRR data; without a route object some of them drop the route.","fix":"Create a :object object in your RIR’s IRR database (or RADB):","record":"route: 130.22.89.0/24\norigin: AS27064","section":"routing"},{"level":"warn","title":"Reverse DNS is not delegated for :prefix, so its addresses have no PTR records.","params":{"prefix":"130.22.89.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=130.22.89.0%2F24"}