Skip to main content

Security report for lisanne.gay

Technology · United States

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

Security score

52/100

Risk levelMedium

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

Lisanne.gay is a personal website operated by an individual developer named Lisanne, who identifies as they/she. The site serves as a portfolio showcasing their software and game development projects, including Godot games and web browsers. The website is small-scale and targets an audience interested in indie software and gaming projects. The domain was registered in 2022, consistent with the website's stated establishment date. The site links to various external developer platforms such as GitLab and itch.io, reinforcing its role as a personal project hub. Technically, the website is built with standard HTML, CSS, and JavaScript, hosted by Dynadot Inc. It uses HTTPS but lacks advanced security headers and DNSSEC, indicating room for improvement in security hardening. The site is moderately optimized for mobile and has basic accessibility and SEO features. No CMS or major frameworks are detected, suggesting a custom or lightweight static site. From a security perspective, the site has a basic posture with HTTPS enabled but no evident security policies, incident response contacts, or vulnerability disclosure mechanisms. No privacy or cookie policies are present, which may expose the site to compliance risks under GDPR or similar regulations. No contact emails or phone numbers are provided, limiting direct communication channels. Overall, the website is a functional personal portfolio with good content quality but lacks formal security and privacy controls. Strategic improvements in security headers, policy disclosures, and contact information would enhance trust and compliance. The site is safe for general audiences with no adult or questionable content detected.

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

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

  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

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

Keep watching lisanne.gay

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. 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
15
Email security
60
DNS health
70
Network security
40
GDPR outside view
50
Average
52

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 a niche personal brand focused on indie game and software development. Its market position is that of an individual creator rather than a commercial enterprise. The business model is primarily portfolio and project showcase, with no evident monetization or commercial transactions on the site itself. The target customers are likely fellow developers, gamers, and open-source enthusiasts. The presence of multiple external links to developer platforms suggests an ecosystem of related projects and collaborations. Growth indicators are limited due to the personal nature of the site. No formal partnerships or subsidiaries are identified. The site’s operations appear self-managed with a focus on creative output rather than commercial scale.

Security posture

The security maturity level is basic. HTTPS is implemented, which is mandatory, but no additional security headers such as Content-Security-Policy or Strict-Transport-Security are detected. DNSSEC is not enabled, which could improve DNS security. There are no visible vulnerabilities or exposed sensitive data. The absence of privacy and cookie policies indicates compliance gaps, especially for GDPR. No incident response or security contact information is provided, limiting readiness for security events. No vulnerability disclosure or security.txt files are present. Overall, the security culture appears informal and minimal, typical for a personal site but with room for improvement to reduce risk and enhance trust.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS integrity and security.
  2. Implement standard security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Publish a privacy policy and cookie policy to comply with GDPR and other privacy regulations.
  4. Add clear contact information including an email address for general and security-related inquiries.
  5. Consider adding a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Personal website of Lisanne (they/she), a developer who creates games and software, including Godot games and two web browsers. The site hosts projects and links to external developer profiles.
Key services
Game development, Software projects, Project downloads
Content quality
good
Branding
moderate

Technology

Stack
HTML5, CSS3, JavaScript
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
55/100
Good practices seen
  • Domain uses HTTPS

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. Personal developer portfolio website with clear focus on indie game and software projects.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact emails or phone numbers explicitly provided.
  4. No security policies or incident response information available.
  5. No security headers detected; DNSSEC not enabled.
  6. Website uses HTTPS but could improve security posture.
  7. No advertising or tracking technologies detected.
  8. Content is safe and suitable for general audiences.
  9. Good navigation and content structure with moderate branding consistency.
  10. WHOIS data consistent with website claims and domain age.
Technical notes

Notes

The website uses a simple technology stack with HTML5, CSS3, and JavaScript. It does not rely on any detected CMS or major frameworks, indicating a custom or static site approach. Hosting is provided by Dynadot Inc, a reputable registrar and hosting provider. Performance is moderate with deferred loading of JavaScript assets. Mobile optimization is good with responsive viewport settings and flexible layout. Accessibility is basic with some semantic HTML but no advanced ARIA or accessibility features detected. SEO is basic with meta tags and Open Graph tags present but no structured data like JSON-LD. There is no evidence of technical debt or legacy technologies, but security and compliance features are minimal. Opportunities exist to modernize security practices and improve policy disclosures.
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 lisanne.gay. 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 lisanne.gay.

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.