Skip to main content

Security report for ktmgroup.com

KTM AG · Manufacturing · Austria

High risk. 7 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

46/100

Risk levelHigh

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

KTM AG is a well-established Austrian motorcycle manufacturer with a strong market presence and a focus on transparent communication with investors and the public. The website reflects a professional corporate image with clear navigation and relevant business content. Technically, the site is built on WordPress using the Divi theme and integrates modern marketing and analytics tools such as Google Tag Manager and OneTrust for cookie consent. However, the absence of a valid SSL certificate and HTTPS significantly undermines the site's security posture, exposing visitors to potential risks. No explicit security or incident response policies are published, which could be a concern for stakeholders. Overall, while the business credibility and content quality are good, the technical and security aspects require urgent improvement to meet modern standards.

Scanned

NIS2 and GDPR posture

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

7 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

  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 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 ktmgroup.com

This scan found 18 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
25
Email security
50
DNS health
85
Network security
100
GDPR outside view
18
Average
46

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

KTM AG operates in the manufacturing and transportation sectors, focusing on motorcycle production and investor relations. The company targets investors, motorcycle enthusiasts, and the general public. The website supports this with detailed investor relations content and links to related brand sites, indicating a broad partnership ecosystem. The business model centers on product manufacturing and transparent market communication. The site’s content and structure suggest a large enterprise with a mature digital presence, although some modernization in security is needed. The absence of direct contact emails or phone numbers on the homepage or footer may indicate a preference for controlled communication channels.

Security posture

The website currently lacks a valid SSL certificate and does not serve content over HTTPS, which is a critical security flaw. No modern TLS protocols are enabled, and important security headers like HSTS are missing. Cookies are set with secure and HttpOnly flags, and SameSite attributes are used, which is positive. The site uses Cloudflare as a CDN but does not leverage its security features fully. No security policy, incident response information, or vulnerability disclosure mechanisms are found, indicating limited transparency in security governance. The overall security maturity is low, and the site is vulnerable to interception and man-in-the-middle attacks. Immediate remediation is recommended to protect user data and maintain trust.

Recommendations

  1. Obtain and install a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable and enforce modern TLS protocols (TLS 1.2 and TLS 1.3) and disable legacy protocols.
  3. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  4. Publish a clear security policy and incident response plan accessible to users and stakeholders.
  5. Establish a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  6. Add visible and verified contact information including company emails and phone numbers for support and security reporting.
  7. Regularly audit and update third-party scripts and plugins to avoid vulnerabilities.
  8. Enhance accessibility features and optimize site performance for better user experience.

Contact details published on the site

Addresses
Legal name
KTM AG
Technical notes

Notes

The website is built on WordPress CMS with the Divi theme, leveraging jQuery and Yoast SEO for content management and optimization. It uses Cloudflare as a CDN and proxy but lacks HTTPS, which is a major technical deficiency. The site includes modern marketing tools such as Google Tag Manager and OneTrust for cookie consent management. Performance metrics are not provided but inferred as slow due to missing load time data and chunked transfer encoding. The site is mobile optimized with responsive design. Technical debt is indicated by the lack of SSL and outdated security configurations. Modernization opportunities include upgrading security protocols, improving performance, and enhancing accessibility compliance.
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 ktmgroup.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 ktmgroup.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.