atshift IP Blocker

This administrator-only tool reads bounded CloudSecure or Wordfence log records. Repeated candidates default to 30 records of the same classification from the same IP within a rolling ten-minute window. Different classifications are never combined; a candidate still needs manual review. Source reads and .htaccess editing are separate opt-ins, disabled by default. It is not a WAF, does not detect attacks, and never automatically blocks an IP based on its count. Provider plugin pages: CloudSecure WP Security and Wordfence. Apache 2.4, single-site WordPress and a same-directory site home are required for file editing. Select exact public IPs, review a preview, download the original file and confirm independent hosting/SFTP access before applying. The plugin preserves unrelated .htaccess bytes and manages only its own conditional-denial section. Failed site checks attempt rollback but cannot guarantee recovery after process termination, hosting failures or concurrent changes. Verify compatibility on staging first. Deactivation/uninstall leaves server blocks and local recovery data intact. Existing manual deny rules are not managed by this plugin.

1.0.3

• Mark IPs currently present in this plugin's validated .htaccess section as Blocked, disable duplicate selection, and restore normal eligibility after removal. Manual rules outside the section are not classified by this badge.
• Organize change previews into IP attribution, independent recovery backup, and required confirmations before applying.
• Add visible Required badges to the backup download and both confirmation checkboxes, and improve spacing above the download button.
• Explain why database recovery history cannot replace a local download when WordPress is unreachable, and how to restore the downloaded .txt file as .htaccess through hosting or SFTP.
• Add hosting-log, trusted-proxy and published-range verification guidance, with generic Cloudflare and RIPEstat links that do not include selected IPs. Do not block an IP whose attribution is uncertain.
• Reword the recovery acknowledgement as personal recovery capability and translate all new labels and guidance in all 15 interface languages.
• Preserve administrator permissions, nonces, the mandatory current-file backup, explicit confirmations and SDN measurement protections.

1.0.2

• Identify the exact Semantic Deterrence settings path and checkbox for optional CloudSecure / BBQ reference observations when saving CloudSecure connections.
• Link directly to Semantic Deterrence settings from Connections & safety when those optional observations are disabled.
• Keep IP blocking independent from SD reference observations; no SD opt-in, mode or experiment assignment is changed.
• Clarify this guidance in all 15 interface languages and add the supplied WordPress.org directory icon.

1.0.1

• Add complete bundled translations for Spanish, German, French, Brazilian Portuguese, Italian, Russian, Dutch, Simplified Chinese, Polish, Turkish, Indonesian, Traditional Chinese (Taiwan) and Korean.
• Retain English and Japanese for 15 interface languages in total, selected through the WordPress user locale.
• Validate catalog completeness, printf placeholders, compiled translations and actual WordPress locale switching.
• Blocking behavior, consent, permissions, backups and SDN measurement are unchanged.

1.0.0

• First stable WordPress.org release under the approved name atshift IP Blocker and slug atshift-ip-blocker.
• Include the latest SDN 0.1.8 coexistence and measurement recovery support from the GitHub pilot.
• Add bundled Japanese translations alongside the English interface using the approved text domain.
• Preserve existing ipbw settings, backups and managed .htaccess section markers.
• Use WordPress.org updates without a GitHub updater or Update URI override.
• Retain the reviewed submission nonce checks, strict input validation and documented atomic-file protections.

0.1.3

• Allow manual IP blocks alongside SDN experiments through the SDN 0.1.8 measurement API, without changing its mode or experiment assignment.
• Protect overlapping undecided observation windows from being classified as non-continuation successes; keep these results indeterminate in local and shared statistics.
• Require explicit, health-checked measurement recovery after an interrupted change. Preserve the legacy safety guard with older SDN versions.
• Show compatibility and recovery guidance before applying changes, and separate missing confirmations, expired previews and missing backup errors.

0.1.2

• Add GitHub Release notifications and plugin details through WordPress's normal update interface, only in the GitHub distribution.
• Validate stable release versions and exact repository assets, cache metadata, verify downloaded ZIPs against their named SHA-256 file, and reject missing or mismatched checksums.
• Keep the WordPress.org submission in a separate English-only branch without this updater. Retain Japanese translations in the GitHub package and register them on init.

0.1.1

• Add official WordPress.org introduction links for CloudSecure WP Security and Wordfence to the administrator connection settings and plugin documentation.
• Keep provider selection separate from external links, with mobile wrapping and safe new-tab attributes. Detection, grouping, blocking and backup behavior are unchanged.

0.1.0

• Initial pilot: administrator-only CloudSecure/Wordfence IP review, public-IP validation, protected addresses, bounded read-only queries, change previews, backup download, hash-checked replacement and guarded rollback.