Title: Tailwatch – Security, Backups, Monitoring &amp; Management
Author: wptailwatch
Published: <strong>آگوست 25, 2026</strong>
Last modified: آگوست 25, 2026

---

Search plugins

![](https://ps.w.org/tailwatch/assets/banner-772x250.png?rev=3665797)

![](https://ps.w.org/tailwatch/assets/icon-256x256.png?rev=3665797)

# Tailwatch – Security, Backups, Monitoring & Management

 By [wptailwatch](https://profiles.wordpress.org/wptailwatch/)

[Download](https://downloads.wordpress.org/plugin/tailwatch.1.0.1.zip)

 * [Details](https://haz.wordpress.org/plugins/tailwatch/#description)
 * [Reviews](https://haz.wordpress.org/plugins/tailwatch/#reviews)
 *  [Installation](https://haz.wordpress.org/plugins/tailwatch/#installation)
 * [Development](https://haz.wordpress.org/plugins/tailwatch/#developers)

 [Support](https://wordpress.org/support/plugin/tailwatch/)

## Description

Tailwatch is a WordPress security and site management plugin that gives you real-
time visibility into what is happening on your website.

It combines security, monitoring, and backups into one lightweight system, managed
from your WordPress dashboard. Optionally connect a free Tailwatch account to receive
event-based push notifications so you stay informed wherever you are.

#### Core Features

 * Activity Logs (logins, failed logins, registrations, password resets)
 * HTTP Error Logs (4xx / 5xx monitoring)
 * Email / SMTP Logging with custom SMTP server support
 * Security Hardening Audit
 * File & Permission Protection
 * Smart SSL Monitoring & Expiry Alerts
 * File Integrity Monitoring (baseline + change detection)
 * Full Site Backups (files and database)
 * Search & Replace (safe database-wide updates with serialized data handling)
 * Content Restrictions (browser-level protection controls like copy/inspect restrictions)
 * Database Optimization Tools
 * Broken Link Scanner
 * Cron Job Manager
 * 301 Redirect Manager
 * User Management (create, edit, delete users and manage roles)
 * Login Defender (IP-based brute-force protection: failed-login throttling, automatic
   temporary lockouts, configurable retention)
 * Geo-blocking (allow/block individual IPs or IP ranges; whitelist trusted IPs 
   to bypass restrictions)
 * Username Hardening (audits for common high-risk usernames such as admin and administrator)
 * Process Monitoring & Recovery (detect stuck long-running tasks and re-schedule
   them)
 * Disk Space Monitoring
 * Event-based Push Notifications

#### Notifications

Once connected to a free Tailwatch account, your site can send event-based push 
notifications for:

 * Login activity (logins, failed logins, registrations, password resets)
 * Backup completion and backup failures
 * File integrity changes (added, modified, deleted files)
 * SSL expiry alerts and certificate status changes
 * Security Hardening Audit results (scan completed, issues detected)
 * Security feature configuration changes
 * Search & Replace completion results
 * HTTP error spikes (4xx / 5xx monitoring)
 * Database optimization results
 * Broken link scan results
 * Cron job failures
 * Email delivery (success or failed)
 * Login Defender events (IPs blocked after repeated failed logins, brute-force 
   attempts detected)

Notifications are delivered to the Tailwatch mobile app using Firebase Cloud Messaging(
FCM), routed through api.wptailwatch.com (the plugin does not contact Firebase directly).

#### Tailwatch Pro

Tailwatch Pro extends the free version with:

 * Malware Guard (cloud malware scanning, suspicious file detection, cleanup, and
   push alerts for risk-detection events)
 * Country blocking (allow or block visitors by country, applied to login forms 
   or your entire site)
 * Role-based Two-Factor Authentication (2FA)
 * Advanced User Management (account-expiry rules, “login as another user”, per-
   user 2FA status surfaced in the user list)
 * Expanded notification credits
 * Advanced scheduling controls for backups and maintenance tasks
 * Priority support

### External Services

This plugin connects to several external services. Each service, the data sent, 
and the conditions under which the connection is made are listed below. Most connections
only occur when the corresponding optional feature is enabled by the site administrator.

#### Tailwatch API (api.wptailwatch.com)

Used for license verification, push notification delivery, and optional deactivation
feedback submission. License verification and push notification delivery are active
only after you connect a free Tailwatch account from the plugin’s License screen.
The deactivation feedback submission is independent of any account connection and
is sent only if you voluntarily submit it (see below).

What is sent and when:
 – License verification: your anonymized Tailwatch user identifier
and your site URL (query string), plus an `X-Tailwatch-Header-Key` request header
containing the license credential issued when you connected your account. Sent on
dashboard visits (throttled by a short server-side cache) and on demand when you
click “Verify License”. No system metadata is included in this request; – Recovery
access provisioning: when you connect your account, the plugin generates a standard
WordPress recovery-mode cookie for your own site and sends it to the Tailwatch service
so the dashboard can help you regain access if your site later becomes unreachable(
for example, a fatal error that prevents wp-admin from loading). This value is a
single site-scoped recovery credential — the same kind WordPress itself issues for
its built-in recovery mode — that grants recovery-mode access to your site and nothing
more. It is transmitted only over the authenticated connect handshake and only after
you choose to connect your account; – Mobile push notifications: anonymized user
identifier, your site domain, and the notification type/severity tag (the plugin
no longer sends a pre-written title or body; the Tailwatch service composes those
from the event context below, and the request goes to a single relay endpoint authenticated
with a per-site routing token request header). When mobile notifications are enabled,
an additional event-context payload is also stored on api.wptailwatch.com so the
mobile app can render notification details when you tap a push. This event-context
payload contains: the event name and feature, the action and any state-change narrative(
before/after) describing what occurred, the timestamp, the requesting admin’s own
forensic baseline (IP address and user agent at the time of the event), and per-
event fields needed for the mobile app’s detail view (for example, for Email / SMTP
events the recipient address and subject line so the notification is actionable).
It does NOT include message bodies, credentials, tokens, license keys, or any other
secret. The event-context payload is held on api.wptailwatch.com only; it is NOT
forwarded to Firebase Cloud Messaging (see below) — Firebase only ever receives 
the slim title/body/type payload. – Deactivation feedback: site domain, deactivation
reason, plugin version, your “keep data / delete data” choice from the deactivation
modal, and optional free-form comments — sent only if you voluntarily click “Submit&
Deactivate” (the “Skip & Deactivate” button avoids any transmission).

Service provider: WP Tailwatch
 Privacy policy: https://wptailwatch.com/privacy-
policy Terms: https://wptailwatch.com/terms-of-services

#### Tailwatch Dashboard (dashboard.wptailwatch.com)

The central web dashboard you use to connect your site and manage your account. 
The browser opens dashboard.wptailwatch.com only when you click “Connect License”.

What is sent: your site URL and environment type (staging or production) are passed
via URL parameters when you initiate the connection flow. License information is
retrieved and stored in your WordPress database after you log in to the dashboard.

Service provider: WP Tailwatch
 Privacy policy: https://wptailwatch.com/privacy-
policy Terms: https://wptailwatch.com/terms-of-services

#### Firebase Cloud Messaging (fcm.googleapis.com)

Used to deliver mobile push notifications to your paired mobile devices. Only active
when (a) you have connected a Tailwatch account, (b) you have enabled mobile notifications
in plugin settings, and (c) you have toggled on the specific per-feature notification.

What is sent: an anonymized device token and the notification payload (title, body,
type tag) — routed via api.wptailwatch.com to Firebase Cloud Messaging for delivery
to your paired device.

Service provider: Google LLC
 Privacy policy: https://firebase.google.com/support/
privacy Terms: https://firebase.google.com/terms

#### Smart SSL Monitoring — host certificate inspection

The Smart SSL feature opens a TLS connection (raw socket) to your own site’s domain(
derived from your WordPress Site Address / `home_url()`) to read its certificate
metadata (issuer, validity dates, chain). It also issues an HTTP HEAD probe over
plain HTTP to your own site to detect HTTPHTTPS redirection behaviour. Only your
own site is contacted — Tailwatch does not connect to any third-party service for
this purpose. Disable the Smart SSL feature in plugin settings if you do not want
these requests issued.

#### Broken Link Checker — external URL scanning

The Broken Links scanner contacts URLs that you (or your site’s authors) have placed
in your post content, pages, term descriptions, user meta, and options. The plugin
issues GET requests to those URLs to determine whether they return 4xx or 5xx errors.
The set of URLs contacted is therefore controlled entirely by your own site content—
Tailwatch does not maintain a list of external services for this purpose. Disable
the Broken Links feature in plugin settings if you do not want these requests issued.

#### MaxMind GeoLite2 database download (download.maxmind.com)

The optional GeoIP integration downloads the MaxMind GeoLite2-Country database so
the plugin can resolve visitor IP addresses to a country (used to display the country
of an event in the Login Defender logs, and — with the Pro add-on — for country-
based access rules). This connection is made ONLY when you have entered your own
MaxMind license key on the Integrations screen, and ONLY on an explicit action you
take: when you save the key, and when you click “Check for updates”. There is no
automatic, background, or scheduled download.

What is sent: your MaxMind license key and the requested database edition (“GeoLite2-
Country”), in a request to https://download.maxmind.com/app/geoip_download. The 
downloaded database file is stored inside your site’s uploads directory. You must
obtain your own (free) MaxMind account and license key; the GeoLite2 data is provided
by MaxMind under the MaxMind GeoLite2 End User License Agreement. Remove the license
key on the Integrations screen to delete the database and stop all such requests.

Service provider: MaxMind, Inc.
 Privacy policy: https://www.maxmind.com/en/privacy-
policy GeoLite2 EULA: https://www.maxmind.com/en/geolite2/eula

#### WordPress.org — plugin, theme, and core updates & rollback

The optional Updates & Rollback feature contacts WordPress.org to manage updates
for your plugins, themes, and WordPress core. When you open the Updates screen it
queries api.wordpress.org for available-update information and version lists (the
same API WordPress core itself uses); when you update or roll back an item it downloads
the official package from downloads.wordpress.org and installs it through WordPress’s
own upgrade routines (WP_Upgrader / Core_Upgrader). Only official WordPress.org 
packages are ever downloaded — no third-party source is contacted. These requests
are made only when you open the Updates screen or explicitly click Update or Rollback.
Disable the Updates & Rollback feature in plugin settings if you do not want these
requests issued.

Service provider: WordPress.org (The WordPress Foundation)
 Privacy policy: https://
wordpress.org/about/privacy/

### Third-Party Libraries

#### Bundled PHP libraries

Tailwatch bundles the following open-source PHP libraries. They run entirely on 
your server and are GPLv2-compatible.

 * MaxMind GeoIP2 PHP API + MaxMind-DB Reader — reads a GeoLite2-Country database(
   which you either download on the Integrations screen using your own MaxMind license
   key, or upload manually to your site’s uploads directory) to resolve visitor 
   IPs to a country for the IP Management / Login Defender geolocation feature. 
   Runs under the `Tailwatch\Vendor\MaxMind\*` namespace. Source: https://github.
   com/maxmind/GeoIP2-php and https://github.com/maxmind/MaxMind-DB-Reader-php —
   License: Apache-2.0 (full text in `Vendor/MaxMind/LICENSE`)
 * Firebase JWT (firebase/php-jwt) — encodes and verifies the signed HS256 JSON 
   Web Tokens that authenticate the Connect REST API (used by the mobile app and
   cloud dashboard). Runs under the `Tailwatch\Vendor\Firebase\JWT\*` namespace.
   Source: https://github.com/firebase/php-jwt — License: BSD-3-Clause (full text
   in `Vendor/Firebase/JWT/LICENSE`)

All server-side HTTP requests use WordPress core’s built-in HTTP API (wp_remote_get/
wp_remote_post / wp_remote_head). No external PHP HTTP client libraries (e.g. Guzzle)
are bundled.

#### Bundled JavaScript libraries

The plugin’s admin dashboard is a React single-page application. Its compiled bundle
in `Admin/View/Static/js/` and `Admin/View/Static/css/` is built from the following
open-source libraries, all of which are GPLv2-compatible:

 * React + ReactDOM (UI framework) — https://react.dev — License: MIT
 * Redux, Redux Toolkit, and React-Redux (state management) — https://redux.js.org—
   License: MIT
 * React Router (react-router-dom) (client-side routing) — https://reactrouter.com—
   License: MIT
 * React Hook Form (form state and validation) — https://react-hook-form.com — License:
   MIT
 * Axios (HTTP client) — https://github.com/axios/axios — License: MIT
 * SweetAlert2 (modal dialogs) — https://sweetalert2.github.io — License: MIT
 * Recharts and react-d3-speedometer (charts and gauges) — https://recharts.org —
   License: MIT
 * @tanstack/react-virtual (long-list virtualization) — https://tanstack.com/virtual—
   License: MIT
 * react-loading-skeleton, react-top-loading-bar, and @ramonak/react-progress-bar(
   loading indicators) — License: MIT
 * react-hot-toast and react-toastify (toast notifications) — License: MIT
 * react-tooltip (tooltips) — https://react-tooltip.com — License: MIT
 * react-slick + slick-carousel (carousels) — https://react-slick.neostack.com —
   License: MIT
 * lucide-react (License: ISC) and react-icons (License: MIT) — icon sets
 * @uppy/core (file selection) — https://uppy.io — License: MIT
 * file-saver (client-side file downloads) — https://github.com/eligrey/FileSaver.
   js — License: MIT
 * i18n-iso-countries and countries-list (country names and metadata for country
   name and flag display) — License: MIT
 * DOMPurify (HTML sanitisation for user-supplied strings rendered in the dashboard)—
   https://github.com/cure53/DOMPurify — License: Apache-2.0 / MPL-2.0
 * prop-types (runtime prop checks) — https://github.com/facebook/prop-types — License:
   MIT
 * classnames (conditional CSS class-name joining) — https://github.com/JedWatson/
   classnames — License: MIT
 * decimal.js-light (arbitrary-precision decimal math used by the charts) — https://
   github.com/MikeMcl/decimal.js-light — License: MIT
 * Tailwind CSS (utility-first styling) — https://tailwindcss.com — License: MIT

#### Bundled font

 * Noto Color Emoji (flags-only subset) — a small subset containing only country-
   flag glyphs, bundled in `Admin/View/Static/fonts/` so country flag emoji render
   consistently across platforms, including Windows (whose system emoji font omits
   flag glyphs). Source: https://github.com/googlefonts/noto-emoji — License: SIL
   Open Font License 1.1 (full text in `Admin/View/Static/fonts/OFL.txt`).

No JavaScript library is loaded from a remote CDN at runtime; the bundle is served
entirely from the plugin directory.

### Privacy Policy

Tailwatch stores all logs and operational data locally in your WordPress database(
custom tables `{prefix}tw_settings`, `{prefix}tw_logs`, `{prefix}tw_filemon_baseline`,
and `{prefix}tw_filemon_scans`) and on disk under `uploads/tailwatch/tailwatch-logs/`(
logs and generated data) and `wp-content/tailwatch/tailwatch-backup/` (backup archives).
Both directories are sealed with deny files (.htaccess, index.php, web.config) so
their contents are not reachable over the web.

Data stored locally:

– **Activity logs** — login/logout events, failed login attempts (including the 
username submitted and the originating IP address), registrations, password reset
events
 – **HTTP error logs** — 4xx / 5xx responses captured during the request 
lifecycle – **Email logs** — SMTP send results for outbound site mail – **Backup
metadata** — backup catalogue entries (filenames, sizes, timestamps); the actual
archives live in `wp-content/tailwatch/tailwatch-backup/` – **File integrity baselines**—
file path + hash snapshots used to detect added / modified / deleted files – **Broken
link / redirection records** — URLs detected on your site and any redirects you 
have configured – **System configuration data** — every plugin feature toggle, schedule,
and threshold lives in `{prefix}tw_settings` – **Client IP addresses** — captured
for security-relevant events (failed logins, rate-limited requests, redirection 
hits) so the dashboard and audit trail can show where the event came from – **Login
Defender state** — IP addresses temporarily locked out after repeated failed logins,
throttling counters, and the per-IP activity history that drives the lockout decisions–**
Geo-blocking lists** — IPs and IP ranges you have explicitly allow-listed or block-
listed via the Geo-blocking screen, plus the timestamp and admin who created each
rule – **Visit / usage telemetry** — a local-only counter in the `tailwatch_visit_data`
option, used to drive in-dashboard onboarding hints; never transmitted

No user data, logs, or PII is transmitted to external servers unless an optional
feature is explicitly enabled by the site administrator. The full list of outbound
transmissions is documented in the “External Services” section above.

### Source Code

Tailwatch is 100% open source and distributed under GPL-2.0-or-later. The
 complete,
human-readable source code — including the React source and the Create React App/
Webpack build tooling used to produce the admin dashboard bundle that ships with
this plugin — is publicly available at:

https://github.com/tailwatch/tailwatch

The React source for the admin dashboard lives under `admin-app/` in that
 repository.
To reproduce the compiled bundle that ships in this plugin, from the repository 
root:

    ```
    npm run build
    ```

That installs the pinned dependencies, builds the React app, and copies the
 compiled
bundle into `Admin/View/Static/`. Prerequisites are Node.js 20 or later and npm …

## Screenshots

[⌊Features Overview⌉⌊Features Overview⌉[

Features Overview

[⌊Real-time Notification Settings⌉⌊Real-time Notification Settings⌉[

Real-time Notification Settings

[⌊Updates & Rollback (Real-time Notifications)⌉⌊Updates & Rollback (Real-time Notifications
)⌉[

Updates & Rollback (Real-time Notifications)

[⌊Dashboard Overview⌉⌊Dashboard Overview⌉[

Dashboard Overview

[⌊Backup Vault⌉⌊Backup Vault⌉[

Backup Vault

[⌊Malware Guard⌉⌊Malware Guard⌉[

Malware Guard

[⌊System Settings⌉⌊System Settings⌉[

System Settings

[⌊Connect License⌉⌊Connect License⌉[

Connect License

## Installation

 1. Upload the plugin to `/wp-content/plugins/tailwatch`
 2. Activate it via the WordPress Plugins screen
 3. Open Tailwatch from the admin menu
 4. Optionally connect a free Tailwatch account for mobile notifications and dashboard
    access

## FAQ

### Is Tailwatch free?

Yes. Core features run locally on your WordPress site with no paid subscription 
required.

### Do I need an account?

No. An account is only required for optional features like push notifications and
license/account sync.

### Will it slow down my site?

No. Tailwatch uses lazy loading, caching, and scheduled background processing for
performance efficiency.

### Does Tailwatch send data externally?

Only when you enable optional features such as:
 – Push notifications – License 
verification – Optional feedback submission

Core features remain fully local. See the “External Services” section below for 
the full breakdown of each transmission.

### Can I disable features?

Yes. Every module in Tailwatch can be individually enabled or disabled.

### How does the one-click login link work?

When you request a login link from an already-authenticated Tailwatch session (the
mobile app or the connected dashboard), the plugin issues a single-use link that
expires within one hour and signs in only the administrator who requested it. The
link is stored hashed, so a copy of your database reveals no usable link, and it
is invalidated the moment it is opened. Because it is a passwordless login you start
yourself, opening the link signs you straight in — like a password-reset link, it
is an alternative to typing your password rather than a second prompt.

### Does Tailwatch modify my site’s .htaccess file?

The optional Performance Optimizer feature can add a “Tailwatch Performance Settings”
block to your site’s root .htaccess — but only if you apply PHP configuration settings
from that feature and your server runs Apache with mod_php (the plugin probes for
support first). It uses WordPress core’s insert_with_markers() function, which scopes
the change to a single BEGIN/END marker block and preserves every other line in 
the file; the plugin never rewrites the whole file. After writing, it verifies your
site still responds and automatically removes the block if anything fails. You can
clear these settings at any time from the feature. Separately, Tailwatch writes 
deny files (.htaccess, index.php, web.config) inside its own storage folders under
uploads/tailwatch/ and wp-content/tailwatch/ to keep their contents unreachable 
over the web; it does not modify .htaccess anywhere else.

### Does Tailwatch change PHP settings during scans?

During a heavy operation you start — a malware scan, file-integrity check, hardening
audit, or backup — Tailwatch may temporarily raise PHP limits (memory_limit, max_execution_time)
for the duration of that request so the operation does not fail on constrained hosts.
This is a runtime-only adjustment: nothing is written to any file, it never lowers
a limit your host already sets higher, and it has no effect outside the running 
scan.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“Tailwatch – Security, Backups, Monitoring & Management” is open source software.
The following people have contributed to this plugin.

Contributors

 *   [ wptailwatch ](https://profiles.wordpress.org/wptailwatch/)

[Translate “Tailwatch – Security, Backups, Monitoring & Management” into your language.](https://translate.wordpress.org/projects/wp-plugins/tailwatch)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/tailwatch/), check 
out the [SVN repository](https://plugins.svn.wordpress.org/tailwatch/), or subscribe
to the [development log](https://plugins.trac.wordpress.org/log/tailwatch/) by [RSS](https://plugins.trac.wordpress.org/log/tailwatch/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 1.0.1

 * Connect a free Tailwatch (wptailwatch.com) account for web-dashboard and mobile
   app access with real-time push notifications, over a hardened REST connection
   with dedicated-key encryption.
 * One-click administrator login links (single-use, hashed, expire within one hour)
   initiated from a connected Tailwatch session.
 * Recovery Mode provisioning so you can regain access if your site becomes unreachable.
 * SMTP test tool for verifying your outgoing email configuration.
 * MaxMind GeoLite2 database integration (admin-initiated download) for country 
   detection in logs and geo features.
 * Plugin and theme update management with one-click rollback.
 * Performance Optimizer that raises PHP limits during heavy operations, with optional.
   htaccess tuning.
 * Setup now runs only after you choose to begin, and remembers your choice.
 * Login Defender: trusted allow-list IPs and countries are consistently excluded
   from brute-force tracking while the allow-list is enabled.
 * Feature backfill on update so newly added features appear on existing sites; 
   incompatibility notices are limited to administrators.
 * Tested up to WordPress 7.1.

#### 1.0.0

 * Initial release
 * Activity monitoring system
 * Error (HTTP 4xx / 5xx) logging
 * File integrity monitoring
 * SSL monitoring
 * Backup system (files and database)
 * Database optimization tools
 * Cron job manager
 * Login Defender (IP-based brute-force protection + lockouts)
 * Geo-blocking (IP and IP-range allow/block lists)
 * Event-based push notifications

## Meta

 *  Version **1.0.1**
 *  Last updated **3 روز ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 6.3 or higher **
 *  Tested up to **7.1**
 *  PHP version ** 7.4 or higher **
 *  Language
 * [English (US)](https://wordpress.org/plugins/tailwatch/)
 * Tags
 * [audit log](https://haz.wordpress.org/plugins/tags/audit-log/)[backup](https://haz.wordpress.org/plugins/tags/backup/)
   [monitoring](https://haz.wordpress.org/plugins/tags/monitoring/)[security](https://haz.wordpress.org/plugins/tags/security/)
   [ssl](https://haz.wordpress.org/plugins/tags/ssl/)
 *  [Advanced View](https://haz.wordpress.org/plugins/tailwatch/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/tailwatch/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/tailwatch/reviews/)

## Contributors

 *   [ wptailwatch ](https://profiles.wordpress.org/wptailwatch/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/tailwatch/)