Skip to main content

Security report for termly.io

Termly.io · Technology · Sweden

Low risk. 3 critical or high findings in Security headers and SSL/TLS.

Security score

79/100

Risk levelLow

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

Termly.io is a technology company specializing in privacy compliance solutions for websites, apps, and businesses worldwide. Founded in 2016 and operating under One.com Group AB in Sweden, Termly offers SaaS tools including privacy policy generators, cookie consent management, and terms of service creation. The company targets businesses seeking to comply with global data privacy laws such as GDPR. Their market position is strong as a leading provider in the privacy compliance niche, supported by a professional and well-optimized website with comprehensive legal content and compliance features. Technically, Termly.io leverages a modern WordPress-based infrastructure enhanced with SEO plugins, performance optimizations, and advanced analytics tools like Google Tag Manager and Visual Website Optimizer. The site is mobile-optimized, fast-loading, and accessible, reflecting a mature digital presence. Hosting is provided by One.com, with DNS managed via Cloudflare, although DNSSEC is not enabled. From a security perspective, the website enforces HTTPS with strong domain registration protections. While explicit security headers are not fully confirmed, the use of cookie consent scripts and resource blockers indicates attention to privacy and security best practices. No critical vulnerabilities or exposed sensitive data were detected. However, the site lacks a published security policy, incident response contacts, and vulnerability disclosure mechanisms, which are recommended for enhanced trust. Overall, Termly.io presents a trustworthy, professional, and compliant online presence with strong business credibility and technical implementation. Strategic improvements in security transparency and DNS security would further strengthen their posture.

Scanned

NIS2 and GDPR posture

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

3 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. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

Need hands-on remediation? Email guard@offseq.com

Keep watching termly.io

This scan found 17 issues across 5 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
75
Security headers
50
Email security
70
DNS health
80
Network security
100
GDPR outside view
100
Average
79

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

Termly.io operates in the technology sector, providing essential compliance tools for data privacy laws globally. Their SaaS business model focuses on subscription-based legal compliance solutions, targeting small to medium businesses and enterprises needing privacy policy and cookie consent management. The company benefits from a consistent brand and strong SEO presence, with active social media engagement. Their parent company, One.com Group AB, adds legitimacy and operational scale. The absence of direct contact emails or phone numbers on the main site suggests a preference for contact forms, typical for SaaS providers. The company’s growth is supported by integrations with marketing and analytics platforms, indicating a data-driven approach to customer acquisition and retention.

Security posture

Termly.io demonstrates a solid security posture with HTTPS enforced and domain registration protections that prevent unauthorized transfers or deletions. The use of cookie consent management and resource blocking scripts aligns with GDPR compliance and privacy best practices. However, the lack of DNSSEC and explicit security headers such as Content-Security-Policy or X-Frame-Options represents areas for improvement. The absence of a published security policy or incident response contact reduces transparency for security researchers and customers. No vulnerabilities or exposed sensitive data were identified in the site’s scripts or content. Overall, the security maturity is good but could be enhanced by adopting additional security standards and publishing formal security documentation.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement and verify security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish a dedicated security policy page and provide incident response contact channels such as security@ or abuse@ emails.
  4. Create and host a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  5. Regularly audit third-party scripts and dependencies to ensure no vulnerable libraries are used.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Termly.io
Description
Termly is your all-in-one compliance solution for data privacy laws worldwide. Privacy policy generator, cookie consent, terms, and more.
Key services
Privacy policy generator, Cookie consent management, Terms and conditions generator, Compliance solutions for data privacy laws
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, Google Tag Manager, Termly resource blocker script, Yoast SEO plugin, WP Rocket, Visual Website Optimizer (VWO), Cloudflare DNS
Frameworks
WordPress, Genesis Framework
Platforms
WordPress CMS
Performance
fast
Mobile
excellent
Accessibility
good
SEO
excellent

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Domain status includes clientDeleteProhibited, clientTransferProhibited, clientUpdateProhibited
  • Use of cookie consent and resource blocking scripts

Analytics and tracking

Services
Google Tag Manager, Visual Website Optimizer
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Visual Website Optimizer (VWO)
Marketing tools
Yoast SEO, WP Rocket, Termly resource blocker
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Strong focus on privacy compliance and legal policy generation.
  3. Uses modern web technologies and SEO best practices.
  4. Includes cookie consent mechanism and privacy policy indicating GDPR compliance.
  5. No exposed sensitive data or security vulnerabilities detected in scripts.
  6. WHOIS data supports legitimacy and domain ownership transparency.
  7. No explicit contact emails or phone numbers found in HTML content but contact form is present.
  8. Social media presence on Facebook, Twitter (X), LinkedIn, and YouTube.
  9. No explicit security policy or incident response contacts published.
  10. No vulnerability disclosure or security.txt file detected.
Technical notes

Notes

The website is built on WordPress with the Genesis Framework, enhanced by Yoast SEO Premium and WP Rocket for SEO and performance optimization. It uses Google Tag Manager and Visual Website Optimizer for analytics and A/B testing. Hosting is provided by One.com with DNS managed by Cloudflare, though DNSSEC is not enabled. The site is mobile-optimized, fast, and accessible with modern HTML and CSS practices. JavaScript is used for cookie consent and resource blocking, ensuring compliance with privacy laws. The technical stack is mature and well-maintained, with opportunities to improve DNS security and HTTP security headers for a more robust security posture.
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. 81/100 +3Low25 findingsView report
  2. 78/100 +5Low27 findingsView report
  3. 73/100Medium24 findingsView report
Reviews of this site

Share your experience with termly.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 termly.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.