Skip to main content

Security report for jekyllthemes.io

Privacy service provided by Withheld for Privacy ehf · Technology · Iceland

Medium risk. 7 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

61/100

Risk levelMedium

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

JekyllThemes.io is a specialized online directory offering a curated collection of themes, templates, and resources for building websites using the Jekyll static site generator. Established in 2015, the site targets developers, designers, and tech enthusiasts seeking both free and premium Jekyll themes. The business operates as a niche marketplace, providing value through theme curation and discovery, positioning itself as a trusted resource within the Jekyll community. Technically, the website employs modern web technologies including HTML5, CSS3, JavaScript, and jQuery, with integrations such as Owl Carousel for UI components and Fathom Analytics for privacy-focused user tracking. Hosting and DNS services are managed via Cloudflare, enhancing performance and security. The site demonstrates good mobile optimization and SEO practices, although accessibility features are basic. From a security perspective, the site enforces HTTPS and avoids exposing sensitive data. However, it lacks DNSSEC and security headers, and does not publish explicit security or incident response policies. The use of WHOIS privacy protection is justified given the business type and size. Overall, the security posture is moderate but could be improved with additional hardening measures. The overall risk assessment is low, with no signs of malicious content or vulnerabilities. Strategic recommendations include enabling DNSSEC, implementing security headers, and publishing clear security policies to enhance trust and compliance. The site maintains a professional appearance and trustworthy reputation within its niche.

Scanned

NIS2 and GDPR posture

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

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 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 jekyllthemes.io

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. 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
15
Email security
75
DNS health
50
Network security
100
GDPR outside view
53
Average
61

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

JekyllThemes.io occupies a niche market as a curated directory for Jekyll themes, catering primarily to developers and designers interested in static site generation. Its competitive advantage lies in focused curation and offering both free and premium themes, which supports diversified revenue streams. The business model revolves around theme sales and affiliate links. The target customer segment is technically savvy users seeking quality Jekyll themes. Growth indicators include consistent domain age and ongoing content updates. The partnership ecosystem includes theme creators and hosting providers, although no explicit partners are listed. Operationally, the site is small but professional, with a clear market position as a trusted resource in the Jekyll ecosystem.

Security posture

The website demonstrates a moderate security maturity level. HTTPS is enforced, and no sensitive data is exposed in the HTML content. The absence of DNSSEC and security headers represents areas for improvement. There is no evidence of a formal vulnerability disclosure program or security.txt file, and incident response contact information is not provided. Privacy compliance is partial, with a privacy policy present but no cookie consent mechanism. The use of privacy protection in WHOIS is appropriate. Overall, the security culture appears informal but adequate for the business scale. Enhancing security policies and technical controls would reduce risk and improve compliance.

Recommendations

  1. Enable DNSSEC on the domain to protect against DNS spoofing and improve domain security.
  2. Implement HTTP security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to harden the website against common attacks.
  3. Publish explicit security and incident response policies, including contact channels for reporting vulnerabilities or abuse.
  4. Add a cookie consent mechanism to comply with privacy regulations and improve user transparency.
  5. Regularly review and update third-party libraries and scripts to mitigate potential vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Privacy service provided by Withheld for Privacy ehf
Description
A curated directory of themes, templates and resources for building Jekyll websites.
Key services
Theme curation, Theme sales (premium themes), Theme browsing and discovery
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, jQuery 3.5.1 slim, Owl Carousel, Fathom Analytics, Cloudflare DNS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of privacy protection for WHOIS

Analytics and tracking

Services
Fathom Analytics
Tracking level
minimal
Privacy practices
good

Advertising

Marketing tools
MailChimp
Transparency
basic

Site quality

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

Key observations

  1. Website is a curated directory for Jekyll themes with a professional design.
  2. No direct contact emails or phone numbers found; contact via mailing list signup form.
  3. No explicit cookie consent mechanism detected.
  4. Uses modern JavaScript libraries and analytics with privacy focus (Fathom).
  5. WHOIS privacy protection used but justified and domain age supports legitimacy.
  6. No security.txt or explicit security policies found.
  7. No DNSSEC enabled, which is a minor security gap.
  8. No suspicious or malicious content detected.
Technical notes

Notes

The website is built using standard web technologies including HTML5, CSS3, and JavaScript, with jQuery and Owl Carousel for interactive components. It uses Fathom Analytics, a privacy-focused analytics service, indicating a commitment to user privacy. Hosting and DNS are managed via Cloudflare, providing CDN and security benefits. The site is mobile optimized and SEO friendly, with appropriate meta tags and structured data (JSON-LD) for theme listings. Performance is moderate, with deferred script loading and lazy loading of images. Accessibility features are basic and could be enhanced. Overall, the technical infrastructure is solid for a small niche directory but could benefit from modern security enhancements and accessibility improvements.
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 jekyllthemes.io. 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 jekyllthemes.io.

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.