Logo

Session Report

Summary:
Test run at: 2020-09-24 14:43:42 GMT
Client Prefix (v4): 170.233.239.x/24
Client AS (v4): 265098
IPv4 Probes: 75
Client Prefix (v6): 2804:32cc:10xx::/40
Client AS (v6): 265098
IPv6 Probes: 68
Outbound spoofing summary (from the client to our server)
Source address type IPv4IPv6
Private - RFC1918 or ULA rewrittenrewritten
Routable rewrittenrewritten
Largest spoofable neighbor prefix length nonenone

Meaning of result status in column:

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 (170.233.239.x/24) can spoof 0 neighboring addresses


Spoofed source address (anon)Prefix
Length
ASN of spoofed
source address
Received
170.233.239.x/24/31265098rewritten
170.233.239.x/24/30265098rewritten
170.233.239.x/24/29265098rewritten
170.233.239.x/24/28265098rewritten
170.233.239.x/24/27265098rewritten
170.233.239.x/24/26265098rewritten
170.233.239.x/24/25265098rewritten
170.233.239.x/24/24265098rewritten
170.233.238.x/24/23265098rewritten
170.233.237.x/24/22265098rewritten
170.233.235.x/24/21264741rewritten
170.233.231.x/24/20265198rewritten
170.233.255.x/24/19265097rewritten
170.233.207.x/24/18263321rewritten
170.233.175.x/24/17264281rewritten
170.233.111.x/24/16265090rewritten
170.232.239.x/24/1521833rewritten
170.235.239.x/24/1411534rewritten
170.237.239.x/24/13UNROUTEDrewritten
170.225.239.x/24/12UNROUTEDrewritten
170.249.239.x/24/1163410rewritten
170.201.239.x/24/1010995rewritten
170.169.239.x/24/92134rewritten
170.105.239.x/24/8UNROUTEDrewritten

Meaning of status in Received column:

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.

IPv4 Outbound Filtering Depth:

The tracefilter test found your host able to spoof routable, non-adjacent source addresses through the first 2 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
2804:32cc:10xx::/40/120265098rewritten
2804:32cc:10xx::/40/112265098rewritten
2804:32cc:10xx::/40/104265098rewritten
2804:32cc:10xx::/40/96265098rewritten
2804:32cc:10xx::/40/88265098rewritten
2804:32cc:10xx::/40/80265098rewritten
2804:32cc:10xx::/40/72265098rewritten
2804:32cc:10xx::/40/64265098rewritten
2804:32cc:10xx::/40/56265098rewritten
2804:32cc:10xx::/40/48265098rewritten
2804:32cc:10xx::/40/40265098rewritten
2804:32cc:90xx::/40/32265098rewritten
2804:324c:10xx::/40/24UNROUTEDrewritten
2804:b2cc:10xx::/40/16UNROUTEDrewritten

Meaning of status in Received column:

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