Glossary

The BotBlocker words in a few lines each, with a link to the full page.

Security tools use their own words. When a page or a setting uses a word that you do not know, find it here. Each entry tells you what the word means for your site. It also links to the page that explains it in full.

Words that are already common knowledge, such as IP address or CDN, are not in this list. The guides link them to a good outside source. The entries are in alphabetical order.

2FA

Short for two-factor authentication. A second proof of identity at login, usually a code from an app, on top of your password. See Two-factor authentication.

Add-on

A separate module that you install next to BotBlocker. It adds one more job, for example a file scan or a report to another service. The core works without it. See Add-ons overview.

Anti-detect

The checks that look for signs of an automated browser before any CAPTCHA is shown: hidden properties, fake plugins, canvas and WebGL results, and input timing. Headless tools often fail them even when they copy a normal User-Agent. See Bot detection signals.

ASN

Short for Autonomous System Number. This number identifies the network that an address belongs to, for example the range of one internet provider or one hosting company. BotBlocker rules can use the network of a visitor. See Country and ASN rules.

Backup codes

One-time codes that let you sign in when you lose the device with your authenticator app. Save them in a safe place when you set up two-factor authentication. See Two-factor authentication.

Ban

A block that BotBlocker applies to an address. A temporary ban ends when its timer runs out; a permanent ban stays until you remove it. See Blocks and responses.

bbcs-verify

BotBlocker's own verification endpoint. It has its own address, so the check page still opens when your permalinks or homepage setup change. See Verification.

BotBlocker API

The PRO service that shares attack signals across all BotBlocker sites. Turning it on is the recommended protection level: it adds a second opinion on top of the local checks and keeps your site in step with the whole network. Your site keeps its full local protection if the service is slow or down. See BotBlocker API.

Botnet

A group of infected computers that send requests together under one controller. The addresses are many and change, so blocking one is not enough; BotBlocker uses patterns and shared signals. See Stricter checks.

Brute force

Repeated guessing of passwords or tokens, usually at the login page or over XML-RPC. BotBlocker counts the failures and blocks the address. See Login brute-force protection.

Cache backend

The fast storage BotBlocker can use for rules and counters: Redis or Memcached. If it is missing or fails, your site keeps working without it. See Cache backends.

Cache bypass

Headers that tell a cache (PHP cache, Nginx, CDN) not to store a page. BotBlocker sets them on check pages, so a cache never serves a security page to everyone. See Cache backends.

Challenge page

The page a checked visitor sees. It shows a short task or an invisible check, and then remembers the visitor when they pass. See Verification overview.

CIDR

A compact way to write a range of IP addresses, for example 203.0.113.0/24. BotBlocker IP and ASN rules accept CIDR ranges. See IP lists and proxies.

Circuit Breaker

A safety pause in the check flow. After repeated failures BotBlocker waits a short cooldown and then retries, so a broken page or a retry storm does not loop forever. See DDoS and intermediary resilience.

Command Palette

A search box that opens with Ctrl+K (Cmd+K on Mac) on any admin page. It finds every setting, tab, and action without hunting through menus. See Dashboard.

How long BotBlocker remembers a visitor who passed a check, so they are not asked again on every visit. See Cookies and sessions.

CSP

Content Security Policy. A header that tells the browser which sources it may load scripts, styles, and frames from. See Security Headers.

Drop-in

A single file in the content folder of your site. It replaces one built-in part of WordPress, for example the object cache or the maintenance page. It is easy to miss, because it does not show on the Plugins screen. See Files that run without showing up in Plugins.

Early Init

A start mode. BotBlocker blocks the addresses on your lists before WordPress loads. It needs a PRO license and the Early Init add-on. See Early Init and Early phase and MU mode.

False positive

When BotBlocker treats a real visitor as a bot. It is rare, and you fix it by allowing that visitor by address or path. See Find help for a specific problem.

FCrDNS

Forward-confirmed Reverse DNS. The method BotBlocker uses to verify search engine bots and AI crawlers: it checks that an address really belongs to the provider it claims. You cannot pass it without controlling that provider's DNS. See Trusted bots and AI providers.

File integrity

Checking that the files on your site are the ones that should be there, and that none were changed, added, or removed. See Malware Scanner.

Gateway

The payment service that processes a checkout on your site. A gateway often sends its own server request to your site to confirm a payment. This request does not look like a normal visit. See Payment callbacks.

Geo-blocking

Allowing or blocking visitors by their country. See Countries and ASN.

Health Score

A score in the admin area that rates how well your site is protected, with a level from Critical to Secure. It comes from your settings, not from your traffic. See Dashboard.

HMAC

A keyed signature. BotBlocker signs its own responses so it can tell them apart from a challenge page added by a DDoS protection service. See DDoS and intermediary resilience.

Honeypot

A hidden field on the check page. Real visitors do not see it and do not fill it in. Simple bots often fill in every field. So a filled honeypot is one more sign of a bot. See Challenge modes.

HSTS

HTTP Strict Transport Security. A header that makes browsers use only HTTPS for your site, even when a link says http. See Security Headers.

Hybrid Mode

A mode that runs BotBlocker's own check and an invisible reCAPTCHA at the same time, as two layers. See Challenge modes.

IPN

Instant Payment Notification: the server request a payment provider sends to confirm a payment. BotBlocker lets it through, so orders are not lost. See Payment callbacks.

JA3 and JA4

Two fingerprints of the way a client starts an encrypted (HTTPS) connection. BotBlocker compares them with known browsers and bot tools. A fingerprint does not identify a person. It works best as one signal together with other signals. See TLS fingerprinting.

