Skip to main content

Security report for go.dev

Google · Technology · United States

Medium risk. 4 critical or high findings in Email security, Security headers and 1 other check.

Security score

69/100

Risk levelMedium

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

The website go.dev is the official site for the Go programming language, an open source language developed and supported by Google. It serves as a comprehensive resource hub for developers, offering documentation, learning materials, downloads, and community engagement. The site is well-positioned in the technology sector as a leading programming language platform with strong industry adoption and backing by a major enterprise, Google. The content is highly relevant to software developers and teams focused on building scalable, secure systems. From a technical perspective, the website employs modern web technologies including HTML5, CSS3, JavaScript, and integrates Google Tag Manager and Analytics for performance and user behavior tracking. The site is hosted on Google infrastructure, ensuring fast performance and excellent mobile optimization. Accessibility and SEO practices are well implemented, contributing to a positive user experience. Security-wise, the site enforces HTTPS and uses best practices such as asynchronous loading of analytics scripts. However, it lacks explicit security policy documentation and incident response contact information, which are recommended for transparency and trust. No vulnerabilities or exposed sensitive data were detected in the content. Privacy and cookie policies are present and link to Google's official policies, indicating good compliance with GDPR and related regulations. Overall, the website demonstrates a high level of professionalism, trustworthiness, and technical maturity. The domain registration details align with the business claims, reinforcing legitimacy. Strategic recommendations include publishing dedicated security and incident response policies, enhancing security headers, and maintaining regular audits of third-party scripts to further strengthen security posture.

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. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

    • High

      No SPF record found

      SPF helps prevent email spoofing

      What to do: Add SPF record: "v=spf1 include:_spf.yourmailprovider.com ~all"

  2. 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"

  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

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

Keep watching go.dev

This scan found 22 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
62
Security headers
45
Email security
40
DNS health
80
Network security
100
GDPR outside view
88
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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention go.dev, from OffSeq Breach.

No leaked records found

Breach holds no records for go.dev right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Go.dev operates as a flagship platform for the Go programming language, targeting developers and organizations building scalable software systems. Its business model revolves around open source software development supported by Google, leveraging a strong ecosystem of partners and community contributors. The site highlights case studies from major companies, indicating broad industry adoption and a robust partnership network. Revenue streams are indirect, primarily through Google’s broader ecosystem and cloud services. The platform’s growth is supported by extensive learning resources, community events, and integration with cloud providers. Strategic observations include the importance of maintaining strong community engagement and expanding enterprise adoption through enhanced tooling and support.

Security posture

The website exhibits a mature security posture with enforced HTTPS and no visible security vulnerabilities. The use of Google-managed analytics and tag management ensures reliable and secure data collection. However, the absence of a dedicated security policy page and incident response contacts represents a compliance gap and potential risk in transparency. There is no evidence of a security.txt file or vulnerability disclosure program, which are best practices for open source projects. Data protection practices appear aligned with GDPR through links to Google's privacy policies. Incident response readiness and security culture indicators are not explicitly documented, suggesting room for improvement in formal security governance and communication.

Recommendations

  1. Publish a dedicated security policy page outlining security practices and commitments.
  2. Provide clear incident response contact information, including security@ or abuse@ email addresses.
  3. Implement and publish a security.txt file to facilitate vulnerability disclosures.
  4. Enhance HTTP security headers such as Content-Security-Policy and X-Content-Type-Options.
  5. Conduct regular security audits of third-party scripts and dependencies to mitigate risks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Google
Description
Go is an open source programming language that makes it simple to build secure, scalable systems.
Key services
Programming language development, Documentation and learning resources, Package hosting and management, Community engagement and support
Content quality
excellent
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, Google Tag Manager, Google Analytics, Material Icons, Custom JavaScript
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of Google Tag Manager and Analytics with async loading

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 professionally designed and well-structured.
  2. Content is comprehensive and targeted at developers and technical audiences.
  3. Strong branding consistency with Google and Go programming language.
  4. No signs of malicious or suspicious activity.
  5. Good use of modern web technologies and analytics.
  6. Lacks explicit security policy and incident response contact pages.
  7. Privacy and cookie policies are present and linked to Google's official policies.
Technical notes

Notes

The website is built on a custom CMS or static site architecture using modern web standards including HTML5, CSS3, and JavaScript. It integrates Google Tag Manager and Google Analytics for tracking and performance monitoring. Hosting is provided by Google, ensuring high availability and fast load times. The site is mobile optimized with responsive design and accessibility features such as skip navigation links and ARIA labels. SEO is supported through proper meta tags and Open Graph data. There is no use of common CMS platforms like WordPress or Drupal, indicating a tailored solution. Technical risks are minimal but include reliance on third-party analytics scripts which should be regularly audited.
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 go.dev. 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 go.dev.

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.