{"tool":"network-report","status":"warn","input":{"query":"155.103.1.0/24"},"findings":[{"level":"warn","text":"155.103.1.0/24 is announced by AS401682 (DIALWAVE).","title":"155.103.1.0/24 is announced by AS401682 (DIALWAVE).","params":{"query":"155.103.1.0/24","origins":"AS401682 (DIALWAVE)"}},{"level":"warn","text":"No IRR route object for 155.103.1.0/24 with origin AS401682.","title":"No IRR route object for 155.103.1.0/24 with origin AS401682.","params":{"prefix":"155.103.1.0/24","asn":401682,"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: 155.103.1.0/24\norigin: AS401682"},{"level":"warn","text":"Seen by only 20% of RIPE RIS peers.","title":"Seen by only 20% of RIPE RIS peers.","params":{"pct":20},"detail":"Partial visibility points to filtering, a missing IRR route object, or an RPKI problem."},{"level":"warn","text":"Reverse DNS is not delegated for 155.103.1.0/24, so its addresses have no PTR records.","title":"Reverse DNS is not delegated for 155.103.1.0/24, so its addresses have no PTR records.","params":{"prefix":"155.103.1.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":"155.103.1.0/24","kind":"prefix","special":null,"allocation":{"rir":"arin","registry":"ARIN","cc":"US","country":"United States","date":"2026-04-02","status":"allocated","range":"155.103.0.0/22 (155.103.0.0 – 155.103.3.255)","opaque_id":"5c811aaf62f2a2b277e1480ff6638610","special":null},"verdict":{"level":"warn","title":":query is announced by :origins.","params":{"query":"155.103.1.0/24","origins":"AS401682 (DIALWAVE)"}},"seconds":1.5,"sections":{"routing":{"status":"warn","findings":[{"level":"pass","title":"Announced as :prefix by :origins.","params":{"prefix":"155.103.1.0/24","origins":"AS401682"}},{"level":"pass","title":":prefix from AS:asn is RPKI valid.","params":{"asn":401682,"prefix":"155.103.1.0/24"},"detail":"A ROA authorises this origin AS for this prefix length.","tool":["rpki",{"prefix":"155.103.1.0/24","asn":"401682"}],"guide":"create-rpki-roas"},{"level":"warn","title":"No IRR route object for :prefix with origin AS:asn.","params":{"prefix":"155.103.1.0/24","asn":401682,"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: 155.103.1.0/24\norigin: AS401682"},{"level":"warn","title":"Seen by only :pct% of RIPE RIS peers.","params":{"pct":20},"detail":"Partial visibility points to filtering, a missing IRR route object, or an RPKI problem."},{"level":"info","title":"The ROA :roa allows announcements up to /:max.","params":{"roa":"155.103.0.0/22 AS401682","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":"155.103.1.0/24","origins":[{"asn":401682,"irr":[],"name":"DIALWAVE - Dialwave, Inc."}],"rpki":[{"asn":401682,"prefix":"155.103.1.0/24","state":"valid"}],"seen":65,"total":320,"first_seen":"2026-04-26T08:00:00","covering":[],"more":[],"more_count":0,"roas":[{"asn":401682,"prefix":"155.103.0.0/22","max_length":24}]},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"155.103.1.0/24"},"summary":{"level":"warn","title":"No IRR route object for :prefix with origin AS:asn.","params":{"prefix":"155.103.1.0/24","asn":401682,"object":"route"}}},"reverse":{"status":"warn","findings":[{"level":"warn","title":"Reverse DNS is not delegated for :prefix, so its addresses have no PTR records.","params":{"prefix":"155.103.1.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":"1.103.155.in-addr.arpa","ns":[]}],"total":"1"},"title":"Reverse DNS","tool":"dns-lookup","tool_input":{"name":"1.103.155.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":"155.103.1.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":"155.103.1.0/24","looked_up":"155.103.1.0/24","kind":"ip","source":"https://rdap.arin.net/registry/ip/155.103.1.0/24","terms":"https://www.arin.net/resources/registry/whois/tou/","summary":{"Name":"DIALWAVE","Handle":"NET-155-103-0-0-1","Range":"155.103.0.0 – 155.103.3.255","Status":"active","Registered":"2026-04-02T09:52:12-04:00","Last changed":"2026-04-02T09:52:12-04:00","Abuse contact":"support@dialwave.com"},"entities":[{"roles":["registrant"],"kind":"org","name":"Dialwave, Inc.","email":null}],"allocation":{"rir":"arin","registry":"ARIN","cc":"US","country":"United States","date":"2026-04-02","status":"allocated","range":"155.103.0.0/22 (155.103.0.0 – 155.103.3.255)","opaque_id":"5c811aaf62f2a2b277e1480ff6638610","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"155.103.1.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":401682,"name":"Dialwave"}},{"level":"info","title":"Peering policy: :policy.","params":{"policy":"Open"},"detail":"Peers with anyone at a shared location, usually without a contract."},{"level":"info","title":"Present at :ix internet exchanges with :ports ports (:capacity in total).","params":{"ix":2,"ports":2,"capacity":"0M"}},{"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":401682,"net":{"id":39112,"name":"Dialwave","aka":"","website":"https://dialwave.com","looking_glass":"","route_server":"","irr_as_set":"AS-DIALWAVE","info_type":"NSP","info_prefixes4":7,"info_prefixes6":10,"info_traffic":"","info_ratio":"Balanced","info_scope":"Global","info_unicast":true,"info_ipv6":true,"info_never_via_route_servers":false,"ix_count":2,"fac_count":3,"policy_url":"https://www.peeringdb.com/asn/401682","policy_general":"Open","policy_locations":"Not Required","policy_ratio":false,"policy_contracts":"Not Required","updated":"2026-04-27T17:37:24Z"},"ix_count":2,"capacity":0,"ix":[],"ix_total":2,"fac":[],"fac_total":3,"poc":[],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"401682"},"summary":{"level":"warn","title":"No public NOC, policy or technical contact.","params":[]}}},"fixes":[{"level":"warn","title":"No IRR route object for :prefix with origin AS:asn.","params":{"prefix":"155.103.1.0/24","asn":401682,"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: 155.103.1.0/24\norigin: AS401682","section":"routing"},{"level":"warn","title":"Seen by only :pct% of RIPE RIS peers.","params":{"pct":20},"detail":"Partial visibility points to filtering, a missing IRR route object, or an RPKI problem.","section":"routing"},{"level":"warn","title":"Reverse DNS is not delegated for :prefix, so its addresses have no PTR records.","params":{"prefix":"155.103.1.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=155.103.1.0%2F24"}