Skip to main content

Security report for isabelroses.com

Technology · N/a

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

Security score

72/100

Risk levelMedium

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

The website is a personal portfolio and blog of a computer science student and open source contributor named Isabel Roses. It documents her development journey, contributions to open source projects such as Nixpkgs and Catppuccin themes, and showcases her projects. The site targets developers and tech enthusiasts interested in programming and open source software. The business model is personal branding and community engagement through blogging and project maintenance. The site is small scale and founded recently in 2023. Technically, the site is built using the Astro static site generator (version 5.8.0) with client-side JavaScript for theme switching. It uses Cloudflare DNS servers but does not have DNSSEC enabled. The site loads quickly, is mobile optimized, and has good SEO metadata. Analytics are self-hosted, indicating some privacy consideration. However, no CMS or hosting provider is explicitly identified. From a security perspective, the site uses HTTPS and domain registration includes protective statuses against unauthorized deletion or transfer. However, DNSSEC is not enabled, and no security headers are detected in the HTML content. There are no privacy or cookie policies, no contact information, and no vulnerability disclosure or security.txt files. These gaps reduce compliance and security posture scores. Overall, the site is trustworthy and legitimate as a personal project with good technical quality but lacks formal privacy and security documentation. Strategic improvements include adding privacy and cookie policies, enabling DNSSEC, implementing security headers, and providing contact information for incident response.

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

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

    • 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 isabelroses.com

This scan found 19 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
75
Security headers
40
Email security
80
DNS health
85
Network security
100
GDPR outside view
50
Average
72

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 represents an individual personal brand focused on software development and open source contributions. The market positioning is niche, targeting the open source and developer community. The business model is non-commercial, centered on content sharing and project maintenance. Revenue streams are not evident, suggesting a hobby or portfolio site. The target customer segment includes computer science students, developers interested in Nix, Rust, Go, and theming. Growth indicators include active GitHub repositories and blog updates. The partnership ecosystem includes open source projects like Nixpkgs and Catppuccin. Strategic observations note the importance of maintaining transparency and improving compliance to enhance credibility.

Security posture

The security maturity level is moderate. HTTPS is enforced, and domain registration includes clientDeleteProhibited and clientTransferProhibited statuses, which protect domain integrity. However, the absence of DNSSEC, security headers, privacy policies, and incident response contacts indicates gaps in security best practices. No vulnerabilities or exposed sensitive data were detected in the HTML content. Compliance with GDPR or other regulations is not demonstrated. The site lacks formal mechanisms for vulnerability disclosure or incident reporting. Overall, the security culture appears informal, consistent with a personal site, but could benefit from adopting standard security and privacy frameworks.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement and publish a comprehensive privacy policy and cookie policy with consent mechanisms to improve GDPR compliance.
  3. Add standard security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to harden the site against common attacks.
  4. Provide clear contact information, including a security or abuse email address, to facilitate incident response and vulnerability reporting.
  5. Consider publishing a security.txt or vulnerability disclosure policy to encourage responsible security communication.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
A personal website documenting the development journey of a computer science student and open source contributor.
Key services
blog content, open source project maintenance, theme development
Content quality
good
Branding
consistent

Technology

Stack
Astro v5.8.0, JavaScript (ES Modules), Cloudflare DNS, Custom CSS, Client-side theme switching
Frameworks
Astro
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced (implied by canonical URL https://)
  • Domain status includes clientDeleteProhibited and clientTransferProhibited

Analytics and tracking

Services
analytics.isabelroses.com (self-hosted analytics)
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
analytics.isabelroses.com
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 and project portfolio of a computer science student and open source contributor.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact emails or phone numbers explicitly provided.
  4. Uses modern static site generator Astro with client-side theme switching.
  5. Self-hosted analytics script used, indicating some privacy awareness.
  6. No security.txt or vulnerability disclosure policy found.
  7. No security headers detected in HTML content; likely set at server level but not confirmed.
  8. Domain registration is transparent and consistent with website content.
  9. No advertising or affiliate marketing detected.
  10. Content is safe and suitable for general audiences.
Technical notes

Notes

The website uses a modern static site generator (Astro v5.8.0) with client-side JavaScript for theme management, indicating a contemporary and lightweight technical infrastructure. The site is well-structured with proper meta tags for SEO and social media sharing (Open Graph and Twitter cards). Hosting details are not explicit, but DNS is managed via Cloudflare. Performance is fast with good mobile optimization. Accessibility is basic but functional. No CMS or third-party frameworks beyond Astro and custom scripts are detected. The site uses a self-hosted analytics solution, which reduces reliance on third-party trackers and enhances privacy. Technical risks include lack of DNSSEC and missing security headers, which could be addressed to improve resilience.
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 isabelroses.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 isabelroses.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.