Skip to main content

Security report for termageddon.com

Termageddon · Technology · N/a

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

Security score

82/100

Risk levelLow

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

Termageddon is a specialized technology company offering auto-updating website legal policies such as Privacy Policies, Terms of Service, and Cookie Policies. Founded in 2016 and led by a privacy attorney, it occupies a niche market position providing SaaS solutions to businesses seeking compliance with GDPR, CPRA, CalOPPA, and other regulations. The company targets website owners and businesses requiring legally sound, automatically updated policies to mitigate legal risks. Technically, the website is built on WordPress with modern themes and integrates consent management via Usercentrics and privacy-focused analytics through Fathom. The infrastructure uses Cloudflare DNS and GoDaddy as registrar, with domain locking for security. Security posture is strong with HTTPS enforced and client prohibitions on domain transfers, though DNSSEC is not enabled and no explicit security or incident response policies are published. Overall, the website is professional, well-branded, and trustworthy, with good privacy compliance indicators but lacks direct contact information and formal security disclosures.

Scanned

NIS2 and GDPR posture

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

2 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 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 termageddon.com

This scan found 16 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
75
Security headers
70
Email security
70
DNS health
80
Network security
100
GDPR outside view
95
Average
82

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

Termageddon operates a SaaS business model focused on legal compliance automation for websites. Its competitive advantage lies in its legal foundation and automatic updates to policies as laws change, appealing to small and medium businesses concerned about regulatory compliance. Revenue streams likely include subscription fees for policy generation and maintenance. The target customer segment includes website owners, agencies, and partners needing reliable legal documents. The company maintains a professional online presence with consistent branding and a clear service portfolio. Partnerships or subsidiaries are not evident from the data. Growth indicators include a comprehensive resource section (blog, podcast) and agency partner programs. The company leverages modern web technologies and privacy-first analytics, aligning with its compliance focus.

Security posture

The website demonstrates a mature security posture with HTTPS enforced and domain registration locked against unauthorized changes. The use of Usercentrics for consent management indicates attention to privacy compliance. No security.txt or incident response contacts are published, representing a gap in transparency for vulnerability disclosure and incident handling. No vulnerabilities or exposed sensitive data were detected in the analysis. The absence of DNSSEC is a minor security shortfall. Overall, the security maturity is good but could be improved by publishing formal security policies and enabling DNSSEC.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Publish a dedicated security policy page including incident response procedures and contact channels.
  3. Add a security.txt file at the root domain to facilitate responsible vulnerability disclosure.
  4. Include clear company contact information such as email and phone for customer and security inquiries.
  5. Regularly review and update third-party scripts and consent management tools to mitigate supply chain risks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Termageddon
Description
Auto-updating privacy policies. Get the policies your website needs to comply with GDPR, CPRA, CalOPPA, & more. The only Privacy Policy Generator founded by a Privacy Attorney.
Key services
Privacy Policy Generator, Terms and Conditions Generator, Disclaimer Generator, End User License Agreement Generator, Cookie Policy Generator, Cookie Consent Solution
Content quality
excellent
Branding
consistent

Technology

Stack
WordPress, jQuery, Cloudflare DNS, Usercentrics Consent Management, Fathom Analytics
Frameworks
GeneratePress Theme
Platforms
WordPress CMS
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Domain locked with multiple client prohibitions
  • Use of consent management platform (Usercentrics)
  • No exposed sensitive data detected

Analytics and tracking

Services
Fathom Analytics
Tracking level
minimal
Privacy practices
good

Advertising

Tracking pixels
Fathom Analytics, Usercentrics Consent Management
Marketing tools
Usercentrics, Fathom Analytics
Transparency
good

Site quality

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

Key observations

  1. Website provides comprehensive auto-updating legal policy generation services.
  2. Strong legal foundation with privacy attorney involvement.
  3. Good use of modern web technologies and consent management.
  4. No direct contact emails or phone numbers found on main site.
  5. No explicit security or incident response policies published.
  6. Domain is well-registered and locked, but DNSSEC is not enabled.
Technical notes

Notes

The website is built on WordPress CMS using the GeneratePress theme, leveraging jQuery and modern CSS for responsive design. It integrates Usercentrics for cookie consent and Fathom Analytics for privacy-focused tracking. Hosting details are not explicit but DNS is managed via Cloudflare and domain registered with GoDaddy. Performance is moderate with good mobile optimization and accessibility features. SEO is well implemented with comprehensive meta tags, Open Graph, and JSON-LD structured data. No critical technical debt or vulnerabilities were identified. Opportunities exist to improve DNS security and formalize security disclosures.
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 termageddon.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 termageddon.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.