Skip to main content

Security report for trusted-introducer.org

TF-CSIRT · Technology · N/a

Medium risk. 4 critical or high findings in Security headers and GDPR outside view.

Security score

75/100

Risk levelMedium

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

The Task Force CSIRT website serves as a hub for Computer Security Incident Response Teams and cybersecurity entities, focusing on fostering a trusted European cybersecurity community. It offers key services including community collaboration, training through TRANSITS, and the Trusted Introducer service which acts as a clearinghouse and directory for cybersecurity teams. The site targets cybersecurity professionals and organizations involved in incident response, positioning itself as a trusted backbone in the European cybersecurity landscape. Technically, the website uses standard web technologies including Bootstrap for responsive design and custom CSS/JS. Hosting is managed via Gandi.net. However, the site suffers from slow load times and lacks modern performance optimizations. Mobile optimization and accessibility are basic but functional. SEO is minimally addressed with basic meta tags and Open Graph images. From a security perspective, the site has significant weaknesses: it lacks a valid SSL certificate and does not serve content over HTTPS, exposing users to potential interception risks. No modern TLS protocols or security headers are enabled, and DNS security features like DNSSEC and CAA are absent. Email security is also weak with no DMARC record. These issues substantially reduce the site's security posture and trustworthiness. Overall, while the website provides valuable content and services to its niche audience, its technical and security shortcomings present risks that should be addressed promptly. Enhancing SSL/TLS deployment, implementing security headers, and improving performance would significantly improve the site's security and user trust.

Scanned

This is an earlier scan of trusted-introducer.org. View the latest report

NIS2 and GDPR posture

GDPR outside view
40/ 100 · High
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. 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';…

  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

    • 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 trusted-introducer.org

This scan found 16 issues across 5 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
100
Security headers
65
Email security
70
DNS health
75
Network security
100
GDPR outside view
40
Average
75

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

TF-CSIRT operates as an important entity within the cybersecurity incident response ecosystem, primarily serving European CSIRTs and related organizations. Its business model revolves around community building, training, and providing trusted infrastructure services. The organization leverages partnerships with entities like DFN-CERT and OpenCSIRT, as evidenced by linked domains. The absence of commercial advertising or tracking indicates a non-profit or community-driven approach. The website's clear service segmentation and professional branding support its market position as a trusted facilitator in cybersecurity collaboration and training. Growth opportunities may lie in expanding training offerings and enhancing digital presence. The lack of explicit business contact information and certifications suggests a focus on community trust rather than commercial transactions. The organization's reliance on Gandi.net for hosting and absence of advanced web analytics reflect a modest digital maturity level. Strategic partnerships and directory services form the backbone of its ecosystem, positioning TF-CSIRT as a central node in European cybersecurity incident response networks.

Security posture

The current security posture of the TF-CSIRT website is weak due to the absence of HTTPS and a valid SSL certificate, which is a critical vulnerability exposing users to man-in-the-middle attacks. The lack of modern TLS protocols and security headers further exacerbates the risk profile. DNS security is minimal with no DNSSEC or CAA records, increasing susceptibility to DNS spoofing or unauthorized certificate issuance. Email security is also lacking without DMARC, potentially allowing phishing or spoofing attacks. No incident response contact information or security policies are published on the site, limiting transparency and readiness communication. The absence of cookie consent mechanisms and minimal privacy compliance indicate gaps in regulatory adherence. While no active vulnerabilities or malware were detected, the foundational security deficiencies represent significant business risks, especially given the site's role in cybersecurity community trust. Immediate remediation should focus on deploying HTTPS with a valid certificate, enabling security headers, and improving DNS security configurations. Publishing clear security policies and incident response contacts would enhance trust and compliance.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Implement security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Configure DNSSEC and CAA records to strengthen DNS security and certificate issuance control.
  4. Add a DMARC record to improve email domain protection against spoofing.
  5. Develop and publish a comprehensive privacy and cookie policy with user consent mechanisms.
  6. Include clear contact information for incident response and data protection officers.
  7. Optimize website performance by reducing page size and improving load times.
  8. Enhance mobile responsiveness and accessibility to improve user experience.
  9. Integrate analytics with privacy compliance to better understand user engagement.
  10. Regularly audit and update security configurations to maintain compliance and trust.
Technical notes

Notes

The website is built using standard web technologies including Bootstrap for layout and navigation, SVG for graphics, and custom CSS and JavaScript files. Hosting is provided by Gandi.net, as indicated by the authoritative nameservers. The site suffers from slow load times (over 11 seconds) and a large page size (~1.3MB), which could be improved by optimizing images and resources. No modern CMS or frameworks were detected, suggesting a custom or static site approach. The absence of analytics or tracking scripts indicates minimal data collection. The DNS setup is standard but lacks advanced security features like DNSSEC and CAA. SSL/TLS is not configured properly, with no valid certificate and no TLS protocols enabled, which is a critical technical risk. Overall, the technical infrastructure is functional but outdated and lacking in security and performance optimizations. Modernizing the tech stack, improving hosting configurations, and implementing security best practices would reduce technical debt and enhance operational stability.
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/100Medium25 findingsView report
  2. 73/100Medium25 findingsView report
Reviews of this site

Share your experience with trusted-introducer.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 trusted-introducer.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.