Skip to main content

Security report for jakearchibald.com

Jake Archibald · Technology · N/a

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

Security score

65/100

Risk levelMedium

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

JakeArchibald.com is a personal blog operated by Jake Archibald, a web developer and technologist. The site focuses on technical content related to web development, including topics such as progressive image rendering, JavaScript, CSS animations, and browser bugs. The blog targets web developers and technology enthusiasts, serving as a platform for thought leadership and knowledge sharing. The business model is primarily content publishing without commercial transactions or advertising. The domain has been registered since 2006, indicating a long-standing presence in the web development community. Technically, the website is built with modern web standards using HTML5, CSS, and JavaScript modules. It is hosted with Cloudflare DNS services, likely leveraging CDN capabilities for performance. The site is fast, mobile-optimized, and accessible, with good SEO practices evident from meta tags and structured content. No CMS or third-party frameworks are detected, suggesting a custom or static site architecture. From a security perspective, the site uses HTTPS (implied by Cloudflare hosting and modern scripts) but lacks explicit security headers in the HTML content. The domain registration includes protective statuses preventing unauthorized transfers or deletions, enhancing domain security. However, DNSSEC is not enabled, and no privacy or cookie policies are published, indicating gaps in compliance and security best practices. No forms or user input mechanisms are present, reducing attack surface. Overall, the website is trustworthy, professional, and safe for general audiences. The main risks relate to privacy compliance and security header hardening. Strategic improvements in these areas would enhance the site's security posture and regulatory adherence.

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

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

    • 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 jakearchibald.com

This scan found 22 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
75
Security headers
45
Email security
60
DNS health
75
Network security
100
GDPR outside view
35
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

Jake Archibald operates as an individual content creator and web developer with a strong reputation in the web technology community. The blog serves as a knowledge base and personal brand platform rather than a commercial enterprise. The target audience includes developers and tech enthusiasts interested in deep technical insights. The business model is non-commercial, focusing on content quality and community engagement. The site links to social media and a podcast, indicating a multi-channel presence. There are no indications of revenue streams such as advertising or affiliate marketing. The domain age and consistent content output suggest stability and credibility. The lack of formal business information or certifications aligns with the personal nature of the site.

Security posture

The website demonstrates a moderate security maturity level. Protective domain registration statuses are in place, and HTTPS is presumably enforced via Cloudflare. However, the absence of DNSSEC and security headers such as Content Security Policy, HSTS, or X-Frame-Options reduces defense-in-depth. No privacy or cookie policies are published, which is a compliance gap under GDPR and similar regulations. No incident response or vulnerability disclosure information is provided. The site does not collect user input via forms, minimizing attack vectors. Overall, the security posture is adequate for a personal blog but could be improved with standard security headers, DNSSEC, and published policies.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Publish a privacy policy and cookie policy to enhance GDPR compliance and user trust.
  3. Implement standard security headers such as Content Security Policy, HSTS, X-Frame-Options, and Referrer-Policy.
  4. Consider adding a security.txt file or vulnerability disclosure policy to facilitate responsible reporting.
  5. Regularly review and update analytics and tracking scripts to ensure minimal user data collection and privacy compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Jake Archibald
Description
Personal blog of Jake Archibald, a developer who writes about web development topics including progressive image rendering, JavaScript, CSS animations, browser bugs, and web technologies.
Key services
Technical blog posts, Podcast hosting (linked), Social media engagement
Content quality
excellent
Branding
consistent

Technology

Stack
HTML5, CSS, JavaScript (ES Modules), Cloudflare DNS
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
70/100
Good practices seen
  • Domain status includes clientDeleteProhibited, clientTransferProhibited, clientUpdateProhibited

Analytics and tracking

Services
Custom analytics script (analytics-Dxrm3QHx.js)
Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a personal technical blog with high-quality content.
  2. No privacy, cookie, or terms of service policies found.
  3. Contact email is provided but no phone or physical address.
  4. No forms detected on the site.
  5. No explicit security headers detected in HTML content.
  6. Uses Cloudflare DNS but DNSSEC is not enabled.
  7. No advertising or affiliate marketing detected.
  8. Minimal user tracking via a custom analytics script.
  9. Social media presence includes Mastodon, Bluesky, Threads, Twitter, Github.
  10. No signs of suspicious or malicious content.
Technical notes

Notes

The website is built using modern web technologies including HTML5, CSS, and JavaScript ES modules. It uses Cloudflare for DNS and likely CDN services, contributing to fast load times and good performance. The site is mobile-optimized and accessible with semantic HTML structure. No CMS or third-party frameworks are detected, indicating a custom or static site approach. The presence of a custom analytics script suggests bespoke tracking rather than third-party analytics platforms. The site lacks explicit security headers and DNSSEC, representing technical debt in security hardening. Overall, the technical infrastructure is solid for a personal blog but could benefit from enhanced security configurations and formalized compliance documentation.
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 jakearchibald.com. 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 jakearchibald.com.

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.