Hey Pinkies 🦩, did you know approximately 50% of traffic to your website comes from probes or bad actors 🤖? I operate a SaaS w/ ~600 websites, so I see crazy traffic all the time.
In my SaaS, I just created a new rule to ban actors who modify the subdomain and use local DNS. I caught 500+ IPs in the last 4 hours.
It got me thinking: we could crowd-source a firewall. I could open-source the IPs for bad actors, and a package would allow you to protect your website and share bad IPs to the pool.
I'd love to hear how you guys deal with this, and to learn what you guys think about crowd sourcing something like this.
Attaching some screenshots to show you what I see, and give you an idea of the things I scan for before laying down the ban hammer.
Back
•
Why not da dataset with api where Laravels middleware trust host could get the bad ones and filter them?
•
In response to @Stevenking1981
I wonder if there is an existing list of IPs (dataset) that I can incorporate for an additional level of filtering.
Yes, via the middleware. Right now I'm caching my offenders:
gist.github.com/MikeCraig418/573d92ed7cc8d793cfc125d3eacfa09f
I wonder if there is an existing list of IPs (dataset) that I can incorporate for an additional level of filtering.