Skip to main content

Security report for locust.io

Heylab AB · Technology · Sweden

Medium risk. 10 critical or high findings in Email security, Security headers and 2 other checks.

Security score

54/100

Risk levelMedium

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

Locust.io is an established open source load testing framework developed and maintained by Heylab AB, a Swedish company founded in 2011. The platform enables developers and performance testers to define user behavior in Python code and simulate millions of simultaneous users for scalable load testing. The website demonstrates a strong community presence with numerous contributors and endorsements from reputable companies such as Riot Games, Mozilla, Microsoft, and Google. Commercial support is offered via the related domain locust.cloud, indicating a hybrid open source and service business model. Technically, the website employs modern web technologies including Python-based backend, JavaScript, Google Fonts, Twitter widgets, and GitHub integration. Hosting and DNS services are managed through Cloudflare, ensuring reliable performance and security. The site is well-optimized for mobile devices, accessible, and SEO-friendly, with fast loading times and clear navigation. However, some security best practices such as DNSSEC and security headers are not enabled, and privacy compliance documentation is absent. From a security perspective, the site uses HTTPS and has domain transfer protections in place. No vulnerabilities or exposed sensitive data were detected in the content. The WHOIS data is transparent and consistent with the business identity, enhancing trustworthiness. Nonetheless, the absence of privacy and cookie policies, security incident contacts, and vulnerability disclosure mechanisms represent compliance and security posture gaps. Overall, Locust.io presents a professional, trustworthy, and technically mature platform with room for improvement in privacy compliance and security policy transparency. Strategic enhancements in these areas would strengthen user trust and regulatory adherence.

Scanned

NIS2 and GDPR posture

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

10 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  2. 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 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';…

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

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

Keep watching locust.io

This scan found 28 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. See sample alerts.

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
47
Security headers
30
Email security
40
DNS health
70
Network security
100
GDPR outside view
35
Average
54

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

Locust.io occupies a strong position in the technology sector as a specialized open source load testing tool with a clear target audience of developers and performance engineers. Its business model combines free open source software with optional commercial cloud-hosted services and support, enabling diversified revenue streams. The project benefits from a vibrant contributor ecosystem and endorsements from major technology companies, which serve as significant competitive advantages. The partnership with locust.cloud extends its market reach into hosted solutions. Growth indicators include active community engagement and continuous development. The company operates primarily from Sweden, with no subsidiaries or parent company indicated. The website content and branding are consistent and professional, supporting a credible market presence.

Security posture

The security posture of locust.io is solid but not comprehensive. HTTPS is enforced, and domain transfer protections are active, reducing risks of domain hijacking. The use of Cloudflare for DNS and likely CDN services adds resilience and mitigates some attack vectors. However, the lack of DNSSEC implementation and absence of key security headers such as Content-Security-Policy and Strict-Transport-Security are notable gaps. No explicit privacy or security policies are published, and no incident response or vulnerability disclosure contacts are provided, which could hinder timely security communications. No vulnerabilities or sensitive data exposures were found in the analyzed content. Overall, the site demonstrates good baseline security but should enhance transparency and technical controls to improve compliance and risk management.

Recommendations

  1. Enable DNSSEC to strengthen DNS security and prevent spoofing.
  2. Publish comprehensive privacy and cookie policies with GDPR compliance details.
  3. Implement and configure security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Provide explicit contact information for security incidents and consider publishing a security.txt file.
  5. Enhance user trust by adding terms of service and vulnerability disclosure policies.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Heylab AB
Description
An open source load testing tool. Define user behaviour with Python code, and swarm your system with millions of simultaneous users.
Key services
Open source load testing framework, Distributed load testing, Commercial support via Locust.cloud
Content quality
excellent
Branding
consistent

Technology

Stack
Python, JavaScript, Google Fonts, Twitter Widgets, GitHub Buttons, Google Analytics
Frameworks
Locust (Python load testing framework)
Platforms
GitHub, Cloudflare DNS
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced (implied by https:// URLs)
  • Domain status clientTransferProhibited to prevent unauthorized transfers
  • No exposed sensitive data in HTML content

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
poor

Advertising

Marketing tools
Twitter Widgets
Transparency
basic

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 no blocking mechanisms.
  2. No explicit privacy, cookie, or terms of service policies found on the main page.
  3. Strong open source community presence with many contributors and maintainers listed.
  4. Use of modern web technologies and integration with social media and analytics.
  5. No direct contact emails or phone numbers visible on the main page.
  6. No security.txt or vulnerability disclosure information found.
  7. Domain WHOIS data is transparent and consistent with the business.
Technical notes

Notes

The website is built on a modern technology stack centered around Python and JavaScript, leveraging open source frameworks and libraries. It integrates Google Fonts for typography, Twitter widgets for social engagement, and GitHub buttons for community interaction. Hosting and DNS are managed via Cloudflare, providing performance and security benefits. The site is mobile-optimized, accessible, and SEO-friendly with proper meta tags and Open Graph data. Performance is fast with no broken elements detected. However, there is no detected CMS, indicating a custom or static site approach. The absence of DNSSEC and security headers suggests some technical debt in security hardening. Overall, the infrastructure is robust and well-maintained but could benefit from additional security and privacy 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 locust.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 locust.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.