Session Report
Test run at: 2020-03-11 00:21:38 GMT
Client Prefix (v4): 200.170.251.x/24
Client AS (v4): 11432
IPv4 Probes: 75
Outbound spoofing summary (from the client to our server) Source address type IPv4 Private - RFC1918 rewritten Routable received Largest spoofable neighbor prefix length /29
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.
Warnings:
- ⚠️ Your host is behind a Network Address Translation (NAT) router or firewall but spoofed packets are still being received without modification. See here for more information.
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 (200.170.251.x/24) can spoof 7 neighboring addresses (within your /29 prefix)
Spoofed source address (anon) Prefix
LengthASN of spoofed
source addressReceived 200.170.251.x/24 /31 11432 yes 200.170.251.x/24 /30 11432 natblock 200.170.251.x/24 /29 11432 yes 200.170.251.x/24 /28 11432 rewritten 200.170.251.x/24 /27 11432 rewritten 200.170.251.x/24 /26 11432 rewritten 200.170.251.x/24 /25 11432 rewritten 200.170.251.x/24 /24 11432 rewritten 200.170.250.x/24 /23 11432 rewritten 200.170.249.x/24 /22 11432 rewritten 200.170.255.x/24 /21 11432 rewritten 200.170.243.x/24 /20 11432 rewritten 200.170.235.x/24 /19 11432 rewritten 200.170.219.x/24 /18 11432 rewritten 200.170.187.x/24 /17 16735 rewritten 200.170.123.x/24 /16 19182 rewritten 200.171.251.x/24 /15 27699 rewritten 200.168.251.x/24 /14 10429 rewritten 200.174.251.x/24 /13 4230 rewritten 200.162.251.x/24 /12 19182 rewritten 200.186.251.x/24 /11 3549 rewritten 200.138.251.x/24 /10 8167 rewritten 200.234.251.x/24 /9 28597 rewritten 200.42.251.x/24 /8 28118 rewritten Meaning of status in Received column:
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. rewritten The source address of the probe packets we received differs from the spoofed address. It appears that an intermediate device is rewriting your packet headers.
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.