Skip to main content

Security report for eaia.eu

MTÜ Eesti Keskkonnamõju Hindajate Ühing · Non-profit · Estonia

High risk. 11 critical or high findings in GDPR outside view, Network security and 2 other checks.

Security score

42/100

Risk levelHigh

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

MTÜ Eesti Keskkonnamõju Hindajate Ühing (KeMÜ) is a small Estonian non-profit organization founded in 2012 that unites professionals and interested parties in the field of environmental impact assessment. The website serves as an information hub and membership portal, offering news, organizational details, and contact avenues primarily through structured navigation and login forms. The organization targets environmental impact assessors and stakeholders within Estonia, positioning itself as a niche entity in the environmental non-profit sector. Technically, the website is built on Joomla CMS with Yootheme templates, leveraging common web technologies such as jQuery and Widgetkit. It integrates Google Analytics and Facebook Pixel for user tracking and marketing insights. The site is mobile-optimized and features a moderate performance profile. Security measures include HTTPS enforcement and CSRF tokens in forms, but it lacks advanced security headers and explicit privacy or cookie policies. From a security perspective, the site demonstrates a good baseline posture with encrypted communications and secure login forms. However, the absence of privacy and cookie policies, as well as missing security headers, represents compliance and security gaps. No critical vulnerabilities or blocking mechanisms were detected, indicating a stable and accessible platform. Overall, the website is professionally designed and functional for its purpose but would benefit from enhanced privacy compliance and security hardening to improve trust and regulatory adherence.

Scanned

NIS2 and GDPR posture

GDPR outside view
10/ 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

11 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

  2. 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: MySQL

      Port 3306 (MySQL) is publicly accessible - MySQL - Database server

      What to do: Immediately restrict access to MySQL 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

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

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

Keep watching eaia.eu

This scan found 28 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
72
Security headers
20
Email security
70
DNS health
80
Network security
0
GDPR outside view
10
Average
42

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

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 eaia.eu, from OffSeq Breach.

No leaked records found

Breach holds no records for eaia.eu right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

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

Business context

Business profile

KeMÜ operates as a focused non-profit entity within Estonia's environmental sector, providing a platform for environmental impact assessors and related professionals. Its business model revolves around membership engagement and information dissemination rather than commercial revenue streams. The organization maintains a modest online presence with social media integration on LinkedIn and Facebook, supporting community outreach. The website content and structure reflect a stable but small-scale operation with limited digital marketing or e-commerce capabilities. Growth indicators are subtle, with periodic news updates and organizational announcements. The partnership ecosystem is not explicitly detailed, and no related or subsidiary domains were identified, suggesting a standalone operation.

Security posture

The website exhibits a foundational security posture with HTTPS encryption and CSRF protection on forms, which are essential for safeguarding user credentials and data submissions. However, the lack of security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options reduces defense-in-depth effectiveness. The absence of published incident response or vulnerability disclosure policies limits transparency and preparedness for security events. Tracking technologies are present without visible cookie consent mechanisms, posing potential GDPR compliance risks. No exposed sensitive data or known vulnerabilities were identified, indicating a low immediate risk but room for improvement in compliance and security maturity.

Recommendations

  1. Publish comprehensive privacy and cookie policies prominently on the website to enhance GDPR compliance.
  2. Implement a cookie consent mechanism to inform users and obtain consent for tracking technologies.
  3. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to strengthen security posture.
  4. Develop and publish incident response and vulnerability disclosure policies to improve transparency and readiness.
  5. Enhance accessibility features to improve usability for all users and comply with accessibility standards.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
MTÜ Eesti Keskkonnamõju Hindajate Ühing
Description
MTÜ Eesti Keskkonnamõju Hindajate Ühing (KeMÜ) on loodud 2012 aastal ning ühendab endas keskkonnamõju hindamisega tegelevaid ning ka sellest valdkonnast huvitatud isikuid.
Key services
Membership services, Information dissemination, Organizing meetings and general assemblies
Content quality
good
Branding
consistent

Technology

Stack
Joomla!, Yootheme, jQuery, Widgetkit, Google Analytics, Facebook Pixel
Frameworks
Yootheme UIkit
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • CSRF token present in forms
  • Secure login form with password field

Analytics and tracking

Services
Google Analytics, Facebook Pixel
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
Facebook Pixel
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges
  2. No explicit privacy, cookie, or terms of service policies found
  3. Contact information is primarily via contact pages and login form; no explicit emails or phone numbers visible
  4. Uses Joomla CMS with Yootheme template and standard web technologies
  5. Includes social media links to LinkedIn and Facebook
  6. Security posture is good with HTTPS and CSRF tokens but lacks advanced security headers
  7. Tracking via Google Analytics and Facebook Pixel present without visible cookie consent mechanism
  8. Content is relevant and professionally presented for a small non-profit organization
Technical notes

Notes

The website is built on a mature CMS platform (Joomla) with Yootheme UIkit framework, providing a responsive and structured user interface. It uses standard JavaScript libraries including jQuery and Widgetkit for UI components. Analytics and marketing scripts from Google and Facebook are integrated for user behavior tracking. The site demonstrates moderate performance and good mobile optimization but lacks advanced SEO and accessibility features. No critical technical debt or deprecated technologies were detected, indicating a well-maintained infrastructure suitable for a small non-profit organization.
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 eaia.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 eaia.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.