Skip to main content

How to block HIFIBot

Operated by HIFI. Short Description: HIFI is a financial services company for musicians and professional creators. HIFI acts as an agent on behalf of its clients to automate the retrieval and processing of royalty earnings statements. HIFI’s clients provide access credentials for each of their portal accounts and then HIFI automates the otherwise labor intensive process of logging into each portal, downloading and then processing the relevant CSVs. HIFI analyzes and aggregates the underlying data and presents its clients with a business management comprehensive dashboard.

How it identifies itself

Mozilla/5.0 (compatible; HIFIBot/1; +https://hi.fi)

robots.txt

What the agent asks to be told. It obeys this or it does not — nothing enforces it.

robots.txt
User-agent: HIFIBot
Disallow: /

nginx

In the server block, then reload.

nginx
# 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 ~* "(HIFIBot)") {
    return 403;
}

Apache

In .htaccess or the vhost.

Apache
BrowserMatchNoCase "HIFIBot" bad_bot

<RequireAll>
    Require all granted
    Require not env bad_bot
</RequireAll>

Cloudflare

Security → WAF → Custom rules.

Cloudflare
# Security → WAF → Custom rules, action: Block
(http.user_agent contains "HIFIBot")

WordPress

A child theme's functions.php, or a small plugin.

WordPress
// 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 (['HIFIBot'] as $needle) {
        if (stripos($agent, $needle) !== false) {
            status_header(403);
            exit('Blocked: HIFIBot');
        }
    }
});

robots.txt is a request. The rules below it are the wall.

HIFIBot 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.

Others like it

Everything we know about HIFIBot