Skip to main content

Security report for mrbruh.com

Technology · New Zealand

Medium risk. 7 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

53/100

Risk levelMedium

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

MrBruh.com is a personal blog operated by Paul, a young programmer and aspiring cybersecurity professional from New Zealand. The site focuses on sharing technical blog articles related to cybersecurity vulnerabilities, malware analysis, and programming insights. The blog targets gamers and cybersecurity enthusiasts, providing niche content in the technology sector. The website is built using the Hugo static site generator and hosted by Privex, with DNS managed via Cloudflare. The domain is registered with Tucows Domains Inc. and is relatively new, consistent with the stated founding year of 2023. Technically, the website is well-structured with good mobile optimization and accessibility. However, it lacks advanced SEO optimization and security headers. The site uses HTTPS but does not enable DNSSEC, and no privacy or cookie policies are present. There are no analytics or tracking scripts detected, indicating minimal user tracking. Contact information is provided via email and Signal, but no forms or other data collection mechanisms are present. From a security perspective, the site benefits from domain transfer protections but lacks important security headers and DNSSEC, which could improve its security posture. No vulnerabilities or exposed sensitive data were detected in the content. The absence of privacy and cookie policies indicates non-compliance with GDPR and other privacy regulations. Overall, the site is safe for general audiences and does not contain adult or explicit content. The overall risk is low given the personal blog nature, but improvements in security headers, privacy compliance, and DNS security are recommended to enhance trust and protection against potential threats.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
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

7 findings rated critical or high. Fix these first.

  1. 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';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

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

Keep watching mrbruh.com

This scan found 23 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. See sample alerts.

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
75
Security headers
15
Email security
70
DNS health
70
Network security
40
GDPR outside view
50
Average
53

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
  • 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

MrBruh.com operates as a personal blog in the cybersecurity and programming niche, targeting a specialized audience of gamers and tech enthusiasts. The business model is content-driven without evident monetization or commercial services. The site’s market position is that of a niche personal blog with a focus on technical cybersecurity disclosures and educational content. The blog’s growth potential depends on content quality and community engagement. There are no visible partnerships or subsidiaries. The domain registration and hosting choices reflect a small-scale operation with moderate technical infrastructure. The lack of advertising and tracking tools suggests a privacy-conscious approach or minimal commercial intent.

Security posture

The website demonstrates a basic security posture with HTTPS enabled and domain transfer protections in place. However, the absence of DNSSEC and security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options reduces its defense-in-depth capabilities. No incident response or vulnerability disclosure policies are published, which limits transparency and preparedness. The site does not collect user data via forms or analytics, reducing attack surface but also limiting user engagement insights. Compliance with GDPR and other privacy regulations is lacking due to missing privacy and cookie policies. Overall, the security maturity is low to moderate, suitable for a personal blog but requiring enhancements for professional or commercial use.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement standard security headers (CSP, X-Frame-Options, X-Content-Type-Options) to mitigate common web attacks.
  3. Publish a privacy policy and cookie policy to comply with GDPR and enhance user trust.
  4. Consider adding a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  5. Add basic analytics with privacy-respecting configurations to understand user engagement while maintaining minimal tracking.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
A personal blog by Paul, a 21-year-old programmer from New Zealand, focusing on cybersecurity topics and technical write-ups.
Key services
Blog articles on cybersecurity and programming, Technical vulnerability disclosures
Content quality
good
Branding
consistent

Technology

Stack
Hugo 0.111.3, Cloudflare DNS
Performance
moderate
Mobile
good
Accessibility
good
SEO
basic

Security

Observed score
60/100
Good practices seen
  • HTTPS enabled
  • Domain status includes clientTransferProhibited and clientUpdateProhibited

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a personal cybersecurity blog by an individual named Paul from New Zealand.
  2. No privacy, cookie, or terms of service policies found.
  3. Contact information includes an email and Signal handle.
  4. No forms or data collection mechanisms detected.
  5. No analytics or tracking scripts detected.
  6. Website uses Hugo static site generator and is hosted by Privex.
  7. No security headers detected in HTML content; DNSSEC not enabled.
  8. Domain is registered for a long term (until 2034) with Tucows and uses Cloudflare DNS.
  9. Content is safe and suitable for general audiences.
  10. No advertising or marketing tools detected.
Technical notes

Notes

The website is built using the Hugo static site generator, which provides a lightweight and performant platform. Hosting is provided by Privex, and DNS is managed via Cloudflare, ensuring reliable infrastructure. The site uses modern HTML5 and CSS with responsive design for good mobile compatibility. However, SEO optimization is basic, with empty meta description and Open Graph tags, which could be improved for better search engine visibility and social media sharing. No JavaScript frameworks or analytics scripts are detected, indicating minimal technical complexity but also limited interactivity and tracking. The domain registration is long-term and stable, with transfer protections enabled. Overall, the technical implementation is solid for a personal blog but could benefit from enhanced SEO and 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 mrbruh.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 mrbruh.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.