Logo

Session Report

Summary:
Test run at: 2016-09-14 19:17:52 GMT
Client Prefix (v4): 41.41.29.x/24
Client AS (v4): 8452 (TE-AS)
IPv4 Probes: 88
Outbound spoofing summary (from the client to our server)
Source address type IPv4
Private - RFC1918 rewritten
Routable rewritten
Largest spoofable neighbor prefix length /31
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.

Warnings:

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 (41.41.29.x/24) can spoof 1 neighboring addresses (within your /31 prefix)


Spoofed source address (anon)Prefix
Length
ASN of spoofed
source address
Received
41.41.29.x/24/318452yes
41.41.29.x/24/308452no
41.41.29.x/24/298452sendto
41.41.29.x/24/288452rewritten
41.41.29.x/24/278452no
41.41.29.x/24/268452no
41.41.29.x/24/258452no
41.41.29.x/24/248452no
41.41.28.x/24/238452no
41.41.31.x/24/228452no
41.41.25.x/24/218452no
41.41.21.x/24/208452no
41.41.13.x/24/198452no
41.41.61.x/24/188452no
41.41.93.x/24/178452no
41.41.157.x/24/168452no
41.40.29.x/24/158452no
41.43.29.x/24/148452no
41.45.29.x/24/138452no
41.33.29.x/24/128452no
41.57.29.x/24/1122750no
41.9.29.x/24/1029975no
41.105.29.x/24/936947no
41.169.29.x/24/836937no

Meaning of status in Received column:

noPackets spoofed from adjacent netblock were not received, probably due to blocking
yesPackets spoofed from adjacent netblock were received (but that netblock is within the source AS)
rewrittenThe source address of the probe packets we received differs from the spoofed address. It appears that an intermediate device is rewriting your packet headers.
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 able to spoof routable, non-adjacent source addresses through the first 1 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.
Last Modified