Boon Band

BoonRisk gives you a clear security and readiness report for your WordPress site. See exactly what security risks exist, why they matter, and what to do about them — all explained in plain language.
Safe & Read-Only: This plugin only reads your site configuration. It does not scan files, block traffic, or make any changes to your WordPress installation.
<h4>What You Get</h4>
<ul>
<li>Security Check Report — See your site’s security status: PHP version, WordPress updates, user settings, HTTPS, and 30+ configuration checks</li>
<li>Clear Explanations — Every finding explains “why this matters” and “what to do about it” in plain language</li>
<li>Prioritized Risks — Top risks ranked by impact so you know what to fix first</li>
<li>Printable Report — Professional HTML report you can view, print, or share directly from WordPress admin</li>
</ul>
<h4>What This Plugin Does NOT Do (100% Safe)</h4>
<ul>
<li>No file scanning — Does not scan your files or look for malware</li>
<li>No traffic blocking — Does not act as a firewall or block visitors</li>
<li>No site changes — Does not modify settings, files, or database</li>
<li>No active testing — Does not simulate attacks or run security scans</li>
<li>Read-only analysis — Only reads your configuration, never writes or changes anything</li>
</ul>
<h4>Who Is It For?</h4>
<ul>
<li>Site owners — Understand your security risks without technical expertise</li>
<li>Freelancers & agencies — Generate client-ready reports in minutes</li>
<li>Developers — Quick baseline check before or after deployments</li>
<li>Teams — Consistent security reporting across multiple WordPress sites</li>
</ul>
<h4>Free Security Check (No Account Required)</h4>
Run a complete security and readiness check instantly — 100% local, no data sent anywhere:
<ul>
<li>Overall Risk Level — Clear Low/Medium/High rating with explanation of what it means</li>
<li>Top Risks First — See your biggest security issues ranked by impact</li>
<li>30+ Configuration Checks — WordPress updates, PHP version, HTTPS, user permissions, backups, 2FA, debug mode, and more</li>
<li>Action Plan — Every issue includes “why it matters” and “how to fix it”</li>
<li>Professional Report — Printable HTML report you can view in WordPress admin or share with your team</li>
</ul>
What you’ll learn: “Is my site at risk?” and “What should I fix first?”
100% Private: All checks run on your server. Nothing is sent externally. No account or email required.
<h4>Optional: Web Dashboard</h4>
Connect the plugin to the <a href="https://boonrisk.com/" rel="nofollow ugc">BoonRisk web dashboard</a> for additional capabilities (optional, requires free account):
<ul>
<li><a href="https://boonrisk.com/scanner/" rel="nofollow ugc">Surface Scan</a> — External scan of your site’s public-facing security headers, SSL configuration, and exposed services</li>
<li>Vulnerability Intelligence — Known CVEs matched to your installed plugins and themes with severity ratings</li>
<li>Continuous Monitoring — Automatic daily checks with alerts when your security posture changes</li>
<li>Track Over Time — See how your site security improves (or changes) month over month</li>
<li>PDF Reports — Download professional reports to share with clients or management</li>
</ul>
Note: The local security check is fully functional on its own. The web dashboard is completely optional.
Learn more at <a href="https://boonrisk.com/" rel="nofollow ugc">boonrisk.com</a>
<h3>How It Works</h3>
<h4>Local Assessment (Default)</h4>
<ol>
<li>Install and activate the plugin</li>
<li>Go to BoonRisk → Local Assessment</li>
<li>Click Run Assessment Now</li>
<li>View your Security Posture Summary and Top Risks</li>
<li>Click View Full Report for a printable HTML report</li>
</ol>
All analysis happens on your server. Nothing is sent externally.
<h4>Web Dashboard (Optional)</h4>
<ol>
<li>Create a free account at <a href="https://boonrisk.com/" rel="nofollow ugc">boonrisk.com</a></li>
<li>Go to BoonRisk → Connect (Optional)</li>
<li>Enter your API key</li>
<li>Send your assessment to the dashboard for vulnerability intelligence, surface scan, and monitoring</li>
</ol>
External API calls only happen when you explicitly request them.
<h3>Data Usage</h3>
<h4>Local Assessment</h4>
In local mode, no data is sent externally. All checks run inside WordPress.
<h4>Web Dashboard (Optional)</h4>
When you send data to the dashboard, the following is transmitted:
<ul>
<li>PHP and WordPress versions</li>
<li>Active plugin and theme names/versions</li>
<li>Configuration flags (debug mode, file editor status, etc.)</li>
</ul>
What you get in return:
<ul>
<li>Known vulnerability data for your installed plugins and themes</li>
<li>Surface scan results for public-facing security</li>
<li>Severity context for identified risks</li>
<li>Historical trend data and monitoring alerts</li>
</ul>
What is never collected:
<ul>
<li>User data or personal information</li>
<li>Passwords or credentials</li>
<li>Post/page content</li>
<li>Database contents</li>
<li>File contents</li>
</ul>
Data is sent only when you click Send to Dashboard or enable automatic daily sync. No personal data is collected.
<h3>Privacy Policy</h3>
Read our full privacy policy at https://boonrisk.com/privacy

