Skip to main content

Security report for googlesource.com

Google Open Source · Technology · United States

Medium risk. 4 critical or high findings in Security headers, SSL/TLS and 1 other check.

Security score

72/100

Risk levelMedium

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

Google Open Source is a dedicated platform by Google LLC that promotes and supports open source software development. The website serves as a hub for Google's open source projects, programs, and community engagement initiatives. It targets developers and contributors worldwide, providing resources, documentation, and program information such as Google Summer of Code. The site is professionally designed, mobile-optimized, and offers multilingual support, reflecting Google's high digital maturity and commitment to accessibility and SEO best practices. Technically, it leverages Google's proprietary Devsite framework, Google Fonts, Material Icons, and integrates Google Analytics and Tag Manager for performance and user behavior insights. Security posture is strong with HTTPS enforced and no visible vulnerabilities or exposed sensitive data, although explicit security headers and a public security policy page are not detected. Privacy compliance is robust, linking to Google's comprehensive privacy and cookie policies with consent mechanisms in place. Overall, the domain registration and WHOIS data confirm the site's legitimacy as an official Google property. The website is safe for general audiences with no adult or questionable content detected.

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

4 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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

  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
  3. DNS health

    DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.

    • High

      Weak SPF Policy

      SPF record has permissive policy allowing any server to send email

      What to do: Use -all or ~all qualifier for better email security

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

Keep watching googlesource.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. 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
52
Security headers
60
Email security
60
DNS health
70
Network security
100
GDPR outside view
88
Average
72

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

Google Open Source holds a leading position in the technology sector by actively contributing to and supporting open source software. Its business model revolves around fostering innovation and collaboration through open source projects and programs, which indirectly supports Google's broader ecosystem and product development. The platform's extensive use of Google technologies and integration with Google's corporate policies and analytics tools indicate a mature and well-supported digital infrastructure. The absence of direct contact information suggests a focus on community-driven engagement rather than direct customer service. The presence of official social media channels enhances its outreach and community interaction. The platform's strategic partnerships are primarily internal within Google and the open source community, with no external commercial partners explicitly listed.

Security posture

The website demonstrates a mature security posture with HTTPS enforced and no signs of exposed sensitive information or vulnerable libraries. The use of Google-managed infrastructure and analytics tools adds to the security reliability. However, the absence of explicit security headers like Content-Security-Policy and a publicly available vulnerability disclosure or incident response contact reduces transparency in security practices. No security policy or data protection officer information is provided on the site. The site does not expose any forms that collect sensitive data beyond standard search functionality, minimizing attack surface. Overall, the security posture is strong but could be improved by publishing dedicated security and incident response information.

Recommendations

  1. Implement and publish a dedicated security policy and vulnerability disclosure page to enhance transparency and community trust.
  2. Add explicit security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to strengthen browser security.
  3. Provide clear incident response contact channels, such as security@ or abuse@ email addresses, to facilitate vulnerability reporting.
  4. Consider adding contact information or a contact form for business or security inquiries to improve communication.
  5. Regularly audit third-party scripts and dependencies to ensure no vulnerable libraries are included.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Google Open Source
Description
Google Open Source brings the value of open source to Google and shares Google's resources with the open source community. It supports open source innovation, collaboration, and sustainability through various programs and services.
Key services
Open source projects, Open source programs and services, Mentorship and contributor enablement, Documentation support
Content quality
excellent
Branding
consistent

Technology

Stack
Google Tag Manager, Google Analytics, Google Fonts, Material Icons, Progressive Web App (manifest.json), Custom Google Devsite JS modules
Platforms
Web
Performance
fast
Mobile
excellent
Accessibility
excellent
SEO
excellent

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Use of Google security infrastructure
  • No exposed sensitive data in HTML
  • Secure sign-in URLs with OAuth client IDs

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
good

Advertising

Transparency
good

Site quality

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

Key observations

  1. Website is a professionally maintained Google property focused on open source software.
  2. Content is comprehensive and well-structured with multiple language support.
  3. No contact emails or phone numbers explicitly listed on the site.
  4. Strong use of Google technologies and analytics.
  5. No security or privacy policy pages hosted on the domain but links to Google's central policies are provided.
  6. No vulnerability disclosure or security.txt found.
  7. No incident response or security contact information found.
  8. No suspicious or malicious content detected.
Technical notes

Notes

The website is built on Google's proprietary Devsite framework, optimized for performance and accessibility. It uses modern web technologies including Google Fonts, Material Icons, and progressive web app features. The site is hosted on Google Cloud Platform, ensuring high availability and scalability. Analytics and tag management are implemented via Google Analytics and Google Tag Manager, providing detailed user insights. The site is mobile responsive and SEO optimized with proper meta tags and structured data (JSON-LD). No CMS other than Devsite is detected. The technical implementation reflects a high level of digital maturity with minimal technical debt and strong infrastructure support.
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. 73/100Medium28 findingsView report
Reviews of this site

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