Logo

Session Report

Summary:
Test run at: 2019-07-01 09:07:22 GMT
Client Prefix (v4): 129.194.23.x/24
Client AS (v4): 559 (SWITCH)
IPv4 Probes: 93
Outbound spoofing summary (from the client to our server)
Source address type IPv4
Private - RFC1918 blocked
Routable blocked
Largest spoofable neighbor prefix length /18
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 (129.194.23.x/24) can spoof 16383 neighboring addresses (within your /18 prefix)


Spoofed source address (anon)Prefix
Length
ASN of spoofed
source address
Received
129.194.23.x/24/31559yes
129.194.23.x/24/30559yes
129.194.23.x/24/29559yes
129.194.23.x/24/28559yes
129.194.23.x/24/27559yes
129.194.23.x/24/26559sendto
129.194.23.x/24/25559yes
129.194.23.x/24/24559yes
129.194.22.x/24/23559yes
129.194.21.x/24/22559yes
129.194.19.x/24/21559yes
129.194.31.x/24/20559yes
129.194.7.x/24/19559yes
129.194.55.x/24/18559yes
129.194.87.x/24/17559no
129.194.151.x/24/16559no
129.195.23.x/24/15559no
129.192.23.x/24/14158no
129.198.23.x/24/13385no
129.202.23.x/24/12UNROUTEDno
129.210.23.x/24/1126488no
129.226.23.x/24/10132203no
129.130.23.x/24/92701no
129.66.23.x/24/83464no

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)
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.
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