BoonRisk – Site Security Check & Report

Security posture report for WordPress — 30+ checks, prioritized risks, and a printable report. Get a clear picture in minutes.

shasha310

Harden your web applications.
HTTP header fields are components of the header section of request and response messages. The headers define the operating parameters of an HTTP transaction.
Securing HTTP headers will improve the resilience of your web application against many common attacks including those that are on the OWASP top 10 list.
Securing headers can also improve your SEO rank and in addition to preventing websites from being marked as dangerous by browsers and antivirus applications.
Protect sensitive user information and be compliant with privacy regulations. Defend users from stealing private data by protecting website cookies. Use the proper directive such as “secure”, “httponly” and “samesite”, all of those will be applied automatically by “Secure HTTP Headers” plugin.
Secure HTTP Headers will automatically analyze any website and will build up secure headers directives, by the latest best practice.
In addition, Secure HTTP Headers offers fully configurable options, apply or skip any header directive as needed.
Install and activate Secure HTTP Headers with full confidence, the deactivation of this plugin will return your website header directives to their original state.
<h3>Main plugin functionality</h3>
<ol>
<li>
HTTP Strict Transport Security – helps to protect websites against man-in-the-middle attacks and cookie hijacking
</li>
<li>
X-Frame-Options – helps to protect users against ClickJacking attacks
</li>
<li>
X-Content-Type-Options – helps to prevent the browser from MIME-sniffing
</li>
<li>
Referrer-Policy – helps to control how much referrer information should be included with requests
</li>
<li>
Clear-Site-Data – helps to ensure that data is deleted from the browser if the user logs out
</li>
<li>
X-Download-Options – helps to control how IE 8 will handle downloaded HTML files
</li>
<li>
Access-Control-Allow-Origin – helps to ensure whether the response can be shared with requesting code from the given origin
</li>
<li>
Cross-Origin-Embedder-Policy – helps to prevent a document from loading any cross-origin resources that don’t explicitly grant the document permission
</li>
<li>
Permissions-Policy – helps to allow and deny the use of browser features in its own frame, and in content within any iframe elements in the document
</li>
<li>
Cross-Origin-Opener-Policy – helps to protect websites against a set of cross-origin attacks dubbed XS-Leaks
</li>
<li>
Cross-Origin-Resource-Policy – helps to protect websites against speculative side-channel attacks, like Spectre, as well as Cross-Site Script Inclusion attacks
</li>
<li>
X-Permitted-Cross-Domain-Policies – helps to control how cross-domain requests from Flash and PDF documents are handled
</li>
<li>
Cookie Http-Only flag – helps to protect websites against Cross-Site Scripting, or XSS attacks
</li>
<li>
Cookie Secure flag – helps to ensure that cookie is sent over a secure connection
</li>
<li>
Cookie Samesite Lax flag – helps to protect websites against CSRF and XSSI attacks
</li>
<li>
Expect-CT – helps to prevent the use of misissued certificates for a website. Note: The Expect-CT will likely become obsolete in June 2021
</li>
</ol>
<h3>What are the optional extras?</h3>
Magnisec is offering “Secure HTTP Headers enhanced”
A plugin that contains, in addition, an engine that watches and builds in any website changes a CSP – Content Security Policy that is best practice and recommended by all professional securities experts, that mitigate XSS -Cross site Scripting, one of the most common and destructive attacks.
Price: 50$ /year for a domain.
More details and installation <a href="https://magnisec.com" rel="nofollow ugc">here</a>

Secure HTTP Headers

Secure HTTP headers - Essential, and easy.

BoonRisk – Site Security Check & Report vs Secure HTTP Headers