Skip to main content

Security report for microtronics.at

Microtronics Engineering GmbH · Energy · Austria

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

Security score

33/100

Risk levelHigh

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

Microtronics Engineering GmbH is a medium-sized Austrian company specializing in technology solutions for environmental technology and energy management. Their offerings include advanced data loggers, sensors, and an IoT platform designed for reliable data transmission even in harsh environments. The company has a strong international presence with partners in 80 countries and a focus on B2B markets in energy and environmental sectors. Technically, the website is built on WordPress with WooCommerce and Elementor, integrating marketing and analytics tools such as HubSpot and Google Analytics. However, the security posture is weak due to the absence of a valid SSL certificate and lack of modern TLS protocols, which poses risks to data confidentiality and user trust. Privacy compliance is well addressed with comprehensive policies and consent mechanisms. Overall, the website is professional and trustworthy but requires urgent improvements in SSL/TLS security to protect users and enhance credibility.

Scanned

NIS2 and GDPR posture

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

8 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

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

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

This scan found 25 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. 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
0
Security headers
25
Email security
65
DNS health
85
Network security
20
GDPR outside view
0
Average
33

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

Microtronics holds a niche market position as a provider of IoT and data transmission solutions for environmental and energy applications. Their business model focuses on hardware sales combined with platform services and partner collaborations. The company targets professionals and enterprises requiring robust monitoring solutions in challenging environments. Their marketing strategy includes active social media engagement, newsletters, and events, supporting customer education and lead generation. The domain age and WHOIS data align with the company’s founding year, reinforcing legitimacy. The partner ecosystem and multilingual website further support international growth and customer reach.

Security posture

The current security maturity level is low due to the lack of HTTPS enabled by a valid SSL certificate and absence of modern TLS protocols. While some security headers like HSTS are present, they are not fully enabled or configured. No public incident response or vulnerability disclosure policies were found, which may limit transparency and responsiveness to security issues. The use of third-party marketing and analytics tools is compliant with privacy regulations, but the insecure transport layer undermines overall security. Immediate remediation of SSL/TLS configuration is critical to mitigate risks of data interception and to comply with best practices.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable TLS 1.2 or TLS 1.3 protocols and disable insecure legacy protocols.
  3. Configure HSTS header with includeSubDomains and preload directives for enhanced security.
  4. Implement OCSP stapling and session resumption to improve SSL performance and security.
  5. Publish a clear security policy and vulnerability disclosure program to build trust and readiness.

Contact details published on the site

Addresses
Legal name
Microtronics Engineering GmbH
Technical notes

Notes

The website uses a modern CMS (WordPress) with popular plugins such as WooCommerce for e-commerce and Elementor for page building, indicating a mature technical stack. SEO is enhanced by Yoast SEO plugin and structured data (JSON-LD) is implemented for rich search results. Performance metrics are not provided but the site appears moderately optimized with lazy loading and responsive design. Hosting appears to be with Ionos, inferred from DNS and SPF records. The site integrates multiple marketing and analytics tools, including HubSpot and Google Tag Manager, with cookie consent managed by Borlabs Cookie plugin. Technical debt is low but the lack of SSL is a significant risk factor that should be addressed promptly.
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 microtronics.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 microtronics.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.