Skip to main content

Security report for megger.com

Megger · Energy · N/a

Medium risk. 4 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

72/100

Risk levelMedium

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

Megger is a well-established company specializing in manufacturing electrical test equipment designed to improve efficiency and extend the life of electrical assets and cable networks across various voltage levels. The company holds a strong market position with a broad portfolio of products and solutions targeting professionals in the energy and transportation sectors. Their website reflects a mature digital presence with comprehensive multilingual support, professional design, and clear navigation. Technically, the site is built on Drupal 10 and integrates modern analytics and marketing tools, including Google Tag Manager and GetFeedback, with a robust cookie consent mechanism ensuring GDPR compliance. Security posture is good with HTTPS enforced and bot protection via reCAPTCHA, though explicit security headers are not detected and no public incident response contacts are provided. The absence of WHOIS data for the domain reduces trust slightly but is mitigated by strong branding and external references. Overall, the website is professional, secure, and compliant, serving a global audience effectively.

Scanned

NIS2 and GDPR posture

GDPR outside view
68/ 100 · Medium
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

4 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 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. GDPR outside view

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

    • 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

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

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching megger.com

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. 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
57
Security headers
55
Email security
75
DNS health
75
Network security
100
GDPR outside view
68
Average
72

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

Megger operates in the energy and transportation sectors, offering specialized electrical testing equipment and solutions. Their business model focuses on manufacturing and direct sales supported by a network of subsidiaries and partner brands. The company targets industrial clients such as electricians, OEMs, power generation, and renewables sectors. Their market presence is reinforced by comprehensive product offerings, technical support, and customer engagement through webinars and news updates. The multilingual website and regional site selectors indicate a global reach. Megger's ecosystem includes several subsidiary brands, enhancing their market coverage and technical capabilities. The company demonstrates a mature digital marketing strategy with integrated analytics and user feedback tools, supporting continuous improvement and customer satisfaction.

Security posture

Megger's website employs HTTPS and integrates Google reCAPTCHA to mitigate automated threats. Cookie consent management is implemented to comply with privacy regulations. However, the site lacks explicit security headers such as Content-Security-Policy and X-Frame-Options, which could enhance protection against common web attacks. No direct contact information for security incidents or data protection officers is published, which is a gap in transparency and incident response readiness. No vulnerabilities or exposed sensitive data were detected in the analyzed content. Overall, the security posture is solid but could be improved by adding security headers and publishing clear security policies and incident response contacts.

Recommendations

  1. Implement and enforce security headers like Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to strengthen web security.
  2. Publish a dedicated security policy page including incident response procedures and contact information to improve transparency and readiness.
  3. Enhance visibility of contact information for data protection officers or privacy contacts to support GDPR compliance.
  4. Regularly audit third-party scripts and libraries for vulnerabilities and update them promptly.
  5. Maintain and monitor WHOIS information to ensure domain registration transparency and trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Megger
Description
Megger makes electrical test equipment to help you install, improve efficiency and extend the life of electrical assets and cable networks at high, medium and low voltage
Key services
Electrical test equipment manufacturing, Partial discharge testing and monitoring, Asset performance management, Cable fault location and diagnostics, Technical support and customer performance support
Content quality
excellent
Branding
consistent

Technology

Stack
PHP SDK 1.5.14, Drupal 10 CMS, Google Tag Manager, Google Analytics, CookiesJSR, GetFeedback, reCAPTCHA
Frameworks
Drupal
Performance
moderate
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent mechanism implemented
  • Use of reCAPTCHA for bot protection
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Google Tag Manager
Marketing tools
GetFeedback
Transparency
good

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 multiple language support
  2. Strong branding and consistent design
  3. Comprehensive cookie and privacy policies with consent management
  4. Use of modern analytics and marketing tools with user consent
  5. No direct contact emails or phone numbers found on main page
  6. No explicit security policy or incident response contacts published
  7. WHOIS data unavailable, which is unusual for a commercial domain
  8. No signs of adult or questionable content
  9. No WAF or blocking detected
Technical notes

Notes

The website is built on Drupal 10, leveraging PHP SDK and modern JavaScript libraries. It uses Google Tag Manager and Google Analytics for performance and marketing insights, alongside GetFeedback for user surveys. The site is mobile-optimized with responsive design and accessibility features. Performance is moderate with asynchronous loading of scripts and preconnect hints for fonts. Cookie consent is managed via CookiesJSR, ensuring compliance with privacy laws. No hosting provider details were identified from the content. The technical stack is modern and well-maintained, supporting a professional user experience and effective data collection for business intelligence.
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

Earlier scans of this domain

  1. 47/100High25 findingsView report
Reviews of this site

Share your experience with megger.com. 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 megger.com.

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.