How to block Reward Gateway
Operated by Reward Gateway. With the iboss Cloud Platform, each customer gets dedicated source cloud IP Addresses which are associated with the organization. Because of this, any data traversing the global cloud containerized gateways in the Platform will have a uniquely associated IP Address that can be mapped to the organization. This means that users always appear to be accessing the Internet from within the organization regardless of whether they’re in the office or on the road. This preserves the critical connectivity requirements that IT departments need when migrating to a cloud gateway platform.
How it identifies itself
reward-gateway
robots.txt
What the agent asks to be told. It obeys this or it does not — nothing enforces it.
User-agent: reward-gateway Disallow: /
nginx
In the server block, then reload.
# In the server block. 403 rather than 444: a closed connection tells the
# operator nothing, and an agent that gets a status code can log it.
if ($http_user_agent ~* "(reward-gateway)") {
return 403;
}
Apache
In .htaccess or the vhost.
BrowserMatchNoCase "reward-gateway" bad_bot
<RequireAll>
Require all granted
Require not env bad_bot
</RequireAll>
Cloudflare
Security → WAF → Custom rules.
# Security → WAF → Custom rules, action: Block (http.user_agent contains "reward-gateway")
WordPress
A child theme's functions.php, or a small plugin.
// functions.php of a child theme, or a small plugin. Runs before WordPress
// builds the page, so a blocked agent costs one PHP process and no queries.
add_action('init', function () {
$agent = $_SERVER['HTTP_USER_AGENT'] ?? '';
foreach (['reward-gateway'] as $needle) {
if (stripos($agent, $needle) !== false) {
status_header(403);
exit('Blocked: Reward Gateway');
}
}
});
robots.txt is a request. The rules below it are the wall.
Reward Gateway publishes a token, so the directive above will work for as long as it keeps honouring it — and nothing except its own good manners makes it. The server rules match on a header the requester sets, which stops the agent that says who it is and not the one that copies somebody else's name. Botscope verifies identity against DNS and published address ranges, records which check decided each request, and shows you the ones that lied.