Skip to main content

Security report for ltad.com

Waymo LLC · Transportation · United States

Low risk. 5 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

77/100

Risk levelLow

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

Waymo LLC operates a comprehensive and professionally designed website focused on community engagement around autonomous vehicle technology. The company is a recognized leader in the transportation and technology sectors, with a strong market position as an innovator in autonomous ride-hailing services. The website content emphasizes safety, community partnerships, and impact, targeting a broad audience including riders, partners, and stakeholders. Technically, the site employs modern web technologies, extensive third-party analytics, and advertising pixels, hosted likely on Google Cloud infrastructure, ensuring fast performance and excellent mobile optimization. Security posture is strong with HTTPS enforcement and domain lock statuses, though DNSSEC is not enabled and no explicit security or incident response policies are published on this page. Privacy compliance is well addressed with clear privacy and cookie policies and consent mechanisms. Overall, the site is trustworthy, professional, and aligned with the business identity of Waymo LLC, a subsidiary of Alphabet Inc.

Scanned

NIS2 and GDPR posture

GDPR outside view
58/ 100 · Medium
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 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. GDPR outside view

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

    • 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

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

This scan found 15 issues across 5 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
49
Security headers
65
Email security
100
DNS health
90
Network security
100
GDPR outside view
58
Average
77

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

Waymo's market positioning as a pioneer in autonomous driving is supported by its extensive community outreach and partnerships, as reflected on the website. The business model centers on autonomous ride-hailing services complemented by community engagement and safety advocacy. Revenue streams likely include ride services and technology licensing. The company targets urban riders and community organizations, with growth indicated by expansion into multiple cities and partnerships with Uber. The partnership ecosystem includes community organizations and technology platforms, enhancing brand trust and market reach. Strategic observations highlight Waymo's focus on safety, innovation, and social impact as competitive advantages.

Security posture

The website demonstrates a mature security posture with HTTPS enforced and multiple domain lock statuses to prevent unauthorized changes. The absence of DNSSEC is a minor gap. No exposed sensitive data or vulnerable libraries were detected. However, the lack of a dedicated security policy or incident response contact on this page suggests room for improvement in transparency and readiness. The extensive use of third-party tracking pixels requires careful privacy management, which appears to be addressed through consent mechanisms and privacy policies. Overall, the security maturity is high but could benefit from publishing vulnerability disclosure and incident response information.

Recommendations

  1. Enable DNSSEC to enhance DNS security and prevent spoofing.
  2. Publish a dedicated security policy and incident response contact information to improve transparency and readiness.
  3. Consider implementing and publishing a vulnerability disclosure policy or security.txt file.
  4. Review and minimize third-party tracking where possible to enhance user privacy.
  5. Maintain and regularly update privacy and cookie consent mechanisms to ensure ongoing compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Waymo LLC
Description
Waymo supports a diverse set of communities and organizations, working together to build a future where everyone can travel safely and with ease.
Key services
Autonomous ride-hailing, Community engagement, Partnerships with organizations, Safety research and impact
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript ES Modules, Google Tag Manager, Google Analytics, Facebook Pixel, TikTok Analytics, Twitter Universal Website Tag, Snapchat Pixel, Reddit Pixel, Adform (adsrvr.org), Preload and Prefetch for performance optimization, WebP and responsive images
Frameworks
Custom Web Components, Google Tag Manager
Platforms
Google Cloud Storage (for assets), MarkMonitor (Registrar), Google DNS
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Domain locked with multiple EPP status codes
  • No DNSSEC (not enabled)
  • No exposed sensitive data in HTML
  • Use of consent mechanism for cookies
  • No visible vulnerable libraries

Analytics and tracking

Services
Google Analytics, Facebook Analytics, TikTok Analytics, Twitter Analytics, Snapchat Analytics, Reddit Analytics
Tracking level
extensive
Privacy practices
good

Advertising

Ad networks
Tribal Fusion, AppNexus (acdn.adnxs.com), Adform (adsrvr.org)
Tracking pixels
Facebook Pixel, TikTok Pixel, Twitter Pixel, Snapchat Pixel, Reddit Pixel
Transparency
good

Site quality

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

Key observations

  1. Website is professionally designed with clear navigation and rich content.
  2. Strong focus on community engagement and safety in autonomous vehicle technology.
  3. Extensive use of third-party analytics and advertising pixels indicating robust marketing efforts.
  4. No signs of blocking or WAF challenges; content fully accessible.
  5. No direct contact emails or phone numbers found on this page; contact likely centralized elsewhere.
  6. No explicit security or incident response policies found on this page.
  7. DNSSEC not enabled, which is a minor security improvement opportunity.
Technical notes

Notes

The website uses a modern tech stack including JavaScript ES modules, custom web components, and integrates multiple analytics and advertising platforms. Hosting appears to be on Google Cloud infrastructure, contributing to fast load times and excellent mobile optimization. The site employs performance optimizations such as preloading fonts and prefetching key pages. Accessibility features and SEO optimizations are well implemented. There is no explicit CMS detected, suggesting a custom or proprietary solution. Technical risks are minimal, with no visible outdated or vulnerable libraries. Opportunities exist to enable DNSSEC and enhance security policy transparency.
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 ltad.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 ltad.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.