About and support

Where to find help, the documentation, the versions of your site, and the legal pages.

The About page collects the links and contacts that usually sit in five different places. Open it from BotBlocker → About. The Support tile on the Dashboard opens the same page.

Contact the BotBlocker team

Channel Use it for
Support ticket A problem with the plugin, a license question, or a feature request
Telegram Short questions and quick checks: @botblocker
Email admin@botblocker.top
WordPress.org support forum Public questions that other site owners can learn from

The support form opens inside the admin area, so you do not need a second account. A ticket goes faster when you paste the versions from the System status card and the steps that led to the problem.

The form sends your site address, your name, your email and your message to the vendor. Read External services that receive data before you include visitor details in a ticket. Never paste a license key or a recovery link.

Documentation

The Documentation card links to the pages that ship with the plugin and to the public site:

  • User guide: this guide.
  • API and developers: the developer reference.
  • FAQ: the questions that come back most often.
  • Video tutorials: short walk-throughs.
  • Security blog: write-ups about bot traffic and the plugin.
  • Changelog: the release notes for every version.

The same card is a good place to start when a setting looks different from a screenshot in an older tutorial.

System status and versions

The System status card shows whether the services that BotBlocker talks to answer normally. The Software versions card lists the operating system, web server, database, PHP, WordPress and BotBlocker versions, together with the PHP limits.

This is the block to copy into a hosting ticket. The Health Status page shows the same facts next to the protection score.

Compatibility guides

Three buttons open guides that ship in the plugin folder:

  • PAYMENT-BYPASS.md: how payment callbacks are recognized, which bypass modes exist, and how to harden them.
  • DDOS-COMPATIBILITY.md: running BotBlocker behind DDoS-Guard, Stormwall, Cloudflare Under Attack mode, Qrator and similar services.
  • TLS-FINGERPRINTING.md: JA3 and JA4 requirements, server modules and setup options.

The buttons open the raw file in a window, so you read the same text that is on disk. The plugin guides cover the same ground for the same topics: Payment callbacks, DDoS and intermediary resilience, and TLS fingerprinting.

Third-party components

The Third-party card lists the libraries and assets inside the plugin, with their licenses: icons, jQuery, geolocation data, device detection, and the notification library. If your legal or procurement team asks what BotBlocker ships, start here.

The footer links to the privacy policy, the terms of service and the refund policy. The privacy policy describes the vendor side. For what your own site stores about visitors, read Privacy and data.

When something is missing

  • The support form does not open? A browser extension or an admin-side firewall can block the request. Try a private window, or write to the email address above.
  • A guide link opens an older page? The links point to the public documentation site, which falls back to English when a translation is missing. Read the English page first, then compare.
  • The System status card shows a service as down? Open Cloud API and check your license and connection. Local protection keeps working without the service.
  • You need the version numbers for a ticket but cannot open the admin area? Read them from the Health Status page through your host, or ask your host for the PHP and database versions. See Emergency recovery secrets to get back in.