Skip to main content

Security report for git.gay

Private by Design, LLC · Technology · United States

High risk. 5 critical or high findings in Network security, Security headers and 2 other checks.

Security score

49/100

Risk levelHigh

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

git.gay is a niche collaboration platform designed to empower queer developers by providing Git hosting, continuous integration, and static site hosting services. Operated by the collective 'besties', it emphasizes community values, open source software, and privacy by avoiding ads and third-party trackers. The platform leverages a fork of Forgejo, ensuring open source transparency and configurability. The website presents a professional and consistent brand image targeting queer and neurodiverse developers, positioning itself as a community-centric alternative to corporate platforms. Technically, git.gay uses modern web technologies including Forgejo, Cloudflare DNS, and custom JavaScript for enhanced user experience and error handling. The site is mobile optimized with good SEO practices and minimal user tracking, reflecting a mature digital infrastructure. However, DNSSEC is not enabled, and security headers are not visibly implemented, indicating areas for improvement in security hardening. From a security perspective, the site enforces HTTPS and employs CSRF tokens, with no detected vulnerabilities or exposed sensitive data. Privacy policies and terms of service are present but basic, and no explicit incident response or vulnerability disclosure policies are published. The absence of cookie consent mechanisms despite script usage suggests a potential compliance gap. Overall, the security posture is solid but could benefit from enhanced transparency and technical controls. The domain registration is transparent and consistent with the business profile, registered to Private by Design, LLC in the US, matching the website's operational claims. The domain age aligns with the platform's founding date, supporting legitimacy. No suspicious WHOIS patterns or privacy protections obscure ownership, enhancing trustworthiness. The platform's focus on community and open source principles further supports a positive risk profile. Strategic recommendations include enabling DNSSEC, implementing comprehensive security headers, publishing detailed security and incident response policies, adding cookie consent mechanisms, and establishing a vulnerability disclosure process. These steps will strengthen security, compliance, and user trust, supporting git.gay's mission as a safe and empowering platform for queer developers.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 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. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: PostgreSQL

      Port 5432 (PostgreSQL) is publicly accessible - PostgreSQL - Database server

      What to do: Immediately restrict access to PostgreSQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

  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 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 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

  4. 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 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 git.gay

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
75
Security headers
45
Email security
70
DNS health
75
Network security
0
GDPR outside view
53
Average
53
After the cap
49

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 · found on this site
  • 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.gay operates as a small, community-driven technology platform targeting queer and neurodiverse developers. Its competitive advantage lies in its niche focus, open source foundation, and privacy-centric approach, differentiating it from mainstream corporate Git hosting services. The business model appears to be service-oriented with free offerings supported by a collective ('besties'), possibly funded through donations as indicated by the donate link. The target customer segment is developers seeking inclusive, ad-free, and tracker-free collaboration tools. Growth indicators include active open source development and community engagement. The partnership with besties.house reflects a collaborative ecosystem. Strategic observations suggest git.gay prioritizes community trust and transparency over commercial scale, positioning it well within its niche but with limited mainstream market penetration.

Security posture

The security maturity of git.gay is moderate to good. HTTPS is enforced, and CSRF protections are in place, indicating awareness of common web security practices. The absence of DNSSEC and security headers like Content-Security-Policy or X-Frame-Options represents gaps that could be exploited. No public incident response or vulnerability disclosure policies limit transparency and readiness for security events. Privacy compliance is partial, with privacy and terms policies present but lacking cookie consent mechanisms. No exposed sensitive data or vulnerable libraries were detected. The minimal user tracking aligns with privacy goals but requires formal cookie management. Overall, the platform demonstrates a security-conscious culture but should enhance technical controls and policy transparency to improve resilience and compliance.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement comprehensive HTTP security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Publish detailed security policies including incident response and vulnerability disclosure procedures to increase transparency and preparedness.
  4. Add a cookie consent mechanism if any cookies or tracking scripts are used to comply with privacy regulations.
  5. Establish a security.txt file or similar vulnerability disclosure channel to facilitate responsible reporting and remediation.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Private by Design, LLC
Description
git.gay is a collaboration platform made to empower queer developers to create and share their projects with the world. It offers Git hosting, CI, and static site hosting.
Key services
Git hosting, Continuous Integration (CI), Static site hosting
Content quality
good
Branding
consistent

Technology

Stack
Forgejo (fork of Gitea), Cloudflare DNS, JavaScript, HTML5, CSS3
Frameworks
Forgejo
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • No third party trackers or cookies
  • CSRF token implemented in scripts

Analytics and tracking

Services
conscious.besties.house (custom script)
Tracking level
minimal
Privacy practices
good

Advertising

Transparency
excellent

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. Content is focused on queer developer community and open source collaboration.
  3. No contact emails or phone numbers explicitly provided on the main page.
  4. Privacy and terms policies are present but basic.
  5. No cookie consent mechanism detected despite use of cookies or scripts.
  6. Security headers are not explicitly visible in the HTML content.
  7. Use of Cloudflare DNS but DNSSEC not enabled.
  8. Custom emoji sets and branding consistent with community focus.
  9. No social media links explicitly found in the HTML content.
Technical notes

Notes

The website is built on a modern tech stack centered around Forgejo, a fork of Gitea, providing Git hosting and CI capabilities. Hosting utilizes Cloudflare DNS services, though DNSSEC is not enabled. The frontend employs standard HTML5, CSS3, and JavaScript with custom emoji sets and error handling scripts. Performance is moderate with good mobile optimization and SEO practices. Accessibility is basic but functional. The site lacks visible CMS usage, indicating a custom or framework-based build. Technical risks include missing DNSSEC and security headers, which could impact security posture. Opportunities exist to modernize security configurations and enhance accessibility features to improve overall technical robustness.
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.gay. 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.gay.

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.