Logo

Session Report

Summary:
Test run at: 2017-09-22 05:55:43 GMT
Client Prefix (v4): 204.10.0.x/24
Client AS (v4): 17113 (AS-TIERP-17113)
IPv4 Probes: 131
Outbound spoofing summary (from the client to our server)
Source address type IPv4
Private - RFC1918 blocked
Routable blocked
Largest spoofable neighbor prefix length /29
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 (204.10.0.x/24) can spoof 7 neighboring addresses (within your /29 prefix)


Spoofed source address (anon)Prefix
Length
ASN of spoofed
source address
Received
204.10.0.x/24/3117113yes
204.10.0.x/24/3017113rewritten
204.10.0.x/24/2917113yes
204.10.0.x/24/2817113no
204.10.0.x/24/2717113no
204.10.0.x/24/2617113no
204.10.0.x/24/2517113no
204.10.0.x/24/2417113no
204.10.1.x/24/2317113no
204.10.2.x/24/2217113no
204.10.4.x/24/2114043no
204.10.8.x/24/2018628no
204.10.16.x/24/1922154no
204.10.32.x/24/1833101no
204.10.64.x/24/1733260no
204.10.128.x/24/1622408no
204.11.0.x/24/15UNROUTEDno
204.8.0.x/24/144540no
204.14.0.x/24/1340123no
204.2.0.x/24/122914no
204.26.0.x/24/1121874no
204.42.0.x/24/102914no
204.74.0.x/24/96079no
204.138.0.x/24/8UNROUTEDno

Meaning of status in Received column:

noPackets spoofed from adjacent netblock were not received, probably due to blocking
yesPackets spoofed from adjacent netblock were received (but that netblock is within the source AS)
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 unable to spoof routable, non-adjacent source addresses through even the first IP hop.
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