by rimbeplus 0 (0 reviews)

Beplus Security Headers & Script Auditor

Name: Beplus Security Headers & Script Auditor
Author: rimbeplus

Enable common HTTP security headers, scan your site for external scripts/styles, and pick your own Content-Security-Policy rules.

Beplus Security Headers & Script Auditor ranks #70,421 among WordPress.org plugins with 0+ active installations, is #3,855 of 5,058 in the Security category, and was last updated Oct 18, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.4

v1.1.0 Current Version v1.1.0

Updated 2 weeks ago Last Update on 18 Oct, 2026

Refreshed 2 days ago Last Refreshed on

#3,855 of 5,058 in Security Downloads -75% this week Actively maintained

View on WordPress.org

Rank

#70,421

— No change

Active Installs

-100%

KW Avg Position

2 worse

Downloads

327

+1 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 10

Total Progress 0%

0+ 10+

42,853

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 10 more installs to reach 10+

Rank Changes

Current #70,421

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0

0 reviews

Overall 0%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.1.0
Last Updated: Oct 18, 2026
Requires WP: 6.0+
Tested Up To: 7.1.4
PHP Version: 7.4 or higher
Author: rimbeplus

Support & Rating

Rating: ☆ ☆ ☆ ☆ ☆ 0
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

content security policy csp headers http-headers security

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,757

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

Akismet Anti-spam: Spam Protection

5M+ installs

Wordfence Security – Firewall, Malware Scan, and Login Security

5M+ installs

#11

Really Simple Security – Simple and Performant Security (formerly Really Simple SSL)

Limit Login Attempts Security - Login Security, 2FA, Firewall, Brute Force Prevention

View all Security-and-spam-protection plugins

Frequently Asked Questions

Common questions about Beplus Security Headers & Script Auditor

It can, especially Content-Security-Policy. Start with the scanner recommendations, use "Report-only mode" for CSP first to observe without blocking anything, and only switch to enforcing mode once you've confirmed the policy covers everything your site actually loads.

No. It performs normal HTTP requests from your own server to pages on your own site, using the built-in WordPress HTTP API. Nothing is sent to any third party.

Click "Check live headers" on the Headers tab. If headers are missing, a page cache, CDN or your web server is usually serving the page without going through WordPress — clear the cache, or add the headers in your server/CDN configuration. If a header is shown as overridden or sent twice, it's also being set somewhere else (server, CDN or another plugin); set each header in only one place.

Yes, by default (since 1.1.0): every header except Content-Security-Policy and X-Frame-Options is also sent on wp-admin, the login page, admin-ajax and the REST API. CSP is left out because it could break the block editor and other admin screens, and WordPress already protects these pages from being framed. You can turn this off on the Headers tab.

Enable Content-Security-Policy in report-only mode and tick "Collect violation reports". Browsers then report anything your policy would block to your own site, and the CSP Reports tab lists each blocked resource with an "Add to policy" button. Browser extensions can trigger reports too, so only add sources you recognise. Counts are approximate under heavy traffic. On HTTPS sites, Chromium-based browsers use the Reporting API, which can delay reports by up to a minute.

No. Even the whole-site option only scans your homepage plus your most recently published posts/pages (capped at 200) and is meant as a starting point for building a Content-Security-Policy, not a substitute for a complete security review of your site.