Skip to main content

Security report for commanderzero.com

Commander Zero · Other · N/a

High risk. 11 critical or high findings in Network security, Security headers and 2 other checks.

Security score

44/100

Risk levelHigh

0–100, higher is better. How it is calculated

CommanderZero.com is a personal blog established in 2003, focusing on preparedness, survivalism, firearms, and related logistics topics. The site serves a niche audience of survival enthusiasts and firearm owners, providing detailed articles, reviews, and observations. The business model appears to be content publishing supported by community engagement and Patreon donations. Technically, the site runs on WordPress hosted by Bluehost, utilizing modern web technologies and Google Analytics for visitor tracking. The site is moderately optimized for mobile and accessibility but lacks comprehensive privacy and cookie policies, which are compliance gaps. Security posture is adequate with HTTPS enabled and domain transfer protections, but missing advanced security headers and vulnerability disclosures. Overall, the domain age and registration data support the site's legitimacy and stable presence. Strategic improvements in privacy compliance and security practices would enhance trust and reduce risk.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

11 findings rated critical or high. Fix these first.

  1. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: MySQL

      Port 3306 (MySQL) is publicly accessible - MySQL - Database server

      What to do: Immediately restrict access to MySQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
    • Critical

      Critical Service Exposed: PostgreSQL

      Port 5432 (PostgreSQL) is publicly accessible - PostgreSQL - Database server

      What to do: Immediately restrict access to PostgreSQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

  2. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

Need hands-on remediation? Email guard@offseq.com

Keep watching commanderzero.com

This scan found 30 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. The full timeline opens with your unlock code.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
62
Security headers
15
Email security
75
DNS health
75
Network security
0
GDPR outside view
35
Average
44

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet · found on this site
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

The website occupies a niche market serving survivalists and preparedness enthusiasts, leveraging a blog format to share knowledge and experiences. Its competitive advantage lies in long-term domain presence and consistent content production. Revenue streams likely include Patreon support and possibly affiliate links, though no direct e-commerce is evident. The target customer segment is mature adults interested in self-reliance and emergency readiness. The site maintains a modest but engaged community, as evidenced by active comments and Patreon integration. Partnerships or subsidiaries are not evident. The site’s operations are lean, focusing on content quality and community engagement rather than commercial expansion.

Security posture

The site demonstrates a basic to moderate security maturity level. HTTPS is enforced, and domain registration includes clientTransferProhibited status, reducing hijacking risk. However, the absence of DNSSEC, Content-Security-Policy headers, and a published security.txt file indicates room for improvement. No incident response contacts or vulnerability disclosure policies are present, which could hinder timely security issue resolution. The use of Google Analytics and Tag Manager introduces moderate tracking but no apparent privacy safeguards. Overall, the security posture is functional but lacks advanced protections and transparency.

Recommendations

  1. Publish a comprehensive privacy policy and cookie policy with GDPR compliance considerations.
  2. Implement security headers such as Content-Security-Policy, X-Content-Type-Options, and Referrer-Policy.
  3. Enable DNSSEC on the domain to enhance DNS security.
  4. Create and publish a security.txt file to facilitate vulnerability reporting and incident response.
  5. Add clear contact information including security and abuse contacts to improve trust and compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Commander Zero
Description
A personal blog focused on preparedness, survivalism, firearms, logistics, and related topics. The site features articles, reviews, and observations primarily about gear, guns, water storage, precious metals, and real estate related to survival and preparedness.
Key services
Blog content publishing, Information sharing on preparedness and survival, Community engagement via comments, Patreon support for content creation
Content quality
good
Branding
moderate

Technology

Stack
WordPress 6.8.3, PHP, Google Analytics, Google Tag Manager, MediaElement.js, IntersectionObserver API, CSS3, HTML5
Frameworks
WordPress
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
65/100
Good practices seen
  • HTTPS enabled
  • ClientTransferProhibited domain status
  • No DNSSEC enabled (recommend enabling)

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
poor

Advertising

Marketing tools
Patreon widget
Transparency
basic

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
moderate

Key observations

  1. Website is a personal blog focused on survivalism and preparedness.
  2. No privacy or cookie policies found, which is a compliance gap.
  3. Uses WordPress CMS hosted on Bluehost.
  4. Google Analytics and Tag Manager used for tracking.
  5. No security.txt or vulnerability disclosure found.
  6. No explicit contact emails or phone numbers found; contact form present.
  7. No adult or explicit content detected.
  8. Domain is old and stable, indicating legitimacy.
  9. No WAF or blocking detected; content fully accessible.
Technical notes

Notes

The website is built on WordPress 6.8.3, hosted by Bluehost, and uses standard web technologies including HTML5, CSS3, and JavaScript. It integrates Google Analytics and Google Tag Manager for visitor tracking. The site loads moderately fast and is mobile optimized with basic accessibility features. The theme used is 'twentyeleven' with custom styles. No major technical debt or deprecated libraries were detected. However, the site lacks advanced SEO meta tags and structured data beyond basic WordPress defaults. Performance could be improved with caching and CDN usage. Security headers are minimal, and DNSSEC is not enabled, representing technical risks. Overall, the infrastructure is stable but could benefit from modernization and enhanced security configurations.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with commanderzero.com. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review commanderzero.com.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.