Skip to main content

Security report for atomicmaya.me

Technology · Switzerland

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

Security score

67/100

Risk levelMedium

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

AtomicMaya.me is a personal blog operated by Maya Boeckh, focusing on information security, development, OSINT, and personal interests. The site serves as a platform for sharing knowledge, community engagement, and professional insights, including Maya's roles as a community manager and university lecturer. The blog is well-positioned within the niche of infosec enthusiasts and developers, offering relevant and recent content that reflects active participation in the cybersecurity community. Technically, the website is built using Angular 14, employs modern web standards, and is hosted on GitHub Pages, ensuring reliable performance and good SEO practices. Security-wise, the site uses HTTPS and avoids exposing sensitive data, though it lacks advanced security headers and formal security policies. Privacy compliance is basic, with a privacy policy present but no cookie consent mechanism. Overall, the site is trustworthy, professionally maintained, and suitable for its target audience.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 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

6 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 Cookie Policy found

      GDPR requires clear information about cookie usage

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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

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

Keep watching atomicmaya.me

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. 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
95
Security headers
15
Email security
85
DNS health
55
Network security
100
GDPR outside view
53
Average
67

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 blog targets a specialized audience interested in cybersecurity, OSINT, and software development. It leverages community roles and academic involvement to build credibility and engagement. The business model is personal and community-driven rather than commercial, with no direct monetization evident. The presence of active social media links and participation in infosec communities indicates a strong network and potential for influence within its niche. The domain registration aligns with the stated origin, enhancing trust. Growth indicators include recent blog posts and conference participation. Partnerships are limited but include Digital Overdose, an infosec community. Strategic observations suggest opportunities to formalize security and privacy policies to enhance professional stature.

Security posture

The website demonstrates a moderate security maturity level. HTTPS is enforced, and no sensitive data leaks or vulnerable libraries are detected. However, the absence of security headers such as Content Security Policy, HSTS, and X-Frame-Options reduces the overall security posture. No incident response or vulnerability disclosure policies are present, which could be improved to handle potential security issues proactively. The lack of forms reduces attack surface but also limits user interaction. Compliance with GDPR is partial, with a privacy policy but no cookie consent. The security culture is evident through the author's professional background but could benefit from more explicit security documentation on the site.

Recommendations

  1. Implement standard security headers including CSP, HSTS, and X-Frame-Options to enhance protection against common web attacks.
  2. Add a cookie consent mechanism to comply with privacy regulations and improve user transparency.
  3. Publish a formal security policy and incident response contact information to demonstrate readiness and professionalism.
  4. Consider adding a vulnerability disclosure policy or security.txt file to encourage responsible reporting of security issues.
  5. Enhance accessibility features and conduct regular audits to improve user experience for all visitors.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
A personal blog by Maya Boeckh covering infosec, IoT, development, OSINT, CTFs, and personal topics.
Key services
Blog content on infosec, development, OSINT, CTFs, Community management at Digital Overdose, University lecturing
Content quality
good
Branding
consistent

Technology

Stack
Angular 14.2.1, FontAwesome 5.15.4, GoatCounter (commented out), Probable Catgirl outbound links script
Frameworks
Angular
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • No exposed sensitive data in HTML
  • No forms detected

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Personal blog with detailed 'whoami' page
  2. Active social media and community involvement
  3. No forms or direct contact emails visible
  4. No cookie consent or tracking scripts detected
  5. No security.txt or vulnerability disclosure policy found
  6. No explicit business or commercial activity
  7. Good use of modern web technologies and SEO metadata
  8. WHOIS data shows domain registered in Switzerland with privacy redaction
Technical notes

Notes

The site is a single-page application built with Angular 14.2.1, utilizing FontAwesome for icons and hosted on GitHub Pages. The performance is moderate with good SEO metadata and mobile optimization. No CMS is detected, indicating a custom-built solution. The technical stack is modern and well-maintained, though some commented-out analytics scripts suggest privacy-conscious choices. The lack of advanced analytics and tracking reduces data collection but also limits marketing insights. Technical risks are minimal, but the absence of security headers and formal policies represents areas for modernization and risk mitigation.
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 atomicmaya.me. 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 atomicmaya.me.

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.