{"tool":"network-report","status":"warn","input":{"query":"144.2.14.0/24"},"findings":[{"level":"warn","text":"144.2.14.0/24 is announced by AS14413 (LINKEDIN).","title":"144.2.14.0/24 is announced by AS14413 (LINKEDIN).","params":{"query":"144.2.14.0/24","origins":"AS14413 (LINKEDIN)"}},{"level":"warn","text":"Reverse DNS is not delegated for 144.2.14.0/24, so its addresses have no PTR records.","title":"Reverse DNS is not delegated for 144.2.14.0/24, so its addresses have no PTR records.","params":{"prefix":"144.2.14.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":"144.2.14.0/24","kind":"prefix","special":null,"allocation":{"rir":"ripencc","registry":"RIPE NCC","cc":"US","country":"United States","date":"1993-09-01","status":"assigned","range":"144.2.0.0/19 (144.2.0.0 – 144.2.31.255)","opaque_id":"137727fe-22de-4307-9edf-52e48561b96b","special":null},"verdict":{"level":"warn","title":":query is announced by :origins.","params":{"query":"144.2.14.0/24","origins":"AS14413 (LINKEDIN)"}},"seconds":3.5,"sections":{"routing":{"status":"pass","findings":[{"level":"pass","title":"Announced as :prefix by :origins.","params":{"prefix":"144.2.14.0/24","origins":"AS14413"}},{"level":"pass","title":":prefix from AS:asn is RPKI valid.","params":{"asn":14413,"prefix":"144.2.14.0/24"},"detail":"A ROA authorises this origin AS for this prefix length.","tool":["rpki",{"prefix":"144.2.14.0/24","asn":"14413"}],"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":"144.2.0.0/19 AS14413","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":"144.2.14.0/24","origins":[{"asn":14413,"irr":["RADB"],"name":"LINKEDIN - LinkedIn Corporation"}],"rpki":[{"asn":14413,"prefix":"144.2.14.0/24","state":"valid"}],"seen":320,"total":320,"first_seen":"2019-10-30T00:00:00","covering":[],"more":[],"more_count":0,"roas":[{"asn":14413,"prefix":"144.2.0.0/19","max_length":24}]},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"144.2.14.0/24"},"summary":{"level":"pass","title":"Announced as :prefix by :origins.","params":{"prefix":"144.2.14.0/24","origins":"AS14413"}}},"reverse":{"status":"warn","findings":[{"level":"warn","title":"Reverse DNS is not delegated for :prefix, so its addresses have no PTR records.","params":{"prefix":"144.2.14.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":"14.2.144.in-addr.arpa","ns":[]}],"total":"1"},"title":"Reverse DNS","tool":"dns-lookup","tool_input":{"name":"14.2.144.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":"144.2.14.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":"144.2.14.0/24","looked_up":"144.2.14.0/24","kind":"ip","source":"https://rdap.arin.net/registry/ip/144.2.14.0/24","terms":"https://www.arin.net/resources/registry/whois/tou/","summary":{"Name":"LinkedIn","Handle":"144.2.0.0 - 144.2.31.255","Range":"144.2.0.0 – 144.2.31.255","Country":"US","Status":"active","Registered":"2015-01-28T14:55:58Z","Last changed":"2023-08-09T12:56:31Z","Abuse contact":"abuse@linkedin.com"},"entities":[{"roles":["administrative","technical"],"kind":"individual","name":"Hostmaster RIPE","email":null},{"roles":["registrant"],"kind":"individual","name":"HR66822-MNT","email":null},{"roles":["registrant"],"kind":"org","name":"LinkedIn Corporation","email":null},{"roles":["administrative","technical"],"kind":"individual","name":"Prashanth Kumar","email":null},{"roles":["registrant"],"kind":"individual","name":"RIPE-NCC-LEGACY-MNT","email":null},{"roles":["abuse"],"kind":"group","name":"Abuse-C Role","email":"abuse@linkedin.com"}],"allocation":{"rir":"ripencc","registry":"RIPE NCC","cc":"US","country":"United States","date":"1993-09-01","status":"assigned","range":"144.2.0.0/19 (144.2.0.0 – 144.2.31.255)","opaque_id":"137727fe-22de-4307-9edf-52e48561b96b","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"144.2.14.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":14413,"name":"LinkedIn"}},{"level":"info","title":"Peering policy: :policy.","params":{"policy":"Open"},"detail":"Peers with anyone at a shared location, usually without a contract."},{"level":"info","title":"No internet exchange ports are listed.","params":[]},{"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":14413,"net":{"id":4231,"name":"LinkedIn","aka":"LinkedIn","website":"http://press.linkedin.com/about","looking_glass":"","route_server":"","irr_as_set":"AS-LINKEDIN","info_type":"Content","info_prefixes4":30,"info_prefixes6":30,"info_traffic":"","info_ratio":"Heavy Outbound","info_scope":"Global","info_unicast":true,"info_ipv6":true,"info_never_via_route_servers":false,"ix_count":0,"fac_count":7,"policy_url":"","policy_general":"Open","policy_locations":"Preferred","policy_ratio":false,"policy_contracts":"Not Required","updated":"2026-08-01T23:35:23Z"},"ix_count":0,"capacity":0,"ix":[],"ix_total":0,"fac":[],"fac_total":7,"poc":[],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"14413"},"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":"144.2.14.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=144.2.14.0%2F24"}