Skip to main content

Security report for bugsnag.com

BugSnag · Technology · N/a

Medium risk. 5 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

71/100

Risk levelMedium

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

BugSnag operates as a SaaS provider specializing in application monitoring, error tracking, and real user monitoring, targeting developers and engineering teams. The company positions itself as a leader in app stability management with a comprehensive platform supporting multiple technologies including mobile and web platforms. The website reflects a mature digital presence with professional branding, clear product offerings, and extensive resources such as documentation and customer stories. Technically, the site is built on WordPress with modern JavaScript libraries and integrates multiple marketing and analytics tools, demonstrating a high level of digital maturity. Security posture is solid with HTTPS enforced and cookie consent implemented, though explicit security headers and published security policies are absent. The WHOIS data is missing or inaccessible, which raises some concerns about domain registration transparency but does not detract significantly from the overall trustworthiness given the professional site content. Overall, the website is well-designed, secure, and business credible, though improvements in privacy compliance and WHOIS transparency are recommended.

Scanned

This is an earlier scan of bugsnag.com. View the latest report

NIS2 and GDPR posture

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

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. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • 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

  3. 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 bugsnag.com

This scan found 21 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
15
Email security
80
DNS health
80
Network security
100
GDPR outside view
73
Average
71

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

BugSnag targets software development teams requiring robust error monitoring and application stability solutions. Its business model is subscription-based SaaS with offerings tailored for mobile, web, and server-side applications. The company leverages integrations and features like stability scoring and distributed tracing to differentiate itself. The presence of customer stories and demos indicates a focus on enterprise clients. Marketing efforts include Google and Bing ads, and the use of Drift chat for customer engagement. The lack of explicit contact information on the main page suggests a focus on digital lead generation rather than direct sales. The company appears well-positioned in the technology sector with a strong brand and comprehensive product suite.

Security posture

The website enforces HTTPS and uses cookie consent mechanisms, reflecting good baseline security practices. However, the absence of visible security headers such as Content-Security-Policy and X-Frame-Options is a gap. No vulnerabilities or exposed sensitive data were detected in the analyzed content. The use of third-party scripts for analytics and marketing is extensive but consent-based. The lack of a published security policy, incident response contacts, or vulnerability disclosure program limits transparency and may impact trust for security-conscious clients. Overall, the security posture is good but could be enhanced by publishing detailed security and privacy documentation and implementing additional HTTP security headers.

Recommendations

  1. Publish a comprehensive privacy policy and terms of service accessible from the homepage.
  2. Implement and publish a security policy and incident response contact information.
  3. Add HTTP security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  4. Clarify domain registration details or ensure WHOIS data transparency to improve trust.
  5. Establish and publicize a vulnerability disclosure program and security.txt file.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
BugSnag
Description
BugSnag is an error monitoring and reporting software with best-in-class functionality for mobile apps. Our tool alerts users of bugs, errors & more. Free trial!
Key services
Error Monitoring, Real User Monitoring, Distributed Tracing, App Stability Management, Integrations, On-Premises options, Security features, Search & Segment, Stability Score
Content quality
excellent
Branding
consistent

Technology

Stack
jQuery, Lottie animations, Google Tag Manager, Bing Ads, CookieHub, Drift chat widget, Yoast SEO plugin, WordPress CMS
Frameworks
WordPress, Yoast SEO
Platforms
Web, Mobile (Flutter, React Native, Android, iOS)
Performance
moderate
Mobile
excellent
Accessibility
good
SEO
excellent

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced (implied by canonical URL and scripts loaded over HTTPS)
  • Cookie consent mechanism implemented
  • Use of security-focused plugins (Yoast SEO with security features)
  • Chat widget with fallback to Zendesk for support

Analytics and tracking

Services
Google Analytics (via GTM), Ahrefs Analytics, Bing Ads tracking
Tracking level
moderate
Privacy practices
basic

Advertising

Ad networks
Bing Ads, Google Ads, Convert Experiences
Tracking pixels
Bing Ads, CookieHub
Marketing tools
Drift chat, CookieHub
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 rich content and professional design
  2. No WAF or blocking mechanisms detected
  3. WHOIS data is missing or domain not found in WHOIS, which is unusual
  4. Cookie consent and privacy mechanisms are partially implemented
  5. No explicit privacy policy or terms of service links found in provided HTML
  6. Multiple external analytics and marketing scripts are used
  7. No contact emails or phone numbers explicitly found in the HTML snippet
  8. Strong focus on developer tools and application monitoring services
  9. Use of modern web technologies and WordPress CMS
Technical notes

Notes

The website is built on WordPress CMS enhanced with Yoast SEO for search optimization. It uses jQuery and Lottie for animations, and integrates multiple third-party services including Google Tag Manager, Bing Ads, CookieHub for consent management, and Drift for live chat support. The site is mobile-optimized with responsive design and good accessibility features. Performance is moderate, likely influenced by multiple external scripts. The technical stack is modern and well-maintained, supporting a professional and scalable web presence. Opportunities exist to optimize performance by reducing third-party script load and enhancing security headers.
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. 66/100 −5Medium33 findingsView report
  2. 71/100Medium29 findingsView report
  3. 71/100Medium25 findingsView report
Reviews of this site

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