Skip to main content

Security report for xyleminc.com

Xylem Inc. · Energy · United States

High risk. 5 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

47/100

Risk levelHigh

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

Xylem Inc. is a leading enterprise specializing in innovative water solutions and water technology, serving diverse sectors including energy, municipal water, healthcare, and manufacturing. The company offers a broad portfolio of products and services such as water and wastewater treatment systems, pumps, digital water solutions, and parts and supplies. Their market position is strong with a global footprint and multiple subsidiary brands. The website reflects a professional and comprehensive digital presence with excellent content quality and consistent branding. Technically, the site uses modern JavaScript frameworks, Google Tag Manager for analytics, and is hosted behind Cloudflare, but lacks a valid SSL certificate, which significantly impacts its security posture. Security headers are present but the absence of HTTPS and related SSL/TLS features lowers the overall security score. Privacy policies and terms of service are well documented, though no explicit cookie consent mechanism was detected. Contact information is primarily via contact forms with no direct emails or phone numbers found. Overall, the site is trustworthy and professional but requires urgent improvements in SSL/TLS implementation to enhance security and user trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
18/ 100 · Critical
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. GDPR outside view

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

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

    • 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

    • 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

  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.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

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

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

Keep watching xyleminc.com

This scan found 14 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
0
Security headers
65
Email security
50
DNS health
50
Network security
100
GDPR outside view
18
Average
47

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

Xylem operates a B2B business model focused on water technology solutions, targeting utilities, industrial clients, and municipalities. Their competitive advantage lies in a wide range of patented technologies and a strong global brand portfolio. The company leverages digital tools and analytics to support water sustainability and efficiency. The website indicates active engagement with customers through case studies, news, and support resources. Partnerships and subsidiaries are well integrated, enhancing market reach. Growth indicators include innovation labs and sustainability initiatives. The company maintains a strong social media presence and provides extensive product and service information online.

Security posture

The website demonstrates a moderate security maturity level with several best practices such as security headers and secure cookie flags. However, the lack of a valid SSL certificate and disabled HTTPS protocols is a critical vulnerability that exposes users to risks such as data interception and man-in-the-middle attacks. No known vulnerabilities like Heartbleed or POODLE were detected. The absence of OCSP stapling and session resumption indicates room for improvement in SSL/TLS performance and security. No explicit incident response or vulnerability disclosure policies were found, which could be enhanced to improve security culture and transparency. Overall, the security posture is weakened by the missing HTTPS implementation despite other positive controls.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable and configure HSTS with includeSubDomains and preload flags to enforce HTTPS.
  3. Implement OCSP stapling and session resumption to improve SSL performance and security.
  4. Add a cookie consent mechanism to comply with privacy regulations and enhance user trust.
  5. Publish a vulnerability disclosure policy and security.txt file to improve transparency and incident response readiness.
Technical notes

Notes

The website is built on EPiServer (Optimizely CMS) and uses modern JavaScript libraries and FontAwesome icons. It is hosted behind Cloudflare, providing CDN and security services. Google Tag Manager is used for analytics and marketing tracking. The site is mobile optimized with good navigation and SEO meta tags. However, performance metrics are missing or zero, suggesting a need for performance monitoring and optimization. Accessibility features are basic but present. The lack of HTTPS and valid SSL certificate is a major technical risk. The site structure and content are well organized, supporting a positive user experience and professional appearance.
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 xyleminc.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 xyleminc.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.