Session Report
Test run at: 2024-02-09 12:06:10 GMT
Client Prefix (v4): 102.216.77.x/24
Client AS (v4): 328266 (Atomic-AS)
IPv4 Probes: 66
Client Prefix (v6): 2c0f:ef18:14xx::/40
Client AS (v6): 328266 (Atomic-AS)
IPv6 Probes: 56
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 /40
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.
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 (102.216.77.x/24) can spoof 0 neighboring addresses
Spoofed source address (anon) Prefix
LengthASN of spoofed
source addressReceived 102.216.77.x/24 /31 328266 rewritten 102.216.77.x/24 /30 328266 rewritten 102.216.77.x/24 /29 328266 rewritten 102.216.77.x/24 /28 328266 rewritten 102.216.77.x/24 /27 328266 rewritten 102.216.77.x/24 /26 328266 rewritten 102.216.77.x/24 /25 328266 rewritten 102.216.77.x/24 /24 328266 rewritten 102.216.76.x/24 /23 328266 rewritten 102.216.79.x/24 /22 328266 rewritten 102.216.73.x/24 /21 329028 rewritten 102.216.69.x/24 /20 36926 rewritten 102.216.93.x/24 /19 329075 rewritten 102.216.109.x/24 /18 329020 rewritten 102.216.13.x/24 /17 UNROUTED rewritten 102.216.205.x/24 /16 327746 rewritten 102.217.77.x/24 /15 37053 rewritten 102.218.77.x/24 /14 328938 rewritten 102.220.77.x/24 /13 328826 rewritten 102.208.77.x/24 /12 UNROUTED rewritten 102.200.77.x/24 /11 UNROUTED rewritten 102.248.77.x/24 /10 37457 rewritten 102.152.77.x/24 /9 327934 rewritten 102.88.77.x/24 /8 29465 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 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:
IPv6 Adjacent Netblock Testing:
Spoofed source address Destination Received 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:638:902:2000:ba27:ebff:fe86:2c51 no 2001:4978:1fb:6400::d2 2001:638:902:2000:ba27:ebff:fe86:2c51 no 2001:49aa:111:aa00::11 2001:638:902:2000:ba27:ebff:fe86:2c51 no fd11:1111:1111::1111 2001:638:902:2000:ba27:ebff:fe86:2c51 no 2001:48d0:101:501::159 2001:770:1c:7:225:90ff:fe0c:acb4 no 2001:4978:1fb:6400::d2 2001:770:1c:7:225:90ff:fe0c:acb4 no 2001:49aa:111:aa00::11 2001:770:1c:7:225:90ff:fe0c:acb4 no fd11:1111:1111::1111 2001:770:1c:7:225:90ff:fe0c:acb4 no 2001:48d0:101:501::159 2607:8400:2880:4::80df:9d0d no 2001:4978:1fb:6400::d2 2607:8400:2880:4::80df:9d0d no 2001:49aa:111:aa00::11 2607:8400:2880:4::80df:9d0d no fd11:1111:1111::1111 2607:8400:2880:4::80df:9d0d no 2001:48d0:101:501::159 2607:f278:2:13:da3a:ddff:fe30:ce14 no 2001:4978:1fb:6400::d2 2607:f278:2:13:da3a:ddff:fe30:ce14 no 2001:49aa:111:aa00::11 2607:f278:2:13:da3a:ddff:fe30:ce14 no fd11:1111:1111::1111 2607:f278:2:13:da3a:ddff:fe30:ce14 no
Summary:
Spoofed source address (anon) Prefix
LengthASN of spoofed
source addressReceived 2c0f:ef18:14xx::/40 /120 328266 yes 2c0f:ef18:14xx::/40 /112 328266 yes 2c0f:ef18:14xx::/40 /104 328266 yes 2c0f:ef18:14xx::/40 /96 328266 yes 2c0f:ef18:14xx::/40 /88 328266 yes 2c0f:ef18:14xx::/40 /80 328266 yes 2c0f:ef18:14xx::/40 /72 328266 yes 2c0f:ef18:14xx::/40 /64 328266 yes 2c0f:ef18:14xx::/40 /56 328266 yes 2c0f:ef18:14xx::/40 /48 328266 yes 2c0f:ef18:14xx::/40 /40 328266 yes 2c0f:ef18:94xx::/40 /32 328266 no 2c0f:ef98:14xx::/40 /24 UNROUTED no 2c0f:6f18:14xx::/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)
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.