Skip to main content

Security report for edhouse.eu

Edhouse · Technology · Czech Republic

Medium risk. 5 critical or high findings in Security headers, SSL/TLS and 1 other check.

Security score

58/100

Risk levelMedium

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

Edhouse is a well-established software house founded in 2006, specializing in custom software and hardware development services. The company serves both Czech and international markets with a medium-sized team of over 140 developers and specialists. Their business model focuses on delivering integrated technology solutions including software development, hardware development, and complex solutions tailored to client needs. The website reflects a professional and trustworthy brand with extensive case studies and client testimonials from reputable companies, positioning Edhouse as a reliable partner in the technology sector. Technically, the website is built using modern web technologies including jQuery and Google Tag Manager, managed via the Studio9 webManager CMS. It is well-optimized for performance, mobile responsiveness, and accessibility, with proper SEO metadata and structured navigation. The site uses HTTPS exclusively, and a cookie consent mechanism is implemented to comply with GDPR requirements. From a security perspective, the site demonstrates good practices such as HTTPS enforcement and cookie consent but lacks explicit security headers and published security policies or incident response contacts. The WHOIS data is privacy protected as per EURid policy, which is common and justified for this type of business. No vulnerabilities or suspicious content were detected. Overall, Edhouse presents a low-risk profile with a strong business credibility and a mature digital presence. Strategic recommendations include enhancing security posture by adding security headers and publishing a security policy, as well as providing direct contact information for incident response to improve transparency and trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
95/ 100 · Low
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. 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. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

  3. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • High

      High-Risk Service Exposed: RPC

      Port 135 (RPC) is publicly accessible - RPC - Windows RPC endpoint

      What to do: Consider restricting access to RPC or implementing strong authentication

      • 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

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

Keep watching edhouse.eu

This scan found 22 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
15
Email security
70
DNS health
75
Network security
20
GDPR outside view
95
Average
58

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

No leaked records found

Breach holds no records for edhouse.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

Edhouse operates in the technology sector, focusing on custom software and hardware development. Their competitive advantage lies in their integrated approach combining software and hardware competencies, supported by a skilled team and long-term client relationships with high-profile companies. Revenue streams likely come from project-based contracts and ongoing support services. The target customers are businesses requiring tailored IT solutions, including scale-ups and established high-tech firms. Growth indicators include a stable team size, multiple branches in the Czech Republic, and a portfolio of diverse case studies. The company maintains partnerships with industry leaders and invests in corporate social responsibility and technical education, enhancing its market reputation and ecosystem.

Security posture

The website exhibits a moderate to good security maturity level with HTTPS enabled and cookie consent implemented, indicating awareness of privacy regulations. However, the absence of key security headers such as Content-Security-Policy and X-Frame-Options reduces the overall security posture. No exposed sensitive data or vulnerable libraries were detected in the HTML content. There is no published security policy or incident response contact information, which limits transparency and readiness for security incidents. GDPR compliance is evident through the privacy and cookie policies. Overall, the security posture is adequate but could be improved by adopting additional best practices and publishing clear security governance documents.

Recommendations

  1. Implement and verify HTTP security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection against common web attacks.
  2. Publish a dedicated security policy page outlining security practices and incident response procedures to increase transparency and trust.
  3. Add a vulnerability disclosure policy or security.txt file to facilitate responsible reporting of security issues.
  4. Provide direct contact information for security incidents such as a security@ or abuse@ email address.
  5. Regularly audit and update third-party libraries and scripts to mitigate potential vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Edhouse
Description
Edhouse delivers world-class custom software and hardware solutions, tailored to meet your specific needs. Innovative technology development that helps you grow.
Key services
Software development, Hardware development, Complex solutions
Content quality
excellent
Branding
consistent

Technology

Stack
jQuery, Google Tag Manager, SVG, HTML5, CSS3, JavaScript
Frameworks
Studio9 webManager CMS
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent mechanism implemented
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Tag Manager
Tracking level
minimal
Privacy practices
good

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with rich content and multimedia
  2. Strong focus on software and hardware development services
  3. Multiple client testimonials and case studies enhance trust
  4. Cookie consent and GDPR compliance are implemented
  5. No direct contact emails or phone numbers visible on main pages, contact via form
  6. No explicit security policy or incident response info published
  7. WHOIS data is privacy protected as per EURid policy
  8. No signs of malicious or suspicious content
Technical notes

Notes

The website is built on a modern and maintainable technology stack using Studio9 webManager CMS, jQuery, and Google Tag Manager for analytics and marketing. The HTML and CSS are valid and optimized for performance, with multimedia content such as videos and SVG graphics enhancing user engagement. The site is mobile-optimized and accessible, with clear navigation and structured content. No technical debt or outdated technologies were detected. Hosting details are not explicitly available, but HTTPS and performance indicators suggest a reliable hosting environment. Opportunities exist to improve security headers and add more explicit technical SEO enhancements.
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 edhouse.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 edhouse.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.