Logo

Session Report

Summary:
Test run at: 2019-10-09 22:24:55 GMT
Client Prefix (v4): 134.84.3.x/24
Client AS (v4): 217 (UMN-SYSTEM)
IPv4 Probes: 72
Client Prefix (v6): 2607:ea00:1xx::/40
Client AS (v6): 57 (NL-GIGAPOP)
IPv6 Probes: 64
Outbound spoofing summary (from the client to our server)
Source address type IPv4IPv6
Private - RFC1918 or ULA unknownunknown
Routable unknownunknown
Largest spoofable neighbor prefix length nonenone
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 (134.84.3.x/24) can spoof 0 neighboring addresses


Spoofed source address (anon)Prefix
Length
ASN of spoofed
source address
Received
134.84.3.x/24/31217no
134.84.3.x/24/30217no
134.84.3.x/24/29217no
134.84.3.x/24/28217no
134.84.3.x/24/27217no
134.84.3.x/24/26217no
134.84.3.x/24/25217no
134.84.3.x/24/24217no
134.84.2.x/24/23217no
134.84.1.x/24/22217no
134.84.7.x/24/21217no
134.84.11.x/24/20217no
134.84.19.x/24/19217no
134.84.35.x/24/18217no
134.84.67.x/24/17217no
134.84.131.x/24/16217no
134.85.3.x/24/15UNROUTEDno
134.86.3.x/24/1413541no
134.80.3.x/24/13721no
134.92.3.x/24/12UNROUTEDno
134.68.3.x/24/1187no
134.116.3.x/24/10UNROUTEDno
134.20.3.x/24/910702no
134.212.3.x/24/81715no

Meaning of status in Received column:

noPackets spoofed from adjacent netblock were not received, probably due to blocking

IPv4 Outbound Filtering Depth:

The tracefilter test found your host unable to spoof routable, non-adjacent source addresses through even the first IP hop.
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 Adjacent Netblock Testing:
Spoofed source address (anon)Prefix
Length
ASN of spoofed
source address
Received
2607:ea00:1xx::/40/12057no
2607:ea00:1xx::/40/11257no
2607:ea00:1xx::/40/10457no
2607:ea00:1xx::/40/9657no
2607:ea00:1xx::/40/8857no
2607:ea00:1xx::/40/8057no
2607:ea00:1xx::/40/7257no
2607:ea00:1xx::/40/6457no
2607:ea00:1xx::/40/5657no
2607:ea00:1xx::/40/4857no
2607:ea00:1xx::/40/4057no
2607:ea00:81xx::/40/3257no
2607:ea80:1xx::/40/24UNROUTEDno
2607:6a00:1xx::/40/16UNROUTEDno

Meaning of status in Received column:

noPackets spoofed from adjacent netblock were not received, probably due to blocking
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