Session Report

Summary:

Test run at: 2020-02-08 00:02:08 GMT
Client Prefix (v4): 213.205.194.x/24
Client AS (v4): 12576 (EE)
IPv4 Probes: 75
Client Prefix (v6): 2a01:4c8:4xx::/40
Client AS (v6): 12576 (EE)
IPv6 Probes: 72

Outbound spoofing summary (from the client to our server)
Source address type	IPv4		IPv6
Private - RFC1918 or ULA	rewritten		blocked
Routable	rewritten		blocked
Largest spoofable neighbor prefix length	none		/64

Spoof status key
received		Spoofed packet was received.	✔	Pattern of tests from this IP block indicates a switch from allowing spoofing to blocking it.
rewritten		Spoofed packet was received, but the source address was changed en route.
blocked		Spoofed packet was not received, but unspoofed packet was.
unknown		Neither spoofed nor unspoofed packet was received.

Warnings:

• ⚠️ Your host is behind a Network Address Translation (NAT) router or firewall which rewrites the source addresses of the test traffic. To test your provider's network further, you must remove the NAT/firewall/router and connect directly.

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

Spoofed source address (anon)	Prefix Length	ASN of spoofed source address	Received
213.205.194.x/24	/31	12576	rewritten
213.205.194.x/24	/30	12576	rewritten
213.205.194.x/24	/29	12576	rewritten
213.205.194.x/24	/28	12576	rewritten
213.205.194.x/24	/27	12576	rewritten
213.205.194.x/24	/26	12576	rewritten
213.205.194.x/24	/25	12576	rewritten
213.205.194.x/24	/24	12576	rewritten
213.205.195.x/24	/23	12576	rewritten
213.205.192.x/24	/22	12576	rewritten
213.205.198.x/24	/21	12576	rewritten
213.205.202.x/24	/20	12576	rewritten
213.205.210.x/24	/19	12576	rewritten
213.205.226.x/24	/18	12576	rewritten
213.205.130.x/24	/17	5413	rewritten
213.205.66.x/24	/16	2860	rewritten
213.204.194.x/24	/15	UNROUTED	rewritten
213.207.194.x/24	/14	206065	rewritten
213.201.194.x/24	/13	4589	rewritten
213.197.194.x/24	/12	15879	rewritten
213.221.194.x/24	/11	15600	rewritten
213.237.194.x/24	/10	5587	rewritten
213.141.194.x/24	/9	12479	rewritten
213.77.194.x/24	/8	12479	rewritten

Meaning of status in Received column:

rewritten

The 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 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 probes:

Spoofed source address	Destination	Received
2001:48d0:101:501::159	2001:40b0:7500:280::5458:517a	no
2001:4978:1fb:6400::d2	2001:40b0:7500:280::5458:517a	no
2001:49aa:111:aa00::11	2001:40b0:7500:280::5458:517a	no
fd11:1111:1111::1111	2001:40b0:7500:280::5458:517a	no
2001:48d0:101:501::159	2001:48d0:101:501::242	no
2001:4978:1fb:6400::d2	2001:48d0:101:501::242	no
2001:49aa:111:aa00::11	2001:48d0:101:501::242	no
fd11:1111:1111::1111	2001:48d0:101:501::242	no
2001:48d0:101:501::159	2001:48d0:101:501::247	no
2001:4978:1fb:6400::d2	2001:48d0:101:501::247	no
2001:49aa:111:aa00::11	2001:48d0:101:501::247	no
fd11:1111:1111::1111	2001:48d0:101:501::247	no
2001:48d0:101:501::159	2001:610:510:115:192:42:115:98	no
2001:4978:1fb:6400::d2	2001:610:510:115:192:42:115:98	no
2001:49aa:111:aa00::11	2001:610:510:115:192:42:115:98	no
fd11:1111:1111::1111	2001:610:510:115:192:42:115:98	no
2001:48d0:101:501::159	2001:630:212:225:225:90ff:fe0c:45a6	no
2001:4978:1fb:6400::d2	2001:630:212:225:225:90ff:fe0c:45a6	no
2001:49aa:111:aa00::11	2001:630:212:225:225:90ff:fe0c:45a6	no
fd11:1111:1111::1111	2001:630:212:225:225:90ff:fe0c:45a6	no
2001:48d0:101:501::159	2001:770:18:7:225:90ff:fe0c:acb4	no
2001:4978:1fb:6400::d2	2001:770:18:7:225:90ff:fe0c:acb4	no
2001:49aa:111:aa00::11	2001:770:18:7:225:90ff:fe0c:acb4	no
fd11:1111:1111::1111	2001:770:18:7:225:90ff:fe0c:acb4	no
2001:48d0:101:501::159	2001:df0:4:800:21c:c0ff:feb2:ad5f	no
2001:4978:1fb:6400::d2	2001:df0:4:800:21c:c0ff:feb2:ad5f	no
2001:49aa:111:aa00::11	2001:df0:4:800:21c:c0ff:feb2:ad5f	no
fd11:1111:1111::1111	2001:df0:4:800:21c:c0ff:feb2:ad5f	no

IPv6 Adjacent Netblock Testing:

Spoofed source address (anon)	Prefix Length	ASN of spoofed source address	Received
2a01:4c8:4xx::/40	/120	12576	yes
2a01:4c8:4xx::/40	/112	12576	yes
2a01:4c8:4xx::/40	/104	12576	yes
2a01:4c8:4xx::/40	/96	12576	yes
2a01:4c8:4xx::/40	/88	12576	yes
2a01:4c8:4xx::/40	/80	12576	yes
2a01:4c8:4xx::/40	/72	12576	yes
2a01:4c8:4xx::/40	/64	12576	yes
2a01:4c8:4xx::/40	/56	12576	no
2a01:4c8:4xx::/40	/48	12576	no
2a01:4c8:4xx::/40	/40	12576	no
2a01:4c8:84xx::/40	/32	12576	no
2a01:448:4xx::/40	/24	42585	no
2a01:84c8:4xx::/40	/16	UNROUTED	no

Meaning of status in Received column:

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