Julio Potier

<p>In August 2013, a new Web Vulnerability has been released, in some words : “HTTPS can be hacked in 30 seconds”.</p>
<p>If you’re using the HTTPS (TSL or SSL) at any level (admin, front, event for 1 page) you HAVE to protect your site against this flaw now.</p>
<p>How ? Just install this free plugin!</p>


BREACH Avoider

Avoid to be easily the target of the HTTPS BREACH vulnerability.

Platform of Veri Sizintisi

<p>Breach Radar helps WordPress site owners monitor whether their users’ email addresses appear in known data breaches.</p>
<p>Features:<br />
– Dashboard overview with risk summary and insights<br />
– Manual and scheduled scans (daily)<br />
– Logs with filters (email, found, HTTP, date range)<br />
– Admin notifications on breach count increases (configurable threshold)<br />
– Protection badge shortcode and Theme Customizer integration<br />
– i18n: English and Turkish included; Azerbaijani and Russian supported via PO files</p>
<h4>How it works</h4>
<ol>
<li>Get your API key at get.verisizintisi.com/wordpress and paste it in Settings.</li>
<li>Start a manual scan or enable the daily scan. The plugin sends, over HTTPS:
<ul>
<li>Your site domain (to validate token usage)</li>
<li>The email addresses selected for scanning</li>
</ul>
</li>
<li>The API authenticates, rate‑limits, and checks a breach dataset. It returns per‑email status and counts (no breach contents).</li>
<li>Results are summarized in your dashboard and stored locally as scan logs. Breach contents remain user‑private on verisizintisi.com.</li>
</ol>
<h4>Language & translations</h4>
<ul>
<li>Text Domain: breach-radar (auto‑loaded from WordPress.org)</li>
<li>Bundled translations: English, Turkish. PO fallbacks provided for az_AZ and ru_RU under <code>wordpress/languages/</code>.</li>
<li>Plugin UI language can be forced at Breach Radar <span aria-hidden="true" class="wp-exclude-emoji">→</span> Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Language. Default is “Auto (Site language)”.</li>
<li>Language: English | Türkçe <span aria-hidden="true" class="wp-exclude-emoji">→</span> readme-tr_TR.txt</li>
</ul>
<h4>Data sent to the service</h4>
<ul>
<li>Site domain (host) to validate token usage</li>
<li>The email addresses you submit for lookup (transmitted for lookup; not persisted by the API)</li>
<li>Usage metadata (request time, status code, counters) for rate‑limiting and abuse prevention</li>
</ul>
<h4>Privacy and Terms</h4>
<ul>
<li>No tracking scripts are added to your WordPress frontend or admin.</li>
<li>Lookups only run when you initiate them or via your scheduled task. Visitors are not tracked.</li>
<li>Review: https://verisizintisi.com/privacy and https://verisizintisi.com/terms</li>
</ul>
<h4>Security model</h4>
<ul>
<li>Admin pages require <code>manage_options</code> capability.</li>
<li>All state‑changing actions use nonces (<code>check_admin_referer</code>).</li>
<li>Inputs sanitized and validated; outputs escaped (<code>esc_html</code>, <code>esc_attr</code>, <code>esc_url</code>, <code>wp_kses_post</code>).</li>
<li>HTTP host is derived via a safe helper instead of raw <code>$_SERVER</code>.</li>
</ul>
<h4>Consent</h4>
<p>Depending on your local laws and policies, you may need to inform users and/or obtain consent before checking their email addresses against breach datasets. This plugin provides the tools, but responsibility for lawful use remains with the site owner.</p>


Breach Radar via verisizintisi.com

Check your WordPress users’ emails against known breaches via verisizintisi.com and act on risks. Language: English | Türkçe → readme-tr_TR.txt

BREACH Avoider vs Breach Radar via verisizintisi.com