Test run at: 2020-03-19 17:17:30 GMT
Client Prefix (v4): 5.20.4.x/24
Client AS (v4): 21412 (CGATES-AS)
IPv4 Probes: 75
Outbound spoofing summary (from the client to our server) Source address type IPv4 Private - RFC1918 received Routable received Largest spoofable neighbor prefix length /8
Spoof status key received Spoofed packet was received. ✔ Pattern of tests from this IP block indicates a switch from allowing spoofing to blocking it. rewritten Spoofed packet was received, but the source address was changed en route. blocked Spoofed packet was not received, but unspoofed packet was. unknown Neither spoofed nor unspoofed packet was received.
This test run probed the following paths in order to infer your ability to send different spoofed source packets. Each node in the graph corresponds to an autonomous system, i.e. different Internet service providers. NOTE: This graph does NOT show if an AS blocks spoofed packets, only the path taken by received spoofed packets. The IP Path Details are available for this run. If non-spoofed packets weren't received at a destination, the traceroute to that destination is not included in this graph and may even cause a totally empty graph.
IPv4 Adjacent Netblock Testing:
Your host (5.20.4.x/24) can spoof 16777215 neighboring addresses (within your /8 prefix)
Spoofed source address (anon) Prefix
ASN of spoofed
Received 5.20.4.x/24 /31 21412 natblock 5.20.4.x/24 /30 21412 natblock 5.20.4.x/24 /29 21412 natblock 5.20.4.x/24 /28 21412 natblock 5.20.4.x/24 /27 21412 yes 5.20.4.x/24 /26 21412 yes 5.20.4.x/24 /25 21412 yes 5.20.4.x/24 /24 21412 yes 5.20.5.x/24 /23 21412 yes 5.20.6.x/24 /22 21412 yes 5.20.0.x/24 /21 21412 yes 5.20.12.x/24 /20 21412 yes 5.20.20.x/24 /19 21412 yes 5.20.36.x/24 /18 21412 yes 5.20.68.x/24 /17 21412 yes 5.20.132.x/24 /16 21412 yes 5.21.4.x/24 /15 50010 yes 5.22.4.x/24 /14 197207 yes 5.16.4.x/24 /13 21353 yes 5.28.4.x/24 /12 12303 yes 5.4.4.x/24 /11 6805 yes 5.52.4.x/24 /10 197207 yes 5.84.4.x/24 /9 24608 yes 5.148.4.x/24 /8 25180 yes
Meaning of status in Received column:
yes Packets spoofed from adjacent netblock were received yes Packets spoofed from adjacent netblock were received (but that netblock is within the source AS) natblock Spoofed probe packets appear to be blocked by your local NAT or firewall rather than being rewritten with a public source address.
IPv4 Outbound Filtering Depth:
The tracefilter test found your host able to spoof routable, non-adjacent source addresses through the first 10 IP hop(s).Summary:
The results from all tests are aggregated to produce a summary "State of IP Spoofing" report.Feedback:
We welcome questions and feedback to the Spoofer Information Mailing List and invite users to join the Spoofer Users Mailing List for discussion and announcements.