Skip to main content

Security report for jekyllrb.com

Jekyll · Technology · N/a

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

Security score

64/100

Risk levelMedium

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

Jekyll is a mature, open source static site generator project founded in 2009, targeting developers and bloggers who want to transform plain text into static websites and blogs. It is well integrated with GitHub Pages for free hosting, making it a popular choice in the static site ecosystem. The website is professionally designed with excellent content quality, clear navigation, and mobile optimization. Technically, it uses a modern stack including Ruby gems, Liquid templating, Markdown, and integrates third-party services like Google Analytics and Algolia DocSearch for analytics and search functionality. Security posture is good with HTTPS enforced and domain transfer protection, but lacks DNSSEC and security headers. Privacy compliance is weak due to absence of privacy and cookie policies. Overall, the site is trustworthy and credible but could improve compliance and security transparency.

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. 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 jekyllrb.com

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. 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
95
Security headers
15
Email security
70
DNS health
70
Network security
100
GDPR outside view
35
Average
64

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

Jekyll operates as an important entity in the technology sector, specifically in static site generation and developer tools. Its business model is open source with funding from sponsors, targeting developers and content creators seeking simple, blog-aware static sites. The project benefits from strong community support and GitHub integration, positioning it well in the market. The absence of direct commercial offerings or contact details aligns with its volunteer-maintained nature. The ecosystem includes partnerships with GitHub Pages and uses external services like Algolia for search. Growth indicators include recent releases and active GitHub repository. Strategic observations suggest focusing on compliance and security transparency to enhance trust.

Security posture

The website demonstrates a good security maturity level with HTTPS enabled, domain transfer lock, and no visible vulnerabilities or exposed sensitive data. However, it lacks DNSSEC, security headers (CSP, HSTS), and explicit security policies or incident response contacts. No vulnerability disclosure or security.txt files are present. Privacy compliance gaps exist due to missing privacy and cookie policies. The site uses Google Analytics which may have privacy implications without clear disclosures. Incident response readiness and security culture indicators are minimal due to lack of published policies. Overall, security posture is solid but could be improved by adopting best practices and transparency.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Publish comprehensive privacy and cookie policies to improve GDPR and privacy compliance.
  3. Add a security.txt file or dedicated vulnerability disclosure page with contact information.
  4. Implement HTTP security headers such as Content-Security-Policy, Strict-Transport-Security, and X-Frame-Options.
  5. Provide explicit contact information for security incidents and general inquiries to improve trust and responsiveness.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Jekyll
Description
Transform your plain text into static websites and blogs
Key services
Static site generation, Blog-aware site templates, Integration with GitHub Pages hosting
Content quality
excellent
Branding
consistent

Technology

Stack
Ruby (gem install bundler jekyll), Liquid templating, Markdown, HTML, CSS, Google Analytics, Algolia DocSearch
Frameworks
Jekyll v4.4.1
Platforms
GitHub Pages
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced (implied by canonical URL https://jekyllrb.com/)
  • Domain status clientTransferProhibited
  • No exposed sensitive data in HTML
  • No vulnerable libraries detected

Analytics and tracking

Services
Google Analytics
Tracking level
minimal
Privacy practices
poor

Advertising

Marketing tools
Algolia DocSearch
Transparency
basic

Site quality

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

Key observations

  1. Website is a well-established open source project site for Jekyll static site generator.
  2. Content is technical, developer-focused, and well structured.
  3. No privacy or cookie policies are published, which is a compliance gap.
  4. No explicit contact information or security policies are provided on the site.
  5. Uses modern web technologies and integrates with GitHub Pages for hosting.
  6. No signs of malicious or suspicious content.
  7. Good SEO and social media metadata present.
  8. Uses Google Analytics and Algolia DocSearch for analytics and search functionality.
Technical notes

Notes

The website uses a modern and efficient technology stack centered on Jekyll v4.4.1, Ruby gems, Liquid templating, Markdown, and CSS. It leverages GitHub Pages for hosting, ensuring fast performance and high availability. The site is mobile optimized and accessible with good SEO metadata including Open Graph and JSON-LD structured data. Analytics and search are implemented via Google Analytics and Algolia DocSearch respectively. No technical debt or deprecated technologies were detected. Opportunities exist to improve security headers and DNS security. Overall, the technical infrastructure is robust, performant, and well maintained.
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 jekyllrb.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 jekyllrb.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.