Skip to main content

Security report for triggerbee.com

Triggerbee · Technology · Denmark

Medium risk. 5 critical or high findings in Security headers and SSL/TLS.

Security score

66/100

Risk levelMedium

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

Triggerbee is a Denmark-based technology company founded in 2014 that provides an all-in-one onsite marketing platform designed to help businesses convert website traffic through personalization, forms, promotions, surveys, referrals, and gamification. The company targets businesses seeking to enhance onsite marketing effectiveness using SaaS solutions. The website is built on WordPress with Elementor, leveraging modern web technologies and integrating multiple analytics and advertising tools such as Google Analytics, Microsoft Clarity, Facebook Pixel, and LinkedIn Ads. Hosting appears to be on Microsoft Azure, inferred from cookies. Security posture is solid with HTTPS enforced and cookie consent mechanisms in place, though explicit security headers and policies are not fully published. Privacy compliance is partially addressed with a detailed cookie consent banner but lacks a clearly accessible privacy policy and terms of service. Overall, the website demonstrates good technical maturity, professional design, and consistent branding, supporting a high trustworthiness level.

Scanned

NIS2 and GDPR posture

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

5 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. 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 Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1
    • 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 triggerbee.com

This scan found 26 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
57
Security headers
25
Email security
65
DNS health
65
Network security
100
GDPR outside view
83
Average
66

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

Triggerbee operates in the technology sector, focusing on onsite marketing solutions delivered via a SaaS model. The company leverages a niche market position by offering integrated marketing tools that enhance user engagement and conversion on client websites. Their business model likely includes subscription-based revenue streams. The website's structured data and social media presence indicate active digital marketing and brand awareness efforts. Partnerships with major advertising platforms such as Facebook, Google, LinkedIn, and Microsoft suggest a robust marketing ecosystem. The absence of explicit contact information and formal policies on the website may indicate areas for improvement in customer engagement and compliance transparency.

Security posture

The website enforces HTTPS and uses a cookie consent management platform (CookieYes) with detailed cookie categorization, reflecting a good privacy compliance effort. However, explicit security headers like Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options are not evident in the provided content, which could enhance protection against common web attacks. No security policy or incident response contact information is published, limiting transparency for security issues. The use of multiple third-party scripts introduces potential risk vectors, necessitating regular security audits. Overall, the security posture is moderate to good but can be improved by publishing formal policies and enhancing header configurations.

Recommendations

  1. Publish a comprehensive privacy policy and terms of service accessible from the website footer or main navigation.
  2. Implement and explicitly configure security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Add a security policy page and provide clear incident response contact channels (e.g., security@ or abuse@ email addresses).
  4. Regularly audit and update third-party scripts to mitigate vulnerabilities and reduce attack surface.
  5. Enhance transparency by providing contact information including phone numbers and physical addresses to improve business credibility.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Triggerbee
Description
Triggerbee offers an all-in-one onsite marketing platform that helps convert website traffic using forms, promotions, surveys, referrals, and gamification.
Key services
Website personalization, Forms, Promotions, Surveys, Referrals, Gamification
Content quality
good
Branding
consistent

Technology

Stack
WordPress, Elementor, Google Fonts, Cloudflare DNS, Google Tag Manager, Facebook Pixel, Microsoft Clarity, CookieYes Consent Management
Frameworks
Elementor
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Cookie consent banner with detailed cookie categories
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics, Microsoft Clarity, LinkedIn Analytics, Bing Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Facebook Ads, Microsoft Advertising, Google Ads, LinkedIn Ads, Bing Ads
Tracking pixels
Facebook Pixel, Microsoft Clarity, LinkedIn Insight Tag
Marketing tools
Triggerbee onsite marketing platform, CookieYes Consent Management
Transparency
good

Site quality

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

Key observations

  1. Website uses modern WordPress CMS with Elementor builder.
  2. Cookie consent is implemented with detailed categories and user controls.
  3. No explicit privacy policy or terms of service found in provided content.
  4. No direct contact emails or phone numbers found in the HTML content.
  5. Multiple third-party analytics and advertising scripts are used.
  6. Website is well-structured with good SEO metadata and structured data.
  7. No security.txt or vulnerability disclosure page detected.
  8. No explicit security or incident response policies published.
  9. Social media presence is linked via JSON-LD structured data.
Technical notes

Notes

The website is built on WordPress CMS with the Elementor page builder, utilizing Google Fonts and hosted likely on Microsoft Azure, as indicated by Azure-specific cookies. It integrates multiple analytics and advertising technologies including Google Analytics, Microsoft Clarity, Facebook Pixel, LinkedIn Insight Tag, and Bing Ads. The site uses Cloudflare for DNS but does not show evidence of Cloudflare WAF blocking. Performance is moderate with good mobile optimization and accessibility features. SEO is well addressed with proper meta tags, Open Graph, Twitter Cards, and JSON-LD structured data. The cookie consent mechanism is robust, providing granular user control over cookie categories. Technical risks include reliance on multiple third-party scripts and lack of explicit security headers, which should be addressed to improve 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

Reviews of this site

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