{"tool":"network-report","status":"warn","input":{"query":"162.33.167.0/24"},"findings":[{"level":"warn","text":"162.33.167.0/24 is not announced on the internet.","title":"162.33.167.0/24 is not announced on the internet.","params":{"query":"162.33.167.0/24"}},{"level":"warn","text":"162.33.167.0/24 is not announced in the global routing table, so nothing on the internet can reach it.","title":"162.33.167.0/24 is not announced in the global routing table, so nothing on the internet can reach it.","params":{"query":"162.33.167.0/24"},"detail":"Without a route, packets to these addresses are dropped at the first router that has no default route.","fix":"If the space is in use, announce it (or a covering prefix) from your AS, with a ROA and a route object; ask your upstream to accept it."},{"level":"warn","text":"Reverse DNS is not delegated for 162.33.167.0/24, so its addresses have no PTR records.","title":"Reverse DNS is not delegated for 162.33.167.0/24, so its addresses have no PTR records.","params":{"prefix":"162.33.167.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."},{"level":"warn","text":"No abuse contact is published for 162.33.167.0/24.","title":"No abuse contact is published for 162.33.167.0/24.","params":{"what":"162.33.167.0/24"},"detail":"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."}],"data":{"query":"162.33.167.0/24","kind":"prefix","special":null,"allocation":{"rir":"arin","registry":"ARIN","cc":"US","country":"United States","date":"2021-07-07","status":"allocated","range":"162.33.160.0/21 (162.33.160.0 – 162.33.167.255)","opaque_id":"b990687ac3dfe750deaef0f3d6978dd4","special":null},"verdict":{"level":"warn","title":":query is not announced on the internet.","params":{"query":"162.33.167.0/24"}},"seconds":2,"sections":{"routing":{"status":"warn","findings":[{"level":"warn","title":":query is not announced in the global routing table, so nothing on the internet can reach it.","params":{"query":"162.33.167.0/24"},"detail":"Without a route, packets to these addresses are dropped at the first router that has no default route.","fix":"If the space is in use, announce it (or a covering prefix) from your AS, with a ROA and a route object; ask your upstream to accept it."}],"data":{"mode":"none","prefix":null,"origins":[],"rpki":[],"seen":null,"total":null,"first_seen":"2023-07-26T16:00:00","covering":[],"more":[],"more_count":0,"roas":[]},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"162.33.167.0/24"},"summary":{"level":"warn","title":":query is not announced in the global routing table, so nothing on the internet can reach it.","params":{"query":"162.33.167.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":"162.33.167.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":"167.33.162.in-addr.arpa","ns":[]}],"total":"1"},"title":"Reverse DNS","tool":"dns-lookup","tool_input":{"name":"167.33.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.33.167.0/24","count":0,"checked":1,"total":"1"}}},"registration":{"status":"warn","findings":[{"level":"pass","title":"Found at :server.","params":{"server":"rdap.arin.net"}},{"level":"warn","title":"No abuse contact is published for :what.","params":{"what":"162.33.167.0/24"},"detail":"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."}],"data":{"query":"162.33.167.0/24","looked_up":"162.33.167.0/24","kind":"ip","source":"https://rdap.arin.net/registry/ip/162.33.167.0/24","terms":"https://www.arin.net/resources/registry/whois/tou/","summary":{"Name":"9STONE-REASSIGNED","Handle":"NET-162-33-167-0-1","Range":"162.33.167.0 – 162.33.167.255","Status":"active","Registered":"2026-10-27T15:07:17-04:00","Last changed":"2026-10-27T15:07:17-04:00"},"entities":[{"roles":["registrant"],"kind":"org","name":"9Stone LLC","email":null}],"allocation":{"rir":"arin","registry":"ARIN","cc":"US","country":"United States","date":"2021-07-07","status":"allocated","range":"162.33.160.0/21 (162.33.160.0 – 162.33.167.255)","opaque_id":"b990687ac3dfe750deaef0f3d6978dd4","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"162.33.167.0/24"},"summary":{"level":"warn","title":"No abuse contact is published for :what.","params":{"what":"162.33.167.0/24"}}},"peering":{"status":"na","note":"Not announced, so there is no origin network to look up.","findings":[],"data":[],"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":""}}},"fixes":[{"level":"warn","title":":query is not announced in the global routing table, so nothing on the internet can reach it.","params":{"query":"162.33.167.0/24"},"detail":"Without a route, packets to these addresses are dropped at the first router that has no default route.","fix":"If the space is in use, announce it (or a covering prefix) from your AS, with a ROA and a route object; ask your upstream to accept it.","section":"routing"},{"level":"warn","title":"Reverse DNS is not delegated for :prefix, so its addresses have no PTR records.","params":{"prefix":"162.33.167.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"},{"level":"warn","title":"No abuse contact is published for :what.","params":{"what":"162.33.167.0/24"},"detail":"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.","section":"registration"}]},"url":"https://thenetworkery.com/tools/network-report?query=162.33.167.0%2F24"}