Skip to main content

Security report for autumn.town

Technology · United Kingdom

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

Security score

62/100

Risk levelMedium

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

Autumn Town is a personal website operated by an individual named Autumn, focusing on personal blogging, photography, programming, and hardware/software projects. The site is positioned as a creative outlet rather than a commercial business, targeting a general audience interested in personal and indie content. The website is built using the Hugo static site generator and hosted via Cloudflare, ensuring fast performance and HTTPS security. The technical infrastructure is modern and lightweight, with minimal external dependencies and good mobile optimization. Security posture is adequate with HTTPS and domain transfer protection, but lacks DNSSEC and security headers. Privacy compliance is low due to absence of privacy and cookie policies. Overall, the site is trustworthy as a personal project but would benefit from enhanced security and compliance measures.

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 autumn.town

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
100
GDPR outside view
50
Average
62

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 portfolio and blog without commercial transactions or revenue streams. It targets niche audiences interested in creative and technical hobbies. The domain is newly registered in 2024, consistent with the site's recent creation. The operator leverages Cloudflare for DNS and hosting, and links to multiple related personal and community sites. There is no evidence of partnerships or subsidiaries. The business model is non-commercial, focusing on content sharing and community engagement. Growth indicators are limited due to the personal nature of the site.

Security posture

The site uses HTTPS and Cloudflare DNS with clientTransferProhibited status, providing baseline security. However, DNSSEC is not enabled, and no HTTP security headers are present, which could expose the site to certain attacks. There is no privacy policy or cookie consent mechanism, indicating non-compliance with GDPR and related regulations. No incident response or vulnerability disclosure information is provided. The site does not collect personal data via forms, reducing risk. Overall, security maturity is moderate but could be improved with standard best practices.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement standard HTTP security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Add a clear privacy policy and cookie consent mechanism to comply with GDPR and improve user trust.
  4. Provide security contact information or a vulnerability disclosure policy to improve incident response readiness.
  5. Regularly review and update site dependencies and scripts to avoid potential vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Personal website of Autumn, a genderfluid individual interested in photography, software and hardware modding, programming, and personal projects. The site serves as a personal blog and project dump.
Key services
Personal blogging, Project sharing, Photography and creative content
Content quality
good
Branding
consistent

Technology

Stack
Hugo static site generator, Cloudflare DNS and hosting, JavaScript (clipboard API), CSS
Platforms
Static site
Performance
fast
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
65/100
Good practices seen
  • HTTPS enforced
  • Domain status clientTransferProhibited

Analytics and tracking

Services
Cloudflare Insights
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Cloudflare Insights
Transparency
poor

Site quality

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

Key observations

  1. Personal website with clear focus on individual projects and blogging
  2. No commercial or business transactional elements present
  3. No privacy or cookie policies found, indicating low compliance with GDPR
  4. No security policy or incident response information available
  5. Use of Cloudflare for DNS and hosting with HTTPS enabled
  6. No forms collecting personal data except a JavaScript clipboard copy button
  7. Multiple external links to social and personal project sites
  8. No email addresses or phone numbers explicitly listed
  9. No security headers detected in HTML content
  10. No CMS beyond static site generator Hugo detected
Technical notes

Notes

The website is a static site generated by Hugo, hosted on Cloudflare infrastructure, ensuring fast load times and reliable uptime. The tech stack is minimal, relying on standard HTML, CSS, and JavaScript for UI interactions. The site includes a JavaScript clipboard function and Cloudflare Insights for analytics. SEO is basic with meta tags and canonical links but lacks advanced structured data or Open Graph tags. Accessibility is basic but functional. There is no CMS or dynamic backend detected, reducing attack surface but limiting interactivity. The site is mobile optimized and well-structured for user navigation.
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 autumn.town. 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 autumn.town.

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.