Test run at: 2017-10-13 09:03:06 GMTIPv4 AS Route:
Client Prefix (v4): 217.117.233.x/24
Client AS (v4): 16281 (UTELISYS)
IPv4 Probes: 105
Client Prefix (v6): 2a03:a980:xx::/40
Client AS (v6): 16281 (UTELISYS)
IPv6 Probes: 68
Outbound spoofing summary (from the client to our server) Source address type IPv4 IPv6 Private - RFC1918 or ULA blocked blocked Routable blocked blocked Largest spoofable neighbor prefix length none none
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 Outbound Filtering Depth:
The tracefilter test found your host unable to spoof routable, non-adjacent source addresses through even the first IP hop.IPv6 probes:
Spoofed source address Destination Received
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.