Skip to main content

Security report for supplier.io

Supplier.io · Technology · United States

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

Security score

69/100

Risk levelMedium

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

Supplier.io is a US-based technology company specializing in supplier diversity and intelligence software solutions. The company offers a comprehensive SaaS platform that enables enterprise procurement teams to track, source, and measure the impact of working with small, diverse, and sustainable suppliers. Their market position is strong as a leading supplier diversity solution provider with a focus on ESG initiatives and responsible sourcing. The website reflects a mature digital presence with excellent content quality, professional design, and clear navigation tailored to their B2B audience. Technically, the site is built on WordPress with integrations such as HubSpot forms, Google Tag Manager, and CookieYes for consent management, hosted behind Cloudflare for performance and security. Security posture is robust with HTTPS, domain locking, and bot protection via Google reCAPTCHA, though DNSSEC is not enabled and no explicit security or incident response policies are published. Privacy compliance is well addressed with clear privacy and cookie policies and GDPR consent mechanisms. Overall, the website and domain registration data indicate a trustworthy and credible business with a solid online presence.

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 supplier.io

This scan found 23 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
57
Security headers
15
Email security
80
DNS health
80
Network security
100
GDPR outside view
83
Average
69

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

Supplier.io operates in the technology sector, focusing on procurement software for supplier diversity and ESG reporting. Their business model is B2B SaaS targeting enterprise procurement teams seeking to enhance supplier visibility, sourcing, and impact measurement. The company was founded in 2011 and has a medium-sized workforce. Their platform offers data enrichment, analytics, supplier discovery, economic impact analysis, and sustainability reporting. The website showcases a broad partnership ecosystem with logos of notable clients and integrates marketing and analytics tools such as HubSpot, Google Analytics, and Hotjar. The company maintains consistent branding and professional content, supporting its market leadership claims. No parent or subsidiary companies are identified. The absence of direct contact emails or phone numbers on the site suggests a focus on lead generation via forms and demos.

Security posture

The website demonstrates a mature security posture with HTTPS enforced, domain transfer protection, and bot mitigation via Google reCAPTCHA. Cookie consent is managed through CookieYes, providing users control over tracking categories. Security headers are implied but not explicitly detailed in the HTML content. No security.txt or vulnerability disclosure policy is found, which could improve transparency and incident response readiness. No exposed sensitive data or vulnerable libraries were detected. The use of third-party scripts is standard for marketing and analytics but should be regularly audited. Overall, the security posture is good but could be enhanced by enabling DNSSEC and publishing explicit security policies and incident response contacts.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Publish a security.txt file to provide clear vulnerability disclosure and incident response contacts.
  3. Create and publish a dedicated security policy page outlining security frameworks and practices.
  4. Add explicit incident response contact channels such as security@ or abuse@ emails.
  5. Regularly review and audit third-party scripts and cookies to minimize privacy and security risks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Supplier.io
Description
Supplier.io is a supplier diversity software company that empowers procurement teams to manage, measure, and grow their supplier diversity and ESG initiatives. It provides advanced supplier intelligence and expert guidance to help organizations track spending with small, diverse, and sustainable suppliers, discover new qualified vendors, and measure community impact.
Key services
Supplier diversity software, Supplier visibility and data, Supplier discovery and vetting, Economic impact analysis, Responsible sourcing management, Sustainability and ESG reporting
Content quality
excellent
Branding
consistent

Technology

Stack
WordPress, Yoast SEO, HubSpot Forms, Google Tag Manager, CookieYes Consent Management, Swiper.js, jQuery
Frameworks
WordPress
Platforms
HubSpot
Performance
moderate
Mobile
excellent
Accessibility
good
SEO
excellent

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Domain locked with clientTransferProhibited status
  • Use of Google reCAPTCHA for spam protection
  • Cookie consent mechanism implemented

Analytics and tracking

Services
Google Analytics, Hotjar, HubSpot Analytics
Tracking level
extensive
Privacy practices
good

Advertising

Ad networks
Google DoubleClick, Facebook Ads, LinkedIn Ads
Tracking pixels
Hotjar, Facebook Pixel, HubSpot Tracking
Marketing tools
HubSpot, CookieYes
Transparency
good

Site quality

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

Key observations

  1. Website uses modern web technologies and is well optimized for SEO and mobile.
  2. Strong privacy and cookie consent mechanisms are implemented.
  3. No exposed sensitive data or security vulnerabilities detected in the content.
  4. WHOIS data supports legitimacy and consistent business identity.
  5. No explicit security policy or incident response contacts published.
  6. No terms of service page found.
Technical notes

Notes

The website is built on WordPress CMS with a modern tech stack including Yoast SEO for optimization, HubSpot for marketing and form management, Google Tag Manager for analytics, and CookieYes for cookie consent management. Hosting is provided via Cloudflare, offering CDN and security benefits. The site is mobile-optimized with responsive design and good accessibility features. Performance is moderate, with some reliance on external scripts which may impact load times. SEO is well implemented with comprehensive meta tags, Open Graph, and JSON-LD structured data. The technical infrastructure supports a professional and scalable online presence suitable for enterprise clients.
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 supplier.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 supplier.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.