Breach Radar for WordPress
Monitor whether your users' email addresses appear in known data breaches. Results are summarized in your WordPress dashboard — breach contents are never exposed.
| Status | ● Active |
| Current Version | 1.0.2 |
| WordPress | 5.6 or higher |
| Tested Up To | 6.8.1 |
| PHP | ≥ 7.2 |
| Software License | GPL v2+ |
| Languages | English, Turkish · PO files for Azerbaijani, Russian |
| Author | Veri Sızıntısı |
Features
- Dashboard overview with risk summary and insights
- Manual and scheduled scans (daily)
- Scan logs with filters — email, status, HTTP code, date range
- Admin notifications when breach count increases (configurable threshold)
- Protection badge via shortcode or Theme Customizer
- First-run Setup Wizard with API key connectivity test
- Multilingual: English and Turkish bundled, Azerbaijani and Russian via PO files
How It Works
Get a license key
Go to /get/wordpress/breach-radar and enter your email and domain. A license key will be sent to your email.
Install & activate
In WordPress admin, go to Plugins → Add New → Upload Plugin, select the ZIP, install and activate. Or search "Breach Radar" in the plugin directory.
Paste your license key
Go to Breach Radar → Settings in your admin panel and paste your key. The Setup Wizard will guide you through the process.
Scan
Start a manual scan or enable daily automatic scans. The plugin sends user emails over HTTPS to the API, which returns presence and count data — no breach contents.
Data & Privacy
| Data sent | Purpose |
|---|---|
| Site domain (host) | Validates license key usage against the registered domain |
| Email addresses | Transmitted for breach lookup — not stored by the API |
| Usage metadata | Request time, status code, counters for rate-limiting and abuse prevention |
- No tracking scripts added to your frontend or admin
- Lookups only run when initiated by you or via scheduled task — visitors are not tracked
- Breach contents remain user-private on verisizintisi.com
- Admins see presence and counts only, never actual breach data
Security
- Admin pages require
manage_optionscapability - All state-changing actions use WordPress nonces
- Inputs sanitized and validated; outputs escaped with
esc_html,esc_attr,esc_url,wp_kses_post - HTTP host derived via safe helper instead of raw
$_SERVER - Database queries use
$wpdb->prepare()with placeholders
Protection Badge
Display a protection badge on your site to show visitors that you monitor for breaches.
[verisizintisi_badge size="medium" theme="light" align="left" lang="auto"]
Also available via Appearance → Customize → Breach Radar Badge.
Changelog
1.0.2
- Added first-run Setup Wizard (activation redirect, two-step flow)
- API key connectivity test with clear status; daily scan toggle
- Admin notice until setup is completed
- Fixed redirects by processing setup via admin-post
- Minor UX copy and layout improvements
1.0.1
- Security improvements for Plugin Check compliance
- Replaced raw $_SERVER usage with safe helper
- Escaped all flagged outputs
- Self-healing scheduling for daily scans
- i18n fixes, updated POT/PO files
1.0.0
- Initial stable release: risk summary, insights, daily scan, log filters, notifications, badge page
Consent Notice
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.