Skip to main content

Security report for 12daysofweb.dev

Stephanie Eckles · Technology · N/a

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

Security score

59/100

Risk levelMedium

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

12 Days of Web is a niche educational website created by Stephanie Eckles that offers a year-end series of tutorials and articles focused on fundamental web technologies such as HTML, CSS, and JavaScript. The site targets web developers and enthusiasts seeking to deepen their understanding of modern web development techniques. The business model centers around content publishing with an email subscription service for daily updates during December, supported by open-source sponsorship and donations. The website maintains a consistent brand and provides quality content with clear navigation and good user experience. Technically, the site is built using the Eleventy static site generator, leveraging modern web standards including HTML5, CSS3, and JavaScript. It uses Plausible Analytics, a privacy-focused analytics platform, and includes accessibility and SEO best practices. The site performs well with fast loading times and mobile optimization. However, no explicit hosting provider or advanced platform integrations are identified. From a security perspective, the site uses HTTPS as implied by external script sources, but lacks explicit security headers such as Content-Security-Policy or HSTS. Forms use POST methods with basic anti-bot hidden fields, but no published security policies or incident response contacts are available. Privacy and cookie policies are absent, representing compliance gaps. No vulnerabilities or exposed sensitive data were detected. Overall, the website is trustworthy and professional with a strong focus on educational content. The domain registration data aligns well with the website's author and content, supporting legitimacy. Strategic recommendations include publishing privacy and cookie policies, implementing security headers, and adding vulnerability disclosure information to enhance compliance and security posture.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 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

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

    • 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 12daysofweb.dev

This scan found 26 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. See sample alerts.

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
52
Security headers
30
Email security
60
DNS health
75
Network security
100
GDPR outside view
35
Average
59

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention 12daysofweb.dev, from OffSeq Breach.

No leaked records found

Breach holds no records for 12daysofweb.dev right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

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 in the technology sector, specifically targeting web developers interested in foundational web technologies. It holds a niche market position as an annual educational series with a loyal audience. The business model relies on content delivery via email subscription and open-source sponsorship, indicating a community-supported approach rather than direct monetization. The presence of related projects and social media links suggests an ecosystem of web development resources maintained by the author. Growth potential lies in expanding content offerings and improving compliance and security transparency. No direct partnerships or subsidiaries are identified.

Security posture

The current security posture is moderate. The site benefits from HTTPS usage and basic form security measures but lacks advanced security headers and published policies. There is no evidence of incident response readiness or vulnerability disclosure mechanisms. The absence of privacy and cookie policies indicates compliance gaps with GDPR and related regulations. No critical vulnerabilities or exposed sensitive data were found, but improvements are needed to align with best practices and regulatory requirements. The security culture appears informal, consistent with a small personal project rather than a corporate entity.

Recommendations

  1. Publish a comprehensive privacy policy and cookie policy to improve GDPR compliance.
  2. Implement security headers such as Content-Security-Policy, X-Frame-Options, and HSTS to enhance security posture.
  3. Add a security.txt file or vulnerability disclosure page to facilitate responsible reporting of security issues.
  4. Provide explicit contact information for security incidents or abuse reports.
  5. Regularly audit and update third-party scripts and dependencies to mitigate potential vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Stephanie Eckles
Description
A year-end celebration of fundamental web technologies: HTML, CSS, and JavaScript.
Key services
Daily web technology tutorials and articles during December, Email subscription for daily updates, Open-source project sponsorship
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, Eleventy (Static Site Generator), Plausible Analytics
Frameworks
Eleventy
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
70/100
Good practices seen
  • Use of HTTPS implied by external script URLs
  • No exposed sensitive data in HTML
  • Form uses POST method with hidden bot-field for spam protection

Analytics and tracking

Services
Plausible Analytics
Tracking level
minimal
Privacy practices
basic

Advertising

Tracking pixels
Plausible Analytics
Transparency
basic

Site quality

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

Key observations

  1. Website is a niche educational project focused on web development technologies.
  2. Content is well structured with clear navigation and thematic organization.
  3. No privacy or cookie policies are published, which is a compliance gap.
  4. No explicit security policies or incident response information is provided.
  5. Use of modern static site generator (Eleventy) and privacy-focused analytics (Plausible).
  6. No phone numbers or physical addresses found; contact is via email subscription form only.
  7. Social media presence limited to Twitter link in footer.
  8. No signs of suspicious or malicious content.
Technical notes

Notes

The website is built on a modern static site generator (Eleventy) using standard web technologies (HTML5, CSS3, JavaScript). It employs Plausible Analytics for privacy-conscious user tracking. The site demonstrates good performance, mobile responsiveness, and accessibility features. Meta tags and Open Graph data are well implemented for SEO and social sharing. However, no advanced hosting or platform details are evident. The absence of security headers and formal policies suggests technical debt in security and compliance areas. Overall, the technical infrastructure is solid for a small-scale content site but could benefit from enhanced security and compliance features.
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

Earlier scans of this domain

  1. 59/100Medium35 findingsView report
Reviews of this site

Share your experience with 12daysofweb.dev. 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 12daysofweb.dev.

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.