Legitimate interest

The legal basis (Art. 6(1)(f) GDPR) that lets BotBlocker process technical data, such as an IP address, to protect your site, without asking each visitor for consent. See Privacy and data.

LLM / AI crawler

An automated AI service that reads websites, such as GPTBot, ClaudeBot, or PerplexityBot. You can allow or block each one on its own. See Trusted bots and AI providers.

Lockout

A block that starts after repeated failed logins. A progressive lockout makes each next ban longer. See Account security overview.

Mixed content

Parts of an HTTPS page, such as images or scripts, that still use the old http address. They cause the browser's "not secure" warning. See HTTPS Protocol.

mu-plugin

Short for must-use plugin. It is a plugin in the mu-plugins folder of your site. WordPress loads it on every request, and you cannot turn it off on the Plugins screen. See Files that run without showing up in Plugins.

Network activation

Turning BotBlocker on for a whole Multisite network at once, instead of site by site. See Multisite.

Object cache

The part of WordPress that keeps repeated database results in memory. With Redis or Memcached it is fast and shared between requests. See Cache backends.

Origin server

Your real server, behind a CDN or proxy. Attackers try to reach it directly to skip the CDN; BotBlocker helps block that. See HTTP overview.

PII

Personally identifiable information: data that points to a real person. BotBlocker does not collect or store it. See Privacy and data.

Preset

A ready-made group of settings, also called a protection level: Balanced, Medium, Strong, Strong API, Full, or Emergency. Applying one changes all its settings at once. See Setup wizard.

Protection score

The score on the Dashboard that shows how many important protections are on. It comes from your settings, not from your traffic. See Dashboard.

Proxy header

A header added by a CDN or proxy that carries the real visitor address, such as CF-Connecting-IP or X-Forwarded-For. See Network connection types.

PTR

A reverse-DNS record: the host name that is registered for an IP address. It tells you which network an address belongs to. BotBlocker uses it as one clue when it checks visitors and search engine bots. See Reverse-DNS cache.

Real IP

The true address of a visitor, taken from the proxy headers when a CDN or proxy sits in front of your site. See Network connection types.

Referer

The page a visitor came from, sent by the browser. BotBlocker uses it as one clue and in rules. See Search and referrer behavior.

Reputation

What BotBlocker remembers about an address or a network from past behavior. A bad reputation means a faster block on the next visit. See Stricter checks.

Reverse proxy

A server, such as a CDN, Nginx, or a load balancer, that sits in front of your site and forwards requests to it. See Cache backends.

RKN

The Roskomnadzor blocklist. BotBlocker ships it as a cloud-synced range list that you can turn on. See Country and ASN rules.

RPH

Short for requests per hour. It is the number of requests in one full hour. It finds slow bots that stay below the per-minute limits. See Behavioral Analysis.

RPM

Short for requests per minute. It is the average number of requests that a visitor or a network sends in one minute. The rate limits and the Behavioral Analysis add-on use it. See Rate limiting.

Emergency links that pause BotBlocker or turn it off when a setting locks you out. Save them before you need them. See Emergency recovery secrets.

Secure mode

The Security Check Mode setting. It sets which requests BotBlocker checks. Full Mode checks all requests, also the admin area, the API, and scheduled tasks. See Where protection applies.

Security headers

Extra rules in the server response that tell the browser how to behave safely, such as HSTS or CSP. They do not stop bots, but they make misuse harder. See Security Headers.

Session token

The value BotBlocker gives a visitor who passed a check, so later visits are not checked again. See Cookies and sessions.

Shortcode

A tag that you paste into a page to show live security statistics on the frontend. See Tools.

Silent Auto-Verify

The default check mode. A real visitor passes in the background with no click; a bot sees "Access denied". See Challenge modes.

Sliding window

A way to count requests over a moving period, so older requests drop out as time passes. It smooths out bursts better than a fixed window. See Rate limiting.

Subnet

A group of addresses that belong to one network. Counting them together catches distributed attacks that use many addresses. See Rate limiting.

Threat Defense Feed

The cloud rule feed that keeps BotBlocker's firewall rules current, with updates applied without you doing anything. See Protection overview.

TOTP

Time-based one-time password. The short code that an authenticator app, such as Google Authenticator, Authy, 1Password, or Bitwarden, shows for two-factor login. See Two-factor authentication.

TTFB

Time To First Byte: how long the server takes to start sending a page. Lower is better. See Performance overview.

User-Agent

The text that a browser or bot sends to say what it is. Bots often fake it, so BotBlocker treats it as one clue, not as proof. See Bot detection signals.

UTM

Labels in a link, for example a source, a medium, or a campaign name. Analytics tools use them to find where a visit came from. When many labeled links go to the same page, search engines can see duplicates. See Search and referrer behavior.

VPN / Tor blocking

A rule that blocks visitors who come through VPN or Tor, because those services hide the real address. It is part of stricter protection. See Stricter checks.

WAF

Web Application Firewall. The part of BotBlocker that blocks known attack requests before WordPress or your plugins handle them. See Protection overview.

Webhook

A request that another service sends to your site when something happens, such as a payment. It is automated but legitimate, so BotBlocker must let it through. See Payment callbacks.

Webshell

A hidden script on your site that lets an attacker run commands. Malware Scanner looks for webshell markers. See Malware Scanner.

X-Robots-Tag

A response header that tells search engines how to treat a page, for example not to index it (noindex). See Search and referrer behavior.

Zero-day

An attack on a flaw that has no fix yet. BotBlocker blocks the request before the vulnerable code runs, so the flaw is never reached. See Protection overview.