Session Report

Test run at: 2015-12-15 09:54:43 GMT
Client operating system: OSX
Client IP (v4):
Client AS (v4): 23889 (MauritiusTelecom)
IPv4 Probes: 93
Outbound spoofing summary (from the client to our server)
Source address type IPv4
Private - RFC1918 unknown
Routable unknown
Largest spoofable neighbor prefix length none
Spoof status key
receivedSpoofed packet was received.Pattern of tests from this IP block indicates a switch from allowing spoofing to blocking it.
rewrittenSpoofed packet was received, but the source address was changed en route.
blockedSpoofed packet was not received, but unspoofed packet was.
unknownNeither spoofed nor unspoofed packet was received.
IPv4 AS Route:
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 ( can spoof 0 neighboring addresses

Spoofed source addressPrefix
ASN of spoofed
source address

Meaning of status in Received column:

sendtoThe spoofer client was unable to send spoofed headers due to an operating system restriction.

IPv4 Outbound Filtering Depth:

The tracefilter test found your host unable to spoof routable, non-adjacent source addresses through even the first IP hop.
The results from all tests are aggregated to produce a summary "State of IP Spoofing" report.
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.
Last Modified