Logo

Session Report

Summary:
Test run at: 2018-09-11 08:10:11 GMT
Client Prefix (v4): 213.5.92.x/24
Client AS (v4): 8916 (PORTFAST)
IPv4 Probes: 124
Outbound spoofing summary (from the client to our server)
Source address type IPv4
Private - RFC1918 blocked
Routable blocked
Largest spoofable neighbor prefix length /23
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 (213.5.92.x/24) can spoof 511 neighboring addresses (within your /23 prefix)


Spoofed source address (anon)Prefix
Length
ASN of spoofed
source address
Received
213.5.92.x/24/318916sendto
213.5.92.x/24/308916sendto
213.5.92.x/24/298916sendto
213.5.92.x/24/288916yes
213.5.92.x/24/278916sendto
213.5.92.x/24/268916yes
213.5.92.x/24/258916yes
213.5.92.x/24/248916sendto
213.5.93.x/24/238916yes
213.5.94.x/24/228916no
213.5.88.x/24/218916no
213.5.84.x/24/2050141sendto
213.5.76.x/24/1943260no
213.5.124.x/24/1850048no
213.5.28.x/24/1747156no
213.5.220.x/24/1631028sendto
213.4.92.x/24/153352no
213.7.92.x/24/146866no
213.1.92.x/24/132856no
213.13.92.x/24/123243no
213.21.92.x/24/1128908no
213.37.92.x/24/106739sendto
213.69.92.x/24/9702sendto
213.133.92.x/24/835432sendto

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