Skip to main content

Security report for githack.com

Pavel Puchkin · Technology · N/a

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

Security score

63/100

Risk levelMedium

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

raw.githack.com is a specialized content delivery network service designed to serve source code files from popular Git hosting platforms such as GitHub, Bitbucket, GitLab, Gitea, and Codeberg. The service is operated by Pavel Puchkin and leverages Cloudflare's CDN infrastructure to provide fast, reliable, and optimized delivery of source code assets. The website offers URLs tailored for production use with permanent caching and development use with near real-time updates, targeting developers and software teams who require efficient source code file hosting and delivery. Technically, the website is well-implemented with modern HTML5, CSS, and JavaScript technologies, including third-party libraries like clipboard.js and integration with Cloudflare Insights for analytics. The site is mobile-optimized and performs well, with a clean and consistent design. However, it lacks explicit privacy, cookie, and terms of service policies, which impacts compliance and user trust. No contact information or security incident response details are provided, limiting transparency. From a security perspective, the site benefits from HTTPS enforced by Cloudflare and uses Cloudflare's CDN for DDoS protection. There are no visible security vulnerabilities or exposed sensitive data. However, the absence of security headers and vulnerability disclosure mechanisms suggests room for improvement in security best practices. The WHOIS data for the domain raw.githack.com is unavailable, indicating the domain may be unregistered or a special subdomain, which slightly reduces trustworthiness but does not negate the legitimacy of the service based on website content. Overall, raw.githack.com presents a niche, developer-focused CDN service with solid technical infrastructure and good performance. To enhance trust and compliance, the operator should consider publishing privacy and cookie policies, providing contact and security incident information, and improving security headers. The domain WHOIS ambiguity warrants monitoring but does not currently indicate malicious intent.

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

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

    • 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

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

Keep watching githack.com

This scan found 23 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
65
Security headers
15
Email security
70
DNS health
80
Network security
100
GDPR outside view
50
Average
63

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 githack.com, from OffSeq Breach.

Total records
48
Employees
0
Customers
48
Third parties
0
Weak passwords
17%

4 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for githack.com.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

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

Business context

Business profile

raw.githack.com operates in the technology sector, providing a free CDN service for source code files hosted on various Git platforms. Its business model appears to be service-oriented, focusing on developer convenience and leveraging Cloudflare's infrastructure to minimize operational costs. The service targets developers, open source contributors, and software teams needing reliable file delivery. The website's market position is niche but valuable within the developer tools ecosystem. Revenue streams are not explicit but may include sponsorships or donations as hinted by the '❤️' sponsorship link. The operator maintains transparency through source code availability on GitHub. The partnership ecosystem includes Cloudflare for CDN and carbonads.com for advertising. Growth indicators include a decade-long presence and continuous updates. Strategic observations suggest focusing on compliance and security transparency to strengthen market trust.

Security posture

The security posture of raw.githack.com is moderate to good. HTTPS is enforced, ensuring encrypted communications. The use of Cloudflare CDN provides inherent DDoS protection and performance benefits. No security headers such as Content-Security-Policy or X-Frame-Options were detected, which are recommended to mitigate common web attacks. The absence of a published security policy, incident response contacts, or vulnerability disclosure program limits the site's readiness for security incidents and transparency. No exposed sensitive data or vulnerable libraries were found. Compliance with GDPR or other privacy regulations is not evident due to missing privacy and cookie policies. Overall, the site demonstrates basic security hygiene but should enhance policies and headers to improve its security maturity and compliance posture.

Recommendations

  1. Publish comprehensive privacy and cookie policies to improve compliance and user trust.
  2. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Provide clear contact information for security incidents and abuse reporting.
  4. Implement a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  5. Monitor domain registration status and consider registering the domain if unregistered to improve legitimacy.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Pavel Puchkin
Description
A decade proven way to serve files from source code hostings with proper Content-Type headers
Key services
CDN delivery of source code files, Automatic file optimization with query parameters, Permanent caching for tagged/commit URLs, Development URLs with near real-time updates
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS, JavaScript, Cloudflare CDN, clipboard.js, carbonads.com
Performance
fast
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No visible sensitive data exposure
  • Use of Cloudflare CDN for DDoS protection

Analytics and tracking

Services
Cloudflare Insights
Tracking level
minimal
Privacy practices
poor

Advertising

Ad networks
carbonads.com
Tracking pixels
cloudflareinsights.com
Transparency
basic

Site quality

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

Key observations

  1. Website provides a specialized CDN service for source code files
  2. No WHOIS registration data available for domain raw.githack.com
  3. No privacy, cookie, or terms of service policies found
  4. No contact emails or phone numbers provided
  5. Uses Cloudflare CDN and third-party ad network carbonads.com
  6. No security.txt or vulnerability disclosure information present
  7. Website is accessible without WAF or blocking mechanisms
  8. Content is safe and targeted at developers
  9. Technical implementation is modern and performant
Technical notes

Notes

The website uses a modern and lightweight technology stack including HTML5, CSS, and JavaScript with libraries like clipboard.js for enhanced user interaction. Hosting is via Cloudflare CDN, ensuring fast content delivery and global availability. Performance is optimized with options for automatic file minification. The site is mobile responsive and accessible at a basic level. SEO is supported by meta tags and canonical links but could be improved with structured data. No CMS or complex frameworks are detected, indicating a custom-built static or serverless site. The technical implementation is clean and efficient, with minimal technical debt. Opportunities exist to enhance accessibility and SEO further and to implement additional security headers and compliance features.
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 githack.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 githack.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.