Logo

Session Report

Summary:
Test run at: 2017-10-15 09:36:02 GMT
Client Prefix (v4): 212.63.210.x/24
Client AS (v4): 30880 (SPACEDUMP-AS)
IPv4 Probes: 105
Client Prefix (v6): 2a01:298:xx::/40
Client AS (v6): 30880 (SPACEDUMP-AS)
IPv6 Probes: 68
Outbound spoofing summary (from the client to our server)
Source address type IPv4IPv6
Private - RFC1918 or ULA blockedblocked
Routable blockedblocked
Largest spoofable neighbor prefix length /28/48
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 (212.63.210.x/24) can spoof 15 neighboring addresses (within your /28 prefix)


Spoofed source address (anon)Prefix
Length
ASN of spoofed
source address
Received
212.63.210.x/24/3130880yes
212.63.210.x/24/3030880yes
212.63.210.x/24/2930880yes
212.63.210.x/24/2830880yes

Meaning of status in Received column:

yesPackets spoofed from adjacent netblock were received (but that netblock is within the source AS)

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

  

  
IPv6 probes:
Spoofed source addressDestinationReceived
IPv6 Adjacent Netblock Testing:
Spoofed source address (anon)Prefix
Length
ASN of spoofed
source address
Received
2a01:298:xx::/40/12030880yes
2a01:298:xx::/40/11230880yes
2a01:298:xx::/40/10430880yes
2a01:298:xx::/40/9630880yes
2a01:298:xx::/40/8830880yes
2a01:298:xx::/40/8030880yes
2a01:298:xx::/40/7230880yes
2a01:298:xx::/40/6430880yes
2a01:298:xx::/40/5630880yes
2a01:298:xx::/40/4830880yes

Meaning of status in Received column:

yesPackets spoofed from adjacent netblock were received (but that netblock is within the source AS)
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