Skip to main content

Security report for baur.at

BAUR GmbH · Energy · Austria

High risk. 6 critical or high findings in GDPR outside view, SSL/TLS and 2 other checks.

Security score

39/100

Risk levelHigh

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

BAUR GmbH is a well-established Austrian company specializing in high-precision testing and measurement technology for electrical energy distribution systems, with a strong market position as a leader in cable fault location, cable testing, and insulating oil testing. The company operates internationally with multiple subsidiaries across Europe, the Americas, and Africa, offering products, services, and training to ensure reliable energy supply. Technically, the website is built on a modern JavaScript stack with RequireJS, jQuery, and various UI libraries, hosted on an Apache server. However, the primary domain baur.at lacks HTTPS, which is a significant security concern, although the main content is served securely on baur.eu. Security headers are partially implemented, but the absence of SSL/TLS and modern protocols reduces the security posture. Privacy compliance is well addressed with a comprehensive privacy policy and cookie consent mechanism. Overall, the website demonstrates good business credibility and technical maturity but requires urgent security improvements to protect user data and enhance trust.

Scanned

NIS2 and GDPR posture

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

6 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

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

    • 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. 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.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  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 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 baur.at

This scan found 17 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
0
Security headers
45
Email security
50
DNS health
85
Network security
20
GDPR outside view
33
Average
39

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

BAUR GmbH operates in the energy sector, focusing on maintenance and diagnostics of electrical energy distribution systems. Their business model is B2B, targeting utility companies and technical service providers. The company leverages its 80-year history and family-owned culture to innovate and maintain market leadership. Revenue streams likely include product sales, calibration services, training, and support. The company maintains a global presence with subsidiaries in key markets, enhancing its distribution and service capabilities. The website content and structure reflect a professional and consistent brand image, supporting their market position and customer engagement strategies.

Security posture

The current security posture is weak due to the lack of HTTPS on the baur.at domain, exposing users to potential interception and man-in-the-middle attacks. While some security headers like HSTS, X-Content-Type-Options, and X-XSS-Protection are present, the absence of TLS protocols and strong cipher suites is a critical vulnerability. No explicit incident response or vulnerability disclosure policies are found, indicating potential gaps in security governance. The cookie consent mechanism and privacy policy demonstrate awareness of privacy regulations, but overall security hygiene needs significant enhancement to meet industry best practices and compliance requirements.

Recommendations

  1. Implement and enforce HTTPS with valid SSL/TLS certificates on baur.at domain immediately.
  2. Upgrade server configuration to support TLS 1.2 and TLS 1.3 with strong cipher suites.
  3. Add comprehensive security headers including Content-Security-Policy and Referrer-Policy.
  4. Publish a clear security policy and incident response contact information on the website.
  5. Conduct regular security audits and vulnerability assessments to identify and remediate risks.

Contact details published on the site

Addresses
Legal name
BAUR GmbH
Technical notes

Notes

The website uses a robust and modern technology stack including RequireJS for module loading, jQuery and various UI libraries for interactivity, and Apache on Ubuntu for hosting. The CMS is a proprietary eboxx® Enterprise System by xoo design GmbH. Performance metrics indicate slow loading, possibly due to heavy resource usage or server configuration. The site is mobile optimized and accessible with ARIA landmarks and keyboard navigation aids. SEO is well addressed with meta tags, Open Graph, and structured data. However, the lack of HTTPS and outdated SSL configuration on the primary domain is a major technical risk. Modernization efforts should focus on security improvements and performance optimization.
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 baur.at. 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 baur.at.

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.