Skip to main content

Security report for buh.moe

Private by Design, LLC · Technology · United States

Medium risk. 7 critical or high findings in Email security, Security headers and 2 other checks.

Security score

65/100

Risk levelMedium

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

The website buh.moe is a personal portfolio and blog site owned by Alex, a 21-year-old student from Poland with interests in programming, front-end development, UI design, and video games. The site serves as a personal hub showcasing the owner's projects, blog posts, and social media presence. It targets a general audience interested in technology and gaming. The domain is newly registered in December 2024 and uses privacy protection services, which is typical for personal websites. Technically, the site is built using the Astro framework (v5.1.0) and hosted on Vercel, leveraging modern web technologies including Font Awesome icons and Vercel's analytics and speed insights tools. The site is well-optimized for performance and mobile devices, with good SEO practices evident from meta tags and Open Graph data. However, accessibility features are basic, and no CMS is detected. From a security perspective, the site uses HTTPS with a good SSL configuration and domain status protections to prevent unauthorized transfers or deletions. However, DNSSEC is not enabled, and no security headers such as Content-Security-Policy or X-Frame-Options are present. There are no visible vulnerabilities or exposed sensitive data, but the absence of privacy and cookie policies and incident response information indicates room for improvement in compliance and security posture. Overall, the website is safe, professional, and trustworthy for a personal site, with no adult or explicit content detected. Strategic recommendations include enabling DNSSEC, adding security headers, publishing privacy and cookie policies, and providing incident response contacts to enhance trust and compliance.

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. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

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

  3. 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 buh.moe

This scan found 24 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
72
Security headers
30
Email security
60
DNS health
75
Network security
100
GDPR outside view
50
Average
65

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

The website operates as a personal brand platform for an individual rather than a commercial business. It occupies a niche market position as a personal blog and portfolio, targeting technology enthusiasts and gamers. The business model is non-commercial, focusing on content sharing and personal expression. Revenue streams are not evident, though a Ko-fi support link suggests voluntary donations. The site benefits from a network of partner sites and friends linked via buttons, indicating a community-oriented approach. Growth indicators are limited due to the site's recent creation. The use of privacy protection for domain registration is standard for personal sites. The partnership ecosystem includes various personal and community websites, enhancing visibility and networking.

Security posture

The security maturity of the website is moderate. HTTPS is enforced, and domain registration includes clientDeleteProhibited and clientTransferProhibited statuses, which are positive security indicators. However, the lack of DNSSEC and security headers reduces the overall security posture. No privacy or cookie policies are present, which is a compliance gap under GDPR and similar regulations. Incident response readiness is not demonstrated, with no security or abuse contact information provided. The site does not expose sensitive data or use vulnerable libraries based on the analysis. The security culture appears informal, consistent with a personal website. Enhancing security headers, enabling DNSSEC, and publishing compliance documents would improve the security maturity significantly.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement and publish privacy and cookie policies to comply with GDPR and enhance user trust.
  3. Add essential security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options to mitigate common web vulnerabilities.
  4. Provide incident response and abuse contact information to facilitate security issue reporting and response.
  5. Consider improving accessibility features to enhance usability for all users.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Private by Design, LLC
Description
Personal website of Alex, a 21-year-old student from Poland interested in programming, front-end development, UI design, and video games.
Key services
Blogging, Portfolio showcase, Personal interests sharing
Content quality
good
Branding
consistent

Technology

Stack
Astro v5.1.0, Font Awesome 6.7.2, Vercel Analytics, Vercel Speed Insights
Frameworks
Astro
Platforms
Vercel
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • Domain status includes clientDeleteProhibited and clientTransferProhibited

Analytics and tracking

Services
Vercel Analytics
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Vercel Analytics
Marketing tools
Vercel Speed Insights
Transparency
basic

Site quality

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

Key observations

  1. Personal website with clear owner identity and social media presence
  2. No privacy, cookie, or terms of service policies found
  3. No contact emails or phone numbers explicitly listed
  4. Modern tech stack with Astro and Vercel hosting
  5. Good performance and mobile optimization
  6. No security headers detected, DNSSEC not enabled
  7. No signs of adult or explicit content
  8. No WAF or blocking mechanisms detected
Technical notes

Notes

The website is built on a modern static site framework, Astro v5.1.0, and hosted on Vercel, which provides fast performance and scalability. The use of Font Awesome 6.7.2 ensures rich iconography. The site includes Vercel Analytics and Speed Insights scripts for performance monitoring and user analytics. The HTML is well-structured with proper meta tags and Open Graph data for SEO and social sharing. Mobile optimization is good, and the site loads quickly. There is no CMS detected, indicating a static site approach. Technical risks include the absence of DNSSEC and security headers, which could expose the site to DNS attacks and certain web-based threats. The site does not appear to have technical debt or legacy technology issues. Overall, the technical infrastructure is modern and well-maintained.
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 buh.moe. 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 buh.moe.

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.