Skip to main content

Security report for bmw-m.com

BMW M GmbH · Transportation · Germany

Partial score · DNS & email only

75/100

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

BMW M GmbH operates the official BMW M website, showcasing its high-performance vehicles, motorsport heritage, and driving experiences. The company holds a strong market position in the premium automotive segment, targeting enthusiasts and customers seeking performance and motorsport engagement. The website reflects a mature digital presence with rich multimedia content, clear navigation, and comprehensive legal and privacy documentation. Technically, the site uses modern web technologies, including Adobe Experience Manager CMS, Akamai CDN, and performance monitoring tools, delivering a good user experience across devices. Security posture is solid with HTTPS, SPF, DMARC, and no critical vulnerabilities detected, though improvements like HSTS and additional security headers are recommended. Privacy compliance is well addressed with clear policies and consent mechanisms. Overall, the site demonstrates high professionalism and trustworthiness.

Scanned

3 of 7 checks could not complete. The site may be unreachable or blocking automated scans, so the results below cover only what could be checked. Try a rescan later.

NIS2 and GDPR posture

NIS2 outside view
Not assessed
GDPR outside view
Not assessed

Both readouts depend on the site's pages, which could not be loaded in this scan.

Priority findings

No critical or high findings. These medium findings are worth fixing next.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Medium

      No DKIM record found

      DKIM adds cryptographic signatures to emails

      What to do: Configure DKIM with your email provider

    • Medium

      No MTA-STS Policy

      MTA-STS enforces TLS for email delivery

      What to do: Implement MTA-STS to prevent downgrade attacks

  2. DNS health

    DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.

    • Medium

      DNSSEC Not Enabled

      DNSSEC is not configured for this domain

      What to do: Enable DNSSEC to prevent DNS spoofing attacks

      • CAPEC-142
      • RFC 4033
      • RFC 4035

Keep watching bmw-m.com

This scan found 9 issues across 4 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
92
Email security
70
DNS health
85
Network security
100
Average
87
After the cap
75

Not counted

  • Security headers: did not complete in this scan.
  • GDPR outside view: did not complete in this scan.
  • 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

BMW M GmbH benefits from its parent company BMW Group's global brand and resources. The business model focuses on premium automotive manufacturing with a niche in high-performance and motorsport vehicles. Revenue streams include vehicle sales, driving experiences, performance parts, and community engagement. The target audience includes automotive enthusiasts and motorsport fans worldwide. The company maintains a strong partnership ecosystem, including official community platforms and digital engagement tools like chatbots. Growth indicators include electrification initiatives and expanding digital services. Strategic observations highlight the importance of maintaining brand consistency and leveraging digital channels for customer engagement.

Security posture

The website exhibits a mature security posture with mandatory HTTPS enabled using TLS 1.3 and 1.2 protocols. DNS records include SPF and DMARC policies to protect email integrity. No subdomain takeover vulnerabilities or known SSL/TLS vulnerabilities (Heartbleed, FREAK, Logjam) were found. However, the absence of HSTS and OCSP stapling reduces the overall security hardening. No explicit security policies or incident response contacts are published on the site, indicating an area for improvement. The site uses third-party scripts and CDNs, which should be regularly audited to prevent supply chain risks. Overall, the security posture is good but can be enhanced with additional HTTP security headers and transparency compliance.

Recommendations

  1. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload to enforce HTTPS.
  2. Implement OCSP stapling to improve SSL certificate revocation checks and reduce latency.
  3. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web attacks.
  4. Publish a dedicated security policy and incident response contact information to improve transparency and trust.
  5. Regularly audit and update third-party scripts and libraries to minimize vulnerabilities and supply chain risks.
Technical notes

Notes

The website is built on Adobe Experience Manager CMS, leveraging Akamai CDN for content delivery and performance optimization. It uses modern web standards including HTML5, CSS, and JavaScript with video streaming capabilities. Service workers are registered for offline support and improved performance. Performance monitoring is implemented via Akamai Boomerang. The site is mobile optimized with responsive images and accessible navigation. Load time is moderate (~6 seconds) with 40 resources and a page size of ~425 KB, indicating room for optimization. SEO is well addressed with meta tags, Open Graph data, and hreflang attributes for multilingual support. Technical risks include lack of HSTS and OCSP stapling, and missing certificate transparency 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 bmw-m.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 bmw-m.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.