Skip to main content

Security report for git-scm.org

Git · Technology · N/a

Medium risk. 9 critical or high findings in Email security, Security headers and 2 other checks.

Security score

59/100

Risk levelMedium

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

Git-scm.com is the official website for Git, a widely used free and open source distributed version control system. The site provides comprehensive resources including documentation, tools, community links, and download options for Git software. It targets developers and IT professionals seeking efficient version control solutions. The website is mature, well-branded, and positioned as a leader in the version control market with a strong open source community backing. Technically, the site is built using the Hugo static site generator and leverages modern JavaScript libraries such as jQuery and jQuery UI. It is hosted behind Cloudflare DNS and likely CDN services, ensuring fast performance and good availability. The site is mobile optimized and has a clear navigation structure, though accessibility features are basic. SEO optimization is present but could be enhanced. From a security perspective, the site uses HTTPS and has domain transfer protections enabled. However, DNSSEC is not enabled, and no explicit security headers or policies are published on the site. There is no visible privacy or cookie policy, nor incident response or vulnerability disclosure information, which are areas for improvement. No vulnerabilities or exposed sensitive data were detected. Overall, the website is trustworthy, professional, and provides valuable content for its audience. Strategic recommendations include publishing privacy and cookie policies, enabling DNSSEC, adding security headers, and providing clear security and incident response information to enhance compliance and trust.

Scanned

NIS2 and GDPR posture

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

9 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

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

  3. GDPR outside view

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

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

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

Keep watching git-scm.org

This scan found 26 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
57
Security headers
15
Email security
60
DNS health
70
Network security
100
GDPR outside view
50
Average
59

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

Git is positioned as a leading open source version control system with a strong community and extensive documentation. Its business model revolves around free software distribution and community-driven development. The website supports this by offering learning resources, tools, and community engagement channels. The presence of affiliate links to Amazon for the Pro Git book indicates a modest revenue stream. The target audience is primarily developers and IT professionals globally. The project is mature, founded in 2008, and maintains a consistent brand identity. Partnerships with platforms like GitHub and kernel.org reinforce its ecosystem integration. The lack of direct business contact information suggests a community-centric rather than commercial focus.

Security posture

The security posture of git-scm.com is moderate. The site benefits from HTTPS and domain transfer lock status, which are fundamental protections. However, the absence of DNSSEC, security headers, and published security policies limits its security maturity. No incident response or vulnerability disclosure mechanisms are visible, which could hinder timely handling of security issues. The site does not appear to collect personal data aggressively, reducing privacy risks, but the lack of privacy and cookie policies is a compliance gap. Overall, the site is secure for informational and software distribution purposes but could improve transparency and technical security controls.

Recommendations

  1. Enable DNSSEC on the domain to protect against DNS spoofing and improve DNS security.
  2. Publish a comprehensive privacy policy and cookie policy to comply with GDPR and other privacy regulations.
  3. Implement and configure security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  4. Provide explicit security and incident response policies including contact channels for reporting vulnerabilities.
  5. Add a cookie consent mechanism if cookies are used to enhance user privacy and compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Git
Description
Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. It is easy to learn, has a tiny footprint with lightning fast performance, and offers advanced features like cheap local branching, staging areas, and multiple workflows.
Key services
Version control system software, Documentation and learning resources, Tools and GUIs, Community support and development
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, jQuery, jQuery UI, Hugo static site generator
Performance
fast
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
70/100
Good practices seen
  • Use of HTTPS (implied by URL https://git-scm.com/)
  • Domain status clientTransferProhibited

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. No explicit privacy, cookie, or terms of service policies found on the homepage content.
  3. No contact emails or phone numbers explicitly listed on the homepage.
  4. Website uses modern JavaScript libraries and static site generator Hugo.
  5. Content is focused on Git software, documentation, and community resources.
  6. External links include GitHub, Amazon, kernel.org, and ICANN.
  7. No security.txt or vulnerability disclosure information found.
  8. No explicit security or incident response contact information found.
  9. Website branding is consistent with Git project identity.
  10. No advertising networks or tracking pixels detected except affiliate link to Amazon.
Technical notes

Notes

The website is built using the Hugo static site generator, which provides fast and reliable content delivery. It uses JavaScript libraries including jQuery and jQuery UI for interactive elements. Hosting is supported by Cloudflare DNS and likely CDN services, contributing to fast load times and availability. The site is mobile optimized with responsive design and clear navigation. SEO is basic but present. There is no evidence of a traditional CMS, reducing attack surface. The technical stack is modern and well-suited for a documentation and software distribution site. Opportunities exist to enhance accessibility and SEO further.
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 git-scm.org. 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 git-scm.org.

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.