Skip to main content

Security report for goth.zip

Other · N/a

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

Security score

66/100

Risk levelMedium

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

The website goth.zip is a personal blog operated by an individual named Selene. It serves as a homepage with links to related sites and includes a music track display component. The site is built using the Astro framework, indicating a modern technical approach, but it remains a work in progress with minimal business or compliance information. The target audience appears to be general visitors interested in the author's content and related projects. The site is part of a webring associated with staydown.money, suggesting a small network of related personal or niche sites. Technically, the site uses modern web technologies including Astro v3.2.3, JavaScript modules, CSS, and WebP images. The site appears to be mobile optimized and has basic SEO and accessibility features. However, no CMS or hosting provider information is evident. Performance is moderate based on the use of modern but minimalistic design and external scripts. From a security perspective, the site lacks visible security headers and does not provide privacy, cookie, or terms of service policies. No contact information or incident response details are provided, limiting trust and compliance. The site uses an external hit counter from websiteout.com, which may raise privacy concerns. No WAF or blocking mechanisms are detected, and the content is fully accessible. No adult or explicit content is present, making the site safe for general audiences. Overall, the site scores moderately on AI evaluation due to its basic content quality and technical implementation but scores low on privacy compliance and security posture. Strategic improvements include adding privacy and cookie policies, implementing security headers, providing contact and incident response information, and auditing external scripts for privacy and security risks.

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

    • 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 goth.zip

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
72
Security headers
30
Email security
70
DNS health
75
Network security
100
GDPR outside view
50
Average
66

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 site represents a small-scale personal blog with no clear commercial business model or revenue streams. It targets a niche audience interested in the author's personal content and related projects. The presence in a webring with staydown.money indicates a community or network approach rather than a standalone commercial entity. There are no visible partnerships beyond the webring, no certifications, and no formal business registrations or trust signals. The business model is primarily content sharing and personal branding. Growth indicators and market positioning are minimal due to the site's early development stage and limited content.

Security posture

The security maturity level of the site is low. There are no detected security headers such as Content-Security-Policy or X-Frame-Options, and no HTTPS/SSL configuration details were provided. The site does not disclose any security policies or incident response contacts, which limits readiness for security events. The use of an external hit counter introduces potential privacy risks. No forms or user input fields are present, reducing attack surface but also limiting interactivity. Compliance with GDPR or other data protection regulations is not evident. Overall, the site would benefit from implementing basic security best practices and compliance documentation to improve trustworthiness.

Recommendations

  1. Implement HTTPS with a valid SSL/TLS certificate to secure data in transit.
  2. Add standard security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish privacy and cookie policies to improve legal compliance and user trust.
  4. Provide clear contact information and incident response channels for security issues.
  5. Audit and minimize use of third-party scripts to reduce privacy and security risks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Personal blog website of Selene, presenting a homepage with links to related sites and a music track component. The site is described as a work in progress.
Key services
blog content, personal portfolio, music track display
Content quality
basic
Branding
moderate

Technology

Stack
Astro, JavaScript, CSS, WebP images, HTML5
Frameworks
Astro v3.2.3
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
40/100

Analytics and tracking

Services
websiteout.com counter
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
websiteout.com counter
Transparency
basic

Site quality

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

Key observations

  1. Website is a personal blog with minimal business or compliance information.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact emails, phone numbers, or social media links detected.
  4. Uses Astro framework with modern web technologies.
  5. Includes external hit counter from websiteout.com.
  6. No security headers or advanced security features detected in provided data.
  7. No forms or data collection fields present on the homepage.
  8. Site is part of a webring linked to staydown.money.
  9. No signs of adult or explicit content.
  10. No WAF or blocking detected; content fully accessible.
Technical notes

Notes

The website is built using Astro v3.2.3, a modern static site generator framework, leveraging JavaScript modules and CSS for styling. The site uses WebP images for optimized media delivery. The HTML structure is valid and includes meta tags for viewport and Open Graph, supporting basic SEO and social sharing. The site is mobile optimized with responsive design elements. No CMS or hosting provider information is detected. Performance is moderate, with external scripts for hit counting potentially impacting load times. Accessibility is basic but present. There is opportunity to improve technical robustness by adding security headers, optimizing external dependencies, and enhancing SEO metadata.
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 goth.zip. 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 goth.zip.

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.