Skip to main content

Security report for git.nrw

RWTH Aachen University · Education · Germany

Medium risk. 9 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

56/100

Risk levelMedium

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

git.nrw is an educational platform operated under the auspices of RWTH Aachen University, providing a centralized GitLab instance and related services to universities in the NRW region of Germany. The platform supports version control, issue tracking, CI/CD, and offers educational courses and profiling quizzes to enhance learning experiences. The website is professionally designed with excellent content quality and clear navigation, targeting students and experts within the academic community. Technically, the site uses modern static site generation with Hugo, Tailwind CSS, and JavaScript modules, ensuring fast performance and mobile optimization. Security posture is solid with HTTPS enforced and privacy consent mechanisms implemented, though explicit security policies and vulnerability disclosure mechanisms are absent. WHOIS data confirms the domain's legitimacy and university affiliation, reinforcing trustworthiness. Overall, git.nrw represents a credible, well-maintained educational service with strong technical and privacy compliance foundations.

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

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

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

Keep watching git.nrw

This scan found 27 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
42
Security headers
20
Email security
70
DNS health
50
Network security
100
GDPR outside view
53
Average
56

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

The platform occupies a niche market position as a cooperative educational service for universities in NRW, leveraging shared resources to provide a centralized GitLab instance. Its business model is non-commercial, focusing on knowledge exchange and sustainable service provision. The target audience includes university students and academic experts, with offerings such as courses, profiling quizzes, and support services. The affiliation with RWTH Aachen University and cooperation among five universities strengthens its credibility and market presence. The platform's ecosystem includes related services like a dedicated GitLab instance and community chat, enhancing user engagement and collaboration. Growth potential lies in expanding course offerings and increasing user contributions.

Security posture

The website demonstrates a mature security posture with HTTPS usage and privacy consent management. No exposed sensitive data or vulnerable libraries were detected in the analyzed content. However, the absence of explicit security policies, incident response contacts, and vulnerability disclosure mechanisms represents a compliance gap. DNSSEC is not enabled, which could improve DNS security. The platform would benefit from publishing a security.txt file and implementing standard security headers to enhance protection. Overall, the security posture is good but could be improved with formalized policies and additional technical controls.

Recommendations

  1. Enable DNSSEC to enhance DNS security and prevent spoofing.
  2. Publish a dedicated security policy and incident response information on the website.
  3. Implement a security.txt file to facilitate vulnerability disclosures.
  4. Add standard security headers such as Content-Security-Policy and X-Frame-Options.
  5. Consider providing explicit contact information for security and data protection officers.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
RWTH Aachen University
Description
git.nrw offers universities in NRW free access to a central GitLab instance with features such as version control, issue tracking, and CI/CD. It is a cooperative project of five universities promoting knowledge exchange and sustainable service offerings for efficient project work.
Key services
Central GitLab instance, Version control, Issue tracking, CI/CD pipelines, Educational courses, Profiling quiz for course recommendations, Support and FAQs
Content quality
excellent
Branding
consistent

Technology

Stack
Hugo static site generator, Tailwind CSS, FontAwesome icons, JavaScript modules, Pagefind search, GitLab API integration
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced (implied by URL https://git.nrw/en/)
  • No exposed sensitive data in HTML
  • Consent management scripts for privacy
  • No vulnerable libraries detected in scripts

Analytics and tracking

Tracking level
minimal
Privacy practices
good

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a professionally designed educational platform for universities in NRW.
  2. Content is comprehensive and well-structured with clear navigation.
  3. No contact emails or phone numbers explicitly found on the homepage.
  4. Privacy and cookie policies are present with consent mechanisms.
  5. No explicit security or incident response policies published.
  6. No advertising or tracking services detected.
  7. No signs of suspicious or malicious content.
  8. WHOIS data confirms legitimacy and university affiliation.
Technical notes

Notes

The website is built using the Hugo static site generator, leveraging Tailwind CSS for styling and FontAwesome for icons. It integrates JavaScript modules for enhanced interactivity, including a custom search powered by Pagefind and consent management scripts. The site is mobile-optimized with responsive design and fast loading times. Hosting details are not explicit but likely managed by the university or associated registrar. The technical implementation is modern and well-structured, with no visible technical debt or performance bottlenecks. Opportunities exist to improve security headers and DNS configuration for enhanced resilience.
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.nrw. 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.nrw.

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.