Skip to main content

Security report for statamic.com

Statamic, LLC · Technology · United States

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

Security score

73/100

Risk levelMedium

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

Statamic, LLC operates a mature and well-established CMS platform focused on delivering a modern, developer-friendly content management system built on Laravel. The company targets developers and teams seeking an alternative to traditional CMS platforms, offering a rich ecosystem of addons, starter kits, and a partner network. The website reflects a professional and consistent brand with excellent content quality and user experience. Technically, the site leverages modern front-end technologies such as Tailwind CSS and Alpine.js, and integrates services like Stripe and Google reCAPTCHA. However, the website suffers from critical security shortcomings, notably the absence of a valid SSL certificate and lack of HTTPS enforcement, which severely impacts its security posture. Privacy compliance is partially addressed with a clear privacy policy and terms of service, but lacks cookie consent mechanisms. Overall, the business credibility is strong, supported by customer testimonials and a vibrant community presence.

Scanned

NIS2 and GDPR posture

GDPR outside view
25/ 100 · Critical
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

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

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

This scan found 17 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
85
Security headers
65
Email security
80
DNS health
80
Network security
100
GDPR outside view
25
Average
73

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

Statamic holds a niche position in the CMS market, focusing on Laravel developers and flat-file CMS users. Its business model revolves around software licensing, addon sales, and fostering a partner ecosystem. The company demonstrates growth through active community engagement and a marketplace for extensions and starter kits. The website's content and structure indicate a medium-sized technology company with a clear focus on quality and developer experience. Partnerships with certified agencies and freelancers enhance its market reach. The absence of phone contact and physical addresses suggests a primarily digital-first operation.

Security posture

The current security posture of the website is weak due to the lack of a valid SSL certificate and disabled TLS protocols, exposing users to potential data interception and man-in-the-middle attacks. The absence of HSTS, OCSP stapling, and security headers further weakens the site's defense against common web threats. No explicit incident response or vulnerability disclosure policies are present, which may hinder timely handling of security incidents. While SPF records are correctly configured for email, the overall security maturity requires significant improvement to meet industry best practices and compliance standards.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate immediately to enable HTTPS and protect user data.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and disable deprecated protocols to enhance transport security.
  3. Implement HSTS with includeSubDomains and preload directives to enforce HTTPS usage.
  4. Add essential security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  5. Publish a security.txt file and provide clear incident response contact information to improve transparency and readiness.
Technical notes

Notes

The website is built on a solid technical foundation using Laravel and modern front-end frameworks like Tailwind CSS and Alpine.js. It integrates third-party services such as Stripe for payments and Google reCAPTCHA for bot protection. Despite a rich feature set and good mobile optimization, the site suffers from slow load times and a large page size, indicating potential optimization opportunities. The DNS is managed via Cloudflare, providing CDN and DNS services, but the lack of SSL undermines these benefits. The site architecture supports both flat-file and database modes, showcasing flexibility and scalability. Overall, the technical infrastructure is modern but requires security and performance enhancements.
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 statamic.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 statamic.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.