Spoofing Information for AS 53181

Spoofing status per IP block for last year of data

(Results for all dates also available.)
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.
IP blockLatest testSpoof
191.241.65.x/242022-03-22 17:57:34 GMTblockedreceived
191.241.79.x/242022-11-28 10:00:02 GMTrewrittenrewritten
201.33.174.x/242022-12-10 00:35:17 GMTblockedblocked
2804:113c:8cxx::/402022-12-10 00:35:17 GMTrewrittenrewritten

Customers of AS 53181 we have spoofer tests from

This is the list of directly connected customers of AS 53181 from which we have received a spoofer test, ordered by the customer's ability to send spoofed packets and the number of prefixes of an inferred ingress ACL derived from prefix announcements for the customer recorded in the latest month of public BGP data. BCP-84 describes ingress ACLs as "the most bulletproof solution when done properly" and the "best fit ... when the configuration is not too dynamic, ... if the number of used prefixes is low." Further detail about the size and dynamism of an inferred ACL is available by following the History link for each AS.

ASNCountryNumber of Prefixes
in Customer Cone
Number of ASes
in Customer Cone
13335 (CLOUDFLARENET)gbr (United Kingdom)129071220AS 13335 testsblocked

Address Space Announcement History

The customer cone for 53181 is too large for a prefix list to be useful.

Last Modified