Title: Computernørden&#039;s Security Panel
Author: Albert van Harten
Published: <strong>19 Jolay 2026</strong>
Last modified: 19 Jolay 2026

---

Search plugins

![](https://s.w.org/plugins/geopattern-icon/computernoerdens-security-panel.svg)

# Computernørden's Security Panel

 By [Albert van Harten](https://profiles.wordpress.org/albertvanharten/)

[Download](https://downloads.wordpress.org/plugin/computernoerdens-security-panel.1.0.7.zip)

 * [Details](https://mg.wordpress.org/plugins/computernoerdens-security-panel/#description)
 * [Reviews](https://mg.wordpress.org/plugins/computernoerdens-security-panel/#reviews)
 *  [Installation](https://mg.wordpress.org/plugins/computernoerdens-security-panel/#installation)
 * [Development](https://mg.wordpress.org/plugins/computernoerdens-security-panel/#developers)

 [Support](https://wordpress.org/support/plugin/computernoerdens-security-panel/)

## Description

Computernørden’s Security Panel helps you secure your WordPress site with clear,
guided tools — no deep technical knowledge required. Its Security Center shows how
well your site is protected and what to do next, in plain language.

**What it does**

 * **HTTPS & HSTS** — makes sure visitors always reach your site over an encrypted
   connection.
 * **Security headers** — switches on browser protections against framing, content-
   sniffing and referrer leaks.
 * **Content Security Policy builder** — a visual, per-directive editor with a safe
   Test mode, per-request nonces, hash allowlisting, and a violation log that helps
   you tighten the policy from real traffic without breaking your site.
 * **security.txt** — publishes and maintains a valid /.well-known/security.txt (
   RFC 9116), keeping the expiry date fresh automatically, with optional PGP-signed
   content.
 * **Readiness scanner** — checks common hardening settings (debug output, file 
   editing, upload execution and more) and offers one-click fixes where it’s safe
   to apply them.
 * **Infrastructure checks** — detects findings that live below WordPress (CAA DNS
   records, certificate key strength, HTTP compression, DANE) and explains exactly
   how to fix each in your own hosting environment.

The plugin aims for a clean result on public security scanners and gives self-contained,
environment-aware guidance for anything it cannot change directly.

### External services

This plugin performs security diagnostics by connecting to **your own website’s 
domain and public DNS records**. It does not send your data to any third-party company,
analytics service, or the plugin author. The connections exist only to measure how
your own site is configured, the same way an external scanner would, and they run
only when you open the plugin’s diagnostics/Security Center screen (or when the 
daily security.txt maintenance task runs).

Specifically:

 * **TLS probe** — the plugin makes HTTPS requests to your own site’s hostname to
   detect which TLS protocol versions your server accepts. The request goes to your
   domain only; the URL is your own site’s home URL. No request body or personal
   data is sent beyond a standard request and a plugin User-Agent string.
 * **Infrastructure checks** — the plugin queries public DNS records for your own
   domain (CAA and TLSA/DANE records via DNS), opens a TLS connection to your own
   domain to inspect its certificate, and makes one HTTPS request to your own site
   to check whether HTTP compression is enabled. All targets are your own domain.

Because every connection targets your own site and public DNS, there is no third-
party service, terms of service, or privacy policy involved. If your site is served
through a CDN or proxy (e.g. Cloudflare), these probes reach that provider’s edge,
as any external visitor’s would.

## Installation

 1. Upload the plugin files to the `/wp-content/plugins/computernoerdens-security-panel`
    directory, or install the plugin through the WordPress Plugins screen directly.
 2. Activate the plugin through the ‘Plugins’ screen in WordPress.
 3. Open the “Security” menu to see your Security Center and configure each module.

## FAQ

### Will this break my site?

The plugin is designed to be safe. The Content Security Policy has a Test mode that
watches without blocking, so you can confirm what your site needs before enforcing
anything. Settings changes are reversible, and wp-config edits create a timestamped
backup first.

### Does it require any paid service or external account?

No. The plugin is fully functional on its own and does not require any account or
subscription.

### It flagged something it says it cannot fix. What now?

Some security findings live in DNS, your TLS certificate, or your web server — below
the level a WordPress plugin can change. For those, the plugin detects the finding
and gives step-by-step guidance for your specific hosting environment.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“Computernørden's Security Panel” is open source software. The following people 
have contributed to this plugin.

Contributors

 *   [ Albert van Harten ](https://profiles.wordpress.org/albertvanharten/)

[Translate “Computernørden's Security Panel” into your language.](https://translate.wordpress.org/projects/wp-plugins/computernoerdens-security-panel)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/computernoerdens-security-panel/),
check out the [SVN repository](https://plugins.svn.wordpress.org/computernoerdens-security-panel/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/computernoerdens-security-panel/)
by [RSS](https://plugins.trac.wordpress.org/log/computernoerdens-security-panel/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 1.0.7

 * Replaced the direct curl calls in the TLS probe with the WordPress HTTP API (
   wp_remote_get + the http_api_curl hook for TLS-version pinning).
 * Documented the plugin’s self-directed diagnostic connections in a new “External
   services” readme section.
 * Made the security.txt web-root path filterable (cno_security_web_root) and documented
   why the web root is the correct location per RFC 9116.

#### 1.0.6

 * Set a distinct Plugin URI (plugin page) separate from the Author URI.

#### 1.0.5

 * Removed the duplicate Plugin URI header (kept the Author URI) to satisfy WordPress.
   org submission requirements.

#### 1.0.4

 * Made the nonce verification in the settings-reading helper visible to static 
   analysis as well. Resolves the last code-standards warnings.

#### 1.0.3

 * Made AJAX nonce verification visible to static analysis (inline check_ajax_referer
   in each handler) and added full input sanitization for the settings payload. 
   No functional change; resolves the remaining code-standards warnings.

#### 1.0.2

 * WordPress.org compliance pass. Renamed to remove the restricted word “plugin”
   from the name and slug. Replaced unlink() with wp_delete_file(); added wp_unslash()/
   sanitize_text_field() to all $_SERVER/$_POST reads; documented the deliberate
   direct-curl (TLS-version probing), direct-filesystem (wp-config editing) and 
   central-nonce (authorize()) patterns with justified phpcs:ignore annotations;
   marked template-scoped variables. Bumped “Tested up to” to 7.0.

#### 1.0.1

 * Fixed a fatal error on activation caused by relying on a Composer autoloader 
   that isn’t shipped. The plugin now uses a self-contained PSR-4 autoloader and
   bundles no external dependencies.

#### 1.0.0

 * First public release: HTTPS/HSTS, security headers, Content Security Policy builder
   with Test mode, nonces, hashes and violation logging, security.txt with auto-
   renewing expiry and optional PGP signing, readiness scanner with one-click fixes,
   infrastructure checks with environment-aware guidance, and a plain-language Security
   Center dashboard.

## Meta

 *  Version **1.0.7**
 *  Last updated **2 andro ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 6.5 or higher **
 *  Tested up to **7.0.2**
 *  PHP version ** 7.0 or higher **
 *  Language
 * [English (US)](https://wordpress.org/plugins/computernoerdens-security-panel/)
 * Tags
 * [content security policy](https://mg.wordpress.org/plugins/tags/content-security-policy/)
   [hardening](https://mg.wordpress.org/plugins/tags/hardening/)[https](https://mg.wordpress.org/plugins/tags/https/)
   [security](https://mg.wordpress.org/plugins/tags/security/)[Security Headers](https://mg.wordpress.org/plugins/tags/security-headers/)
 *  [Advanced View](https://mg.wordpress.org/plugins/computernoerdens-security-panel/advanced/)

## Ratings

Mbola tsy misy domberina voaray hatreto.

[Your review](https://wordpress.org/support/plugin/computernoerdens-security-panel/reviews/#new-post)

[Hijery ny  domberina rehetra](https://wordpress.org/support/plugin/computernoerdens-security-panel/reviews/)

## Contributors

 *   [ Albert van Harten ](https://profiles.wordpress.org/albertvanharten/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/computernoerdens-security-panel/)