Skip to main content

Security report for eu4business.eu

EU4Business Facility · Government · N/a

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

Security score

69/100

Risk levelMedium

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

EU4Business is a European Union umbrella initiative aimed at supporting small and medium enterprises (SMEs) in the Eastern Partnership countries including Armenia, Azerbaijan, Georgia, Moldova, and Ukraine. The initiative focuses on improving access to finance, providing business development services, and enhancing the business enabling environment. The website serves as an information portal showcasing projects, results, success stories, and reports related to EU support for SMEs in the region. Technically, the website uses modern web technologies including htmx, Google reCAPTCHA v3, and Google Tag Manager for analytics and spam protection. However, a critical security weakness is the absence of a valid SSL certificate and HTTPS support, exposing users to potential risks. Privacy compliance is addressed with a cookie consent mechanism and a privacy policy page, though terms of service and security policies are not explicitly found. Overall, the website is professionally designed with consistent branding and clear navigation but requires urgent security improvements to protect user data and enhance trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
18/ 100 · Critical
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. GDPR outside view

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

    • Critical

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • 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

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

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

Keep watching eu4business.eu

This scan found 19 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
85
Security headers
50
Email security
85
DNS health
75
Network security
100
GDPR outside view
18
Average
69

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 EU4Business initiative operates as a non-profit government-related entity funded by the European Union, targeting SMEs in the Eastern Partnership region. Its business model revolves around providing financial access, advisory, and regulatory improvements to foster SME growth. The website reflects a medium-sized operation with a clear focus on transparency and outreach through newsletters and detailed reporting. The partnership ecosystem includes local country-specific websites, reinforcing regional presence. The initiative's market position is strong as a key EU-supported program in the region, with trust signals such as official EU logos and contact information. Growth indicators include numerous projects and significant budgets allocated for SME support in 2023.

Security posture

The website's security posture is currently weak due to the lack of a valid SSL certificate and absence of HTTPS, which is a critical vulnerability. No modern TLS protocols are enabled, and security headers are missing, increasing exposure to common web attacks. Email security is partially addressed with a valid SPF record, but DMARC is not configured. The use of Google reCAPTCHA v3 for form protection is a positive security practice. No incident response or security policy information is publicly available, indicating limited transparency in security governance. Immediate remediation is required to install valid SSL certificates, enable HTTPS, and implement security headers to protect user data and maintain compliance with EU regulations.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable modern TLS protocols (TLS 1.2 or 1.3) and disable all insecure protocols.
  3. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload options.
  4. Add DMARC DNS record to complement existing SPF and improve email security.
  5. Configure essential security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  6. Publish a clear security policy and incident response contact information to enhance transparency and trust.
Technical notes

Notes

The website is hosted by OVH SAS and uses a modern front-end stack including htmx for dynamic content loading, Google reCAPTCHA v3 for spam prevention, and Google Tag Manager for analytics. The DNS configuration is standard with multiple MX records and valid SPF. However, the SSL certificate is invalid or missing, and no TLS protocols are enabled, which is a major technical deficiency. The site has a slow load time (~6.5 seconds) and a moderate number of resources (55). Mobile optimization is good with responsive design and appropriate meta tags. SEO is supported by meta descriptions and Open Graph tags. There is no evidence of a CMS from the HTML content. Performance and security improvements are recommended to reduce technical debt and improve user experience.
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 eu4business.eu. 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 eu4business.eu.

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.