Skip to main content

Security report for lipamanka.gay

Other · Iceland

Medium risk. 6 critical or high findings in Security headers and GDPR outside view.

Security score

65/100

Risk levelMedium

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

The website 'lipamanka.gay' is a personal site primarily focused on sharing essays, stories, and linguistic resources related to the creator's interests. It is a small-scale, niche site without commercial intent or business contact information. The site is hosted likely on GitHub Pages with domain registration through NameCheap, protected by privacy services. The technical infrastructure is basic, relying on standard HTML, CSS, and JavaScript, with minimal external dependencies. Analytics are implemented via GoatCounter, providing lightweight user tracking without aggressive data collection. From a security perspective, the site uses HTTPS and has domain transfer protection enabled, but lacks DNSSEC and security headers, which could be improved to enhance security posture. There are no privacy or cookie policies, nor terms of service, which limits compliance with GDPR and other privacy regulations. No contact or incident response information is provided, reducing transparency and trustworthiness from a security standpoint. Overall, the site is safe for general audiences, containing no adult or explicit content. The domain registration is recent and privacy protected, appropriate for a personal website. The lack of business information and policies limits the site's credibility and compliance maturity. Strategic improvements in security headers, privacy disclosures, and contact transparency would enhance trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
40/ 100 · High
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 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 lipamanka.gay

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
70
DNS health
70
Network security
100
GDPR outside view
40
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 content sharing platform with no evident commercial activities or revenue streams. Its market position is niche, targeting enthusiasts of linguistics and personal essays. The business model is non-commercial, focusing on content publication and community engagement through linked linguistic resources. The site leverages partnerships with external domains for content embedding and analytics but does not engage in advertising or affiliate marketing. Growth indicators are limited due to the personal nature of the site. The partnership ecosystem includes linguistic community sites and web rings, enhancing content reach within niche audiences.

Security posture

The current security maturity is basic. HTTPS is enforced, and domain transfer protection is active, which are positive indicators. However, the absence of DNSSEC and security headers such as Content-Security-Policy and X-Frame-Options exposes the site to potential risks like DNS spoofing and clickjacking. No forms or input fields reduce attack surface but also limit user engagement. The lack of privacy and cookie policies indicates non-compliance with GDPR and similar regulations. Incident response readiness is not evident due to missing contact channels for security issues. Overall, the security culture appears minimal but adequate for a personal site with low risk exposure.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement standard security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish privacy and cookie policies to improve GDPR compliance and user transparency.
  4. Add clear contact information or a security contact email for incident reporting and trust building.
  5. Consider enhancing accessibility and mobile optimization for better user experience.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
A personal website hosting essays, stories, linguistic resources, and personal interests of the individual 'lipamanka'.
Key services
essays, stories, linguistic resources, personal interests sharing
Content quality
basic
Branding
moderate

Technology

Stack
HTML5, CSS, JavaScript
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
50/100
Good practices seen
  • HTTPS enabled
  • Domain status clientTransferProhibited

Analytics and tracking

Services
GoatCounter
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
GoatCounter
Transparency
poor

Site quality

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

Key observations

  1. Personal website with no commercial or business contact information.
  2. No privacy, cookie, or terms of service policies found.
  3. Minimal security headers and no DNSSEC.
  4. Uses GoatCounter for minimal analytics tracking.
  5. No forms or data collection fields present.
  6. Content is safe and suitable for general audiences.
  7. Domain registration is privacy protected but legitimate for personal use.
Technical notes

Notes

The website is built using basic HTML5, CSS, and JavaScript without any detected CMS or advanced frameworks. Hosting appears to be on GitHub Pages, inferred from the Open Graph URL. Performance is moderate with no explicit indicators of optimization or caching strategies. Mobile responsiveness is basic but present via viewport meta tag. SEO is minimal with basic meta tags and Open Graph properties. No accessibility features beyond basic HTML structure were detected. The use of GoatCounter provides lightweight analytics without heavy tracking. Technical debt is low due to simplicity but modernization opportunities include adding security headers and improving privacy compliance.
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 lipamanka.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 lipamanka.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.