Website URL
na
Error Message
naAA
Other Information
hi i see the protection loads aes.js and a cryptographic challenge
is there any way to improve this protection? Like look for bad user-agents or a more intensive encryption, etc
You cannot alter the security system.
First I want to make a quick comment on your language choice. “Clanker” usually refers to AI bots, and is particularly prevalent when referring to AI voice (IVR) systems. Very few people use true AI to attack websites, they are simple task bots that just repeat the same command over and over again, and don’t vary. So “Clanker” is not a good word for what you are looking for. It’s also not a common word outside of the USA, and doesn’t translate well for people where English is not their first language.
The bot protection is pretty good as it stands, but its not perfect. Premium Hosting actually has better protection, but it’s much more resource heavy.
While you can in theory add better protection to your site (such as a captcha), it will still use resources and hit count. Unless you’re using a custom domain, and have connected it to Cloudflare, then Cloudflare’s anti-bot tools don’t use up your site resources.
i see so the protection is offered as is?
and premium has levels?
Premium Hosting uses Imunify 360 as far as I can tell and is a more sophisticated but better system.
All premium plans uses the same system. There’re no “levels” in then.
I think that premium hosting actually has worse bot protection.
The system on free hosting is quite effective at stopping bots but also introduces a number of problems, blocking things like API access, OpenGraph embeddings and hotlinking. Some websites do want/need that.
What premium hosting does have is much higher limits per account and far fewer accounts per server, which means that moderate bot traffic is acceptable without causing performance issues.
If you want more strict bot protection, you can always put Cloudflare in front of your site which has a lot more options.
They have Immunify360, but that’s a system against malware, not so much against bots.
The protection is already quite extensive as it is. The browser validation challenge is the most visible part, but there are a lot more layers to the security than that. I don’t know the exact details, but I know that there is user agent detection in the stack, so blocking bad user agents could definitely be in there too. Website activity is constantly being monitored to identify new threats and implement appropriate measures to fight them.
But what we don’t do is publicly explain our security measures in detail, which also helps any prospective attacker to figure out how to bypass them. And we don’t provide you with any controls over them: we decide what’s best for the health of our platform and determine the trade-off between functionality and security.
Fair. I’ve not tried it tbh. I was just going off what they say on their site lol