Skip to main content

Security report for mulesoft.com

MuleSoft · Technology · N/a

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

Security score

81/100

Risk levelLow

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

MuleSoft is a leading enterprise software company specializing in integration and automation platforms designed for the AI era. As a Salesforce company, it offers a unified platform to build AI-ready foundations, enabling organizations to deliver integrated, automated, and AI-powered experiences. The website targets IT leaders, developers, and enterprises seeking to modernize their API and integration strategies with advanced AI governance and orchestration capabilities. The platform's market position is strong, supported by comprehensive product offerings and a consistent brand presence. Technically, the website is built on Salesforce Experience Cloud using Lightning Web Components, leveraging modern web technologies and third-party services such as Google Analytics, Optimizely, and OneTrust for consent management. The site demonstrates excellent performance, mobile optimization, accessibility, and SEO practices, reflecting a mature digital infrastructure. From a security perspective, the site enforces HTTPS, employs robust security headers, and integrates cookie consent mechanisms, indicating a solid security posture. However, explicit security policies, incident response information, and vulnerability disclosure mechanisms are not publicly available, representing areas for improvement. The WHOIS data is unavailable publicly, likely due to privacy protection, but the domain and website content align with a legitimate enterprise entity. Overall, the website presents a professional, trustworthy, and secure digital presence suitable for its enterprise audience, with recommendations to enhance transparency around security policies and incident response to further strengthen trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
88/ 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 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 mulesoft.com

This scan found 15 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
62
Security headers
65
Email security
85
DNS health
85
Network security
100
GDPR outside view
88
Average
81

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

MuleSoft operates in the technology sector as an essential enterprise software provider focused on API-led integration and automation. Its business model revolves around delivering a comprehensive platform that supports AI agent governance, orchestration, and multi-agent collaboration. The company targets large enterprises and IT leaders aiming to modernize their integration infrastructure and leverage AI capabilities. Revenue streams likely include platform subscriptions, professional services, and support. The partnership with Salesforce enhances its market reach and credibility. The website content and product portfolio indicate continuous innovation and alignment with emerging AI trends, positioning MuleSoft competitively in the integration platform market.

Security posture

The website exhibits a mature security posture with enforced HTTPS, modern security headers, and integration of consent management tools compliant with GDPR. No exposed sensitive data or vulnerable libraries were detected in the HTML content. However, the absence of a publicly accessible security policy, incident response page, or vulnerability disclosure program limits transparency. There is no visible contact for security incidents or a security.txt file. Compliance with privacy regulations is evident through detailed privacy and cookie policies. The security score is high but could be improved by publishing explicit security governance documentation and incident response procedures.

Recommendations

  1. Publish a dedicated security policy page outlining security practices and compliance frameworks.
  2. Establish and publicize an incident response contact channel and procedures.
  3. Implement and link to a vulnerability disclosure program or security.txt file.
  4. Enhance transparency by listing security certifications and compliance attestations.
  5. Maintain and regularly update privacy and cookie policies to reflect evolving regulations.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
MuleSoft
Description
Build an AI-ready foundation with the all-in-one platform from MuleSoft. Deliver integrated, automated, and AI-powered experiences.
Key services
API management, Integration platform, Automation tools, AI agent governance and orchestration
Content quality
excellent
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, Salesforce Lightning Web Components, Google Tag Manager, Google Analytics, Optimizely, OneTrust Consent Management, Boomerang (performance monitoring)
Frameworks
Salesforce Digital Experience, LWC (Lightning Web Components)
Platforms
Salesforce, Google Cloud (implied by Google services)
Performance
fast
Mobile
excellent
Accessibility
good
SEO
excellent

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Use of CSP
  • Cookie consent mechanism
  • No exposed sensitive data in HTML
  • Secure forms with consent

Analytics and tracking

Services
Google Analytics, Boomerang
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Adobe Demdex, Evergage
Marketing tools
Optimizely, Boomerang, OneTrust
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 multimedia.
  2. No signs of WAF or blocking mechanisms.
  3. Strong use of Salesforce and Google technologies.
  4. Comprehensive privacy and cookie policies with consent management.
  5. No direct contact emails or phone numbers found; contact via forms.
  6. No explicit security policy or incident response page found.
  7. WHOIS data unavailable publicly, likely privacy protected.
  8. High-quality branding and consistent design.
  9. No adult or questionable content detected.
Technical notes

Notes

The website is built on a robust technical infrastructure leveraging Salesforce Experience Cloud and Lightning Web Components, ensuring scalability and maintainability. It uses modern web standards (HTML5, CSS3, JavaScript) and integrates advanced analytics and consent management tools. Performance optimizations such as preloading fonts and asynchronous script loading are implemented. The site is mobile-optimized and accessible, with strong SEO metadata and Open Graph tags for social sharing. Hosting appears to be on Salesforce's secure cloud infrastructure. Technical risks are minimal, with no signs of outdated or vulnerable components. Opportunities exist to further enhance security transparency and incident readiness.
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. 83/100 +1Low20 findingsView report
  2. 82/100Low21 findingsView report
Reviews of this site

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