Skip to main content

Security report for ppg.com

PPG Industries, Inc. · Manufacturing · United States

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

Security score

51/100

Risk levelMedium

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

PPG Industries, Inc. is a global leader in the manufacturing and distribution of paints, coatings, and specialty materials with a rich history spanning nearly 140 years. The company serves diverse markets including construction, automotive, industrial, and transportation, offering a broad portfolio of products and brands such as Comex, Sigma, Johnstone's, Dulux, and others. Their website reflects a mature digital presence with comprehensive content, clear navigation, and strong branding consistency. Technically, the site leverages modern frameworks like Angular and Express, hosted on Microsoft Azure, with integrations for search and consent management. However, a critical security issue is the absence of a valid SSL certificate and lack of modern TLS protocols, which significantly impacts the site's security posture. Privacy policies and cookie consent mechanisms are well implemented, indicating good compliance with GDPR and related regulations. Overall, the site demonstrates high business credibility and professionalism but requires urgent remediation of its SSL/TLS configuration to ensure secure user interactions.

Scanned

NIS2 and GDPR posture

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

6 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

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

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

Keep watching ppg.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
0
Security headers
15
Email security
75
DNS health
85
Network security
100
GDPR outside view
33
Average
51

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

PPG holds a strong market position as an enterprise-level manufacturer with a diversified product portfolio targeting both B2B and B2C segments. Their competitive advantage lies in their extensive brand portfolio, global reach, and commitment to sustainability and innovation. The business model integrates direct sales, distributor partnerships, and e-commerce platforms. The company targets industrial clients, automotive OEMs, contractors, and consumers globally. Growth indicators include active multi-language support, regional sites, and a robust digital infrastructure. The partnership ecosystem includes multiple subsidiary brands and specialized product lines. Strategic observations highlight PPG's focus on sustainability, innovation, and community engagement as key differentiators in the coatings industry.

Security posture

The current security posture of the website is moderate to poor due to the lack of a valid SSL certificate and disabled TLS protocols, which are critical for secure communications. While other security headers are present, the absence of HTTPS significantly undermines user trust and data protection. No known vulnerabilities such as Heartbleed or POODLE are detected, but the site lacks advanced security features like HSTS, OCSP stapling, and session resumption. Compliance with security frameworks is implied through ethical policies but not explicitly documented. Incident response mechanisms and vulnerability disclosure policies are not found, indicating potential gaps in security governance. The company should prioritize SSL/TLS remediation and consider implementing comprehensive security policies and incident response procedures.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate to enable HTTPS across all domains.
  2. Enable and enforce modern TLS protocols (TLS 1.2 and 1.3) and disable deprecated versions.
  3. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload options.
  4. Enable OCSP stapling to improve certificate revocation checks and reduce latency.
  5. Develop and publish a formal vulnerability disclosure policy and incident response plan.
  6. Enhance security headers with Content Security Policy (CSP) and X-Content-Type-Options.
  7. Regularly audit and update third-party libraries and dependencies to mitigate vulnerabilities.
  8. Maintain transparency on data protection officer contact and privacy compliance details.
  9. Improve performance metrics and accessibility features to enhance user experience.
  10. Continue leveraging consent management tools to ensure ongoing privacy compliance.
Technical notes

Notes

The website is built using Angular 17.3.2 with Express as the backend framework, hosted on Microsoft Azure. It integrates Algolia for search functionality and Didomi for consent management. The site uses PrimeNG UI components and is structured with Kentico CMS. Performance data is not available, but the site appears well-structured and mobile-optimized. However, the SSL/TLS configuration is currently invalid, with no active TLS protocols, which is a critical technical risk. The site uses modern web technologies but should address security and performance optimization to reduce technical debt and improve resilience. SEO is supported with comprehensive meta tags and Open Graph data. Accessibility and mobile optimization are rated good based on content and structure.
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 ppg.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 ppg.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.