Security - https://mercedes-benz.com BeaverCheck Audit

D

Content Security Policy

Action

4 of 10 CSP checks passed

FIX

4 of 10 CSP checks passed

Raw CSP policy

Got: default-src 'self' https: *.mercedes-benz.com *.mercedes-benz.de *.corpinter.net *.usercentrics.eu *.googletagmanager.com *.krxd.net *.day.com *.anythingabout.net *.system360gmbh.de *.mercedes-benz-classic.com *.speedcurve.com alltime-stars.com cdn.jsdelivr.net *.mb-lounge.com *.eventbase.com narando.com *.narando.com *.googleapis.com maxcdn.bootstrapcdn.com cdn.plyr.io *.youtube.com *.youtube-nocookie.com *.ytimg.com *.google-analytics.com *.google.com *.google.de *.doubleclick.net shop.nostalgic.de *.gstatic.com cdn.ampproject.org amp.azure.net *.windows.net cmsdata.net booking-widget.quandoo.de api.corpinter.net *.facebook.net *.facebook.com *.atdmt.com *.adobe.com www.kinoheld.de mb-prototypes.swhost.in *.go-mpulse.net *.akstat.io my.matterport.com snap.licdn.com *.ads.linkedin.com p.adsymptotic.com *.linkedin.oribi.io sjs.bizographics.com embed.gomexlive.com playout.3qsdn.com pretix.eu data: blob: 'unsafe-inline' 'unsafe-eval'; frame-ancestors 'self' *.mercedes-benz.com;

default-src directive is set

Got: default-src 'self' https: *.mercedes-benz.com *.mercedes-benz.de *.corpinter.net *.usercentrics.eu *.googletagmanager.com *.krxd.net *.day.com *.anythingabout.net *.system360gmbh.de *.mercedes-benz-classic.com *.speedcurve.com alltime-stars.com cdn.jsdelivr.net *.mb-lounge.com *.eventbase.com narando.com *.narando.com *.googleapis.com maxcdn.bootstrapcdn.com cdn.plyr.io *.youtube.com *.youtube-nocookie.com *.ytimg.com *.google-analytics.com *.google.com *.google.de *.doubleclick.net shop.nostalgic.de *.gstatic.com cdn.ampproject.org amp.azure.net *.windows.net cmsdata.net booking-widget.quandoo.de api.corpinter.net *.facebook.net *.facebook.com *.atdmt.com *.adobe.com www.kinoheld.de mb-prototypes.swhost.in *.go-mpulse.net *.akstat.io my.matterport.com snap.licdn.com *.ads.linkedin.com p.adsymptotic.com *.linkedin.oribi.io sjs.bizographics.com embed.gomexlive.com playout.3qsdn.com pretix.eu data: blob: 'unsafe-inline' 'unsafe-eval'

'unsafe-inline' found in script source

'unsafe-inline' allows inline <script> tags, defeating CSP against XSS. Remove it and use nonces or hashes instead.

Got: script-src 'self' https: *.mercedes-benz.com *.mercedes-benz.de *.corpinter.net *.usercentrics.eu *.googletagmanager.com *.krxd.net *.day.com *.anythingabout.net *.system360gmbh.de *.mercedes-benz-classic.com *.speedcurve.com alltime-stars.com cdn.jsdelivr.net *.mb-lounge.com *.eventbase.com narando.com *.narando.com *.googleapis.com maxcdn.bootstrapcdn.com cdn.plyr.io *.youtube.com *.youtube-nocookie.com *.ytimg.com *.google-analytics.com *.google.com *.google.de *.doubleclick.net shop.nostalgic.de *.gstatic.com cdn.ampproject.org amp.azure.net *.windows.net cmsdata.net booking-widget.quandoo.de api.corpinter.net *.facebook.net *.facebook.com *.atdmt.com *.adobe.com www.kinoheld.de mb-prototypes.swhost.in *.go-mpulse.net *.akstat.io my.matterport.com snap.licdn.com *.ads.linkedin.com p.adsymptotic.com *.linkedin.oribi.io sjs.bizographics.com embed.gomexlive.com playout.3qsdn.com pretix.eu data: blob: 'unsafe-inline' 'unsafe-eval'

'unsafe-eval' found in script source

'unsafe-eval' allows eval() and similar functions, enabling code injection. Remove it.

Got: script-src 'self' https: *.mercedes-benz.com *.mercedes-benz.de *.corpinter.net *.usercentrics.eu *.googletagmanager.com *.krxd.net *.day.com *.anythingabout.net *.system360gmbh.de *.mercedes-benz-classic.com *.speedcurve.com alltime-stars.com cdn.jsdelivr.net *.mb-lounge.com *.eventbase.com narando.com *.narando.com *.googleapis.com maxcdn.bootstrapcdn.com cdn.plyr.io *.youtube.com *.youtube-nocookie.com *.ytimg.com *.google-analytics.com *.google.com *.google.de *.doubleclick.net shop.nostalgic.de *.gstatic.com cdn.ampproject.org amp.azure.net *.windows.net cmsdata.net booking-widget.quandoo.de api.corpinter.net *.facebook.net *.facebook.com *.atdmt.com *.adobe.com www.kinoheld.de mb-prototypes.swhost.in *.go-mpulse.net *.akstat.io my.matterport.com snap.licdn.com *.ads.linkedin.com p.adsymptotic.com *.linkedin.oribi.io sjs.bizographics.com embed.gomexlive.com playout.3qsdn.com pretix.eu data: blob: 'unsafe-inline' 'unsafe-eval'

No wildcard in script source

object-src falls back to default-src

base-uri directive is missing

Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.

Expected: base-uri 'self'

frame-ancestors directive is set

Got: frame-ancestors 'self' *.mercedes-benz.com

form-action directive is missing

form-action restricts where forms can submit data, preventing form hijacking.

Expected: form-action 'self'

upgrade-insecure-requests is not set

This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.

Expected: upgrade-insecure-requests

'unsafe-inline' allows inline <script> tags, defeating CSP against XSS. Remove it and use nonces or hashes instead.

Why this matters

Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.

Learn more ▾

unsafe-inline allows inline <script> tags; unsafe-eval allows eval() and similar. Both are necessary for some legacy code but explicitly dangerous. Migrate to nonces (per-page random tokens) or hashes (per-script SHA-256) instead.

Source: OWASP CSP / MDN

'unsafe-eval' allows eval() and similar functions, enabling code injection. Remove it.

Why this matters

Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.

Learn more ▾

unsafe-inline allows inline <script> tags; unsafe-eval allows eval() and similar. Both are necessary for some legacy code but explicitly dangerous. Migrate to nonces (per-page random tokens) or hashes (per-script SHA-256) instead.

Source: OWASP CSP / MDN

Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.

Expected: base-uri 'self'

Why this matters

Missing base-uri in CSP leaves a base-tag injection attack path open even on otherwise strict policies.

Learn more ▾

A common omission: developers add CSP for script-src and frame-ancestors but forget base-uri. The result is a CSP that looks strict but lets an attacker rewrite every URL on the page via <base href>. Add `base-uri 'self'` to close the gap.

Source: MDN CSP

form-action restricts where forms can submit data, preventing form hijacking.

Expected: form-action 'self'

Why this matters

Security gaps expose your site and users to attacks, eroding trust.

This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.

Expected: upgrade-insecure-requests

Why this matters

Without upgrade-insecure-requests, any HTTP subresource link survives as a mixed-content warning instead of auto-upgrading.

Learn more ▾

Adding `upgrade-insecure-requests` to your CSP turns every http:// subresource fetch into https:// at the browser layer. One-line defense against accidental mixed content from legacy links or third-party widgets.

Source: MDN CSP

Parsed Policy

default-src 'self'https:*.mercedes-benz.com*.mercedes-benz.de*.corpinter.net*.usercentrics.eu*.googletagmanager.com*.krxd.net*.day.com*.anythingabout.net*.system360gmbh.de*.mercedes-benz-classic.com*.speedcurve.comalltime-stars.comcdn.jsdelivr.net*.mb-lounge.com*.eventbase.comnarando.com*.narando.com*.googleapis.commaxcdn.bootstrapcdn.comcdn.plyr.io*.youtube.com*.youtube-nocookie.com*.ytimg.com*.google-analytics.com*.google.com*.google.de*.doubleclick.netshop.nostalgic.de*.gstatic.comcdn.ampproject.orgamp.azure.net*.windows.netcmsdata.netbooking-widget.quandoo.deapi.corpinter.net*.facebook.net*.facebook.com*.atdmt.com*.adobe.comwww.kinoheld.demb-prototypes.swhost.in*.go-mpulse.net*.akstat.iomy.matterport.comsnap.licdn.com*.ads.linkedin.comp.adsymptotic.com*.linkedin.oribi.iosjs.bizographics.comembed.gomexlive.complayout.3qsdn.compretix.eudata:blob:'unsafe-inline''unsafe-eval'

frame-ancestors 'self'*.mercedes-benz.com

F

Bot Challenge Detection

Action

Scan was blocked by Akamai Bot Manager -- the rest of this report does NOT reflect the real site

FIX

Scan was blocked by Akamai Bot Manager -- the rest of this report does NOT reflect the real site

Scan returned a Akamai Bot Manager bot-protection interstitial, not the actual page

The HTML captured by the scanner is a `Akamai Bot Manager` challenge / block page. The scanner's user-agent or IP was flagged as bot traffic and the real site content was never returned. Every other section in this report (security headers, accessibility, content, SEO, performance) was computed against the few KB of interstitial HTML rather than your actual page -- those findings are NOT meaningful for this URL. Detection signal: 'Access Denied' + Reference # + HTTP block + small body -- Akamai Bot Manager pattern Resolution paths: (1) allow-list BeaverCheck's worker IPs at the bot-protection layer, (2) configure a relaxed challenge for known scanner user-agents, or (3) accept that the public site is unscannable from third-party tools. Note that Cloudflare's "Bot Fight Mode" and "Super Bot Fight Mode" both block the scanner by default.

Got: HTTP 403, title: Access Denied

F

Permissions-Policy Granularity

Action

0% high-risk feature coverage (0/10)

FIX

0% high-risk feature coverage (0/10)

Permissions-Policy covers 0/10 high-risk features (0%)

The Permissions-Policy header explicitly declares policies for 0/10 high-risk features. Covered: Not declared (default-allow): camera, microphone, geolocation, payment, usb, serial, midi, accelerometer, gyroscope, magnetometer The non-declared features fall back to their spec-default policy (usually `self`), which means an XSS-injected or compromised iframe could request them. For features the page genuinely doesn't use, declare `feature=()` to fully close them.

Got: 0% (0/10)

C

Security Headers

Action

5 of 10 headers properly configured

REVIEW

5 of 10 headers properly configured

HSTS is missing includeSubDomains

Without includeSubDomains, subdomains can still be accessed over HTTP.

Got: max-age=31536000 Expected: max-age=31536000; includeSubDomains

X-Content-Type-Options header is missing

This header prevents MIME-type sniffing, which can lead to XSS attacks. Set it to 'nosniff'.

Expected: nosniff

X-Frame-Options is properly configured

Got: SAMEORIGIN

Referrer-Policy header is missing

Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.

Expected: strict-origin-when-cross-origin

Permissions-Policy is set

Got: fullscreen=*

Content-Security-Policy is present

Got: default-src 'self' https: *.mercedes-benz.com *.mercedes-benz.de *.corpinter.net…

Cross-Origin-Opener-Policy header is missing

COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.

Expected: same-origin

Cross-Origin-Embedder-Policy header is missing

COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.

Expected: require-corp

X-Powered-By header is not present

Server header is not present

Domain is not in the Chrome HSTS preload list (status: unknown)

Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload).

Got: unknown

Without includeSubDomains, subdomains can still be accessed over HTTP.

Expected: max-age=31536000; includeSubDomains

Why this matters

Without includeSubDomains, a forgotten dev subdomain over HTTP can set malicious cookies that ride to the apex.

Learn more ▾

HSTS without includeSubDomains protects only the exact domain. Cookies set on a non-HSTS subdomain can ride to the apex via cookie-scope attacks. The fix is one directive append. Verify all subdomains support HTTPS first — adding includeSubDomains to a domain with HTTP-only subdomains breaks them.

Source: RFC 6797

This header prevents MIME-type sniffing, which can lead to XSS attacks. Set it to 'nosniff'.

Expected: nosniff

Why this matters

MIME sniffing lets browsers run uploaded files as JavaScript, turning a file upload into an XSS.

Learn more ▾

Setting X-Content-Type-Options: nosniff tells browsers to trust your declared Content-Type instead of guessing. Without it, an attacker who uploads a polyglot file can sometimes get it executed as a script. One header, no downside.

Source: OWASP / MDN

Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.

Expected: strict-origin-when-cross-origin

Why this matters

Default browser behavior leaks full URLs (including query params and tokens) to every third-party resource — set a strict policy.

Learn more ▾

Without a Referrer-Policy header, browsers send the full referring URL with images, scripts, and fonts loaded from third-party origins. URLs containing tokens, user IDs, or session params end up in third-party logs. Set `Referrer-Policy: strict-origin-when-cross-origin` (or stricter) to limit leakage.

Source: MDN / W3C

COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.

Expected: same-origin

Why this matters

COOP isolates your top-level browsing context from cross-origin windows — without it, popup-based side-channel attacks remain possible.

Learn more ▾

Cross-Origin-Opener-Policy: same-origin prevents cross-origin pages from sharing a browsing-context group with yours. This blocks cross-window references that enable Spectre-style timing attacks and tab-nabbing. Required if you want to enable SharedArrayBuffer.

Source: MDN / web.dev

COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.

Expected: require-corp

Why this matters

COEP enforces that all embedded resources opt-in to cross-origin embedding — required for cross-origin isolation features.

Learn more ▾

Cross-Origin-Embedder-Policy: require-corp ensures every embedded resource (script, iframe, image) explicitly allows being loaded cross-origin. Combined with COOP, this enables the cross-origin-isolated context that unlocks SharedArrayBuffer, high-resolution timers, and other powerful APIs.

Source: MDN / web.dev

Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload).

Why this matters

Not in the Chrome preload list — first-time visitors over plain HTTP can be downgraded by a network attacker before HSTS kicks in.

Learn more ▾

The HSTS header only protects users who have already visited the site (TOFU window). Adding your domain to the Chrome preload list closes that gap so HSTS is enforced from the very first connection. Requires a preload-ready header (max-age=31536000+, includeSubDomains, preload) then submission at hstspreload.org. Inclusion ships in the next Chrome release after acceptance.

Source: hstspreload.org

B

WAF / Bot Protection

No WAF detected via response headers

REVIEW

No WAF detected via response headers

No WAF detected

Response headers don't match any known WAF or bot-management product. Sites exposed to abuse (login, signup, payment) typically benefit from a WAF such as Cloudflare, Akamai, AWS WAF, or Imperva.

C

security.txt

Action

No security.txt file found

REVIEW

No security.txt file found

security.txt (RFC 9116) provides a standardized way for security researchers to report vulnerabilities. Create one at /.well-known/security.txt with at least a Contact field.

Expected: /.well-known/security.txt

security.txt

No security.txt found at /.well-known/security.txt

B

Trusted Types (XSS Sink Hardening)

Trusted Types not enabled

REVIEW

Trusted Types not enabled

Trusted Types (CSP3) is a Chrome 83+ defense that requires DOM-XSS sinks (innerHTML, document.write, eval, ...) to receive a typed-and-sanitized value rather than a raw string. Adding `Content-Security-Policy: require-trusted-types-for 'script'; trusted-types default` neutralizes most DOM-XSS even when a payload reaches a sink. Adoption is currently ~0.1% of pages so this is informational; a roll-out usually starts in report-only mode.

B

Referrer-Policy Strictness

Referrer-Policy header not set -- browser default applies (modern: strict-origin-when-cross-origin; legacy browsers: no-referrer-when-downgrade)

REVIEW

Referrer-Policy header not set -- browser default applies (modern: strict-origin-when-cross-origin; legacy browsers: no-referrer-when-downgrade)

Referrer-Policy header not set -- browser default applies

Without an explicit `Referrer-Policy` header, the browser falls back to its default policy. Modern browsers (Chrome 85+, Firefox 87+, Safari 15+) default to `strict-origin-when-cross-origin`, which is privacy-safe. Legacy browsers default to the leaky `no-referrer-when-downgrade`, which sends the full URL (including path + query) on cross-origin HTTPS-to-HTTPS requests. Set an explicit header to ensure consistent behavior: ``` Referrer-Policy: strict-origin-when-cross-origin ``` This matches the modern browser default and is privacy-safe without breaking referrer-based same-origin analytics.

Got: header absent

B

Subdomain Inventory Exposure

1 risky subdomain name(s) in certificate SANs

REVIEW

1 risky subdomain name(s) in certificate SANs

1 risky subdomain name(s) advertised in certificate SANs

These names are publicly visible via Certificate Transparency logs (crt.sh, censys.io) -- any attacker can enumerate them in seconds. Operators are often unaware that internal/staging/admin endpoints are inadvertently advertised this way. Mitigation: use a wildcard cert that doesn't enumerate, issue per-environment certs without non-prod SANs on the prod cert, or move internal services to private DNS off the public cert.

Got: g-class-test.mercedes-benz.com

B

Email Security

DMARC: reject, SPF: ~all, DKIM

REVIEW

DMARC: reject, SPF: ~all, DKIM

DMARC policy is reject — strongest protection

SPF ends in ~all (soft fail)

Soft fail tells receivers to accept-but-mark unauthorized mail. Migrate to -all once you've confirmed all legitimate senders are listed (DMARC aggregate reports help verify).

DKIM configured (selectors: k2, s2, s1, pm)

MTA-STS not configured

MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.

TLS-RPT not configured

TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.

BIMI not configured

BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

DMARC

Policy reject — strongest protection Record v=DMARC1; p=reject; rua=mailto:weacxe0d@ag.eu.dmarcadvisor.com;

Soft fail tells receivers to accept-but-mark unauthorized mail. Migrate to -all once you've confirmed all legitimate senders are listed (DMARC aggregate reports help verify).

Why this matters

Informational: a labeled value pair from the audit.

MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.

Why this matters

Without MTA-STS, inbound mail can be silently downgraded to plain SMTP by a network attacker.

Learn more ▾

MTA-STS (RFC 8461) tells sending mail servers to use TLS and to refuse delivery if TLS fails. Requires both a TXT record at _mta-sts.<domain> AND a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt. Without it, an active attacker on the network path can strip STARTTLS and read the email in plaintext.

Source: RFC 8461

TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.

Why this matters

Without TLS-RPT, you have no visibility into inbound TLS failures — MTA-STS misconfigurations stay hidden until users complain.

Learn more ▾

TLS-RPT (RFC 8460) is the feedback channel for MTA-STS: senders post aggregate reports of TLS-handshake failures to the URI in your _smtp._tls TXT record. Without it, an MTA-STS misconfiguration silently rejects mail and you find out only when someone notices missing email.

Source: RFC 8460

BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

Why this matters

Security gaps expose your site and users to attacks, eroding trust.

C

Permissions-Policy

Action

1 directives, 5 missing

REVIEW

1 directives, 5 missing

fullscreen=*

camera not restricted

Consider adding camera=() to block camera access from embedded content.

microphone not restricted

Consider adding microphone=() to block microphone access from embedded content.

geolocation not restricted

Consider adding geolocation=() to block geolocation access from embedded content.

payment not restricted

Consider adding payment=() to block payment access from embedded content.

usb not restricted

Consider adding usb=() to block usb access from embedded content.

Raw Header

fullscreen=*

Feature Permissions

Blocked Self Only Unrestricted Not Set

fullscreen Unrestricted

camera Not Set

microphone Not Set

geolocation Not Set

payment Not Set

usb Not Set

B

CORS Configuration

No CORS headers

REVIEW

No CORS headers

No CORS headers present — secure default

CORS Configuration ✓ Secure

No CORS headers detected.

Cross-origin requests are blocked by browser same-origin policy.

Origin reflection test

Some servers mirror the request Origin header, which can be exploited. Test manually:

curl -sI -H "Origin: https://evil.com" <url> | grep -i access-control

A+

TLS & Certificates

TLS 1.3, 8 checks passed

PASS

TLS 1.3, 8 checks passed

TLS 1.3 is used

Got: TLS 1.3

Strong cipher suite is used

Got: TLS_CHACHA20_POLY1305_SHA256

HTTP/2 is negotiated

Got: h2

OCSP stapling not enabled

Without stapling, the browser performs a separate OCSP roundtrip on first connection -- adding latency and leaking the visited host to the CA. Enable OCSP stapling on your TLS server.

Certificate is valid (expires in 30 days)

Got: 2026-09-24T12:24:47Z

Certificate chain has 3 certificates

Certificate uses modern signature algorithm

Got: SHA256-RSA

Certificate covers 19 domain(s)

Got: customerracing.mercedes-amg.com, experience.mercedes-amg.com, fleetsales-vans.mercedes-benz.com, g-class-test.mercedes-benz.com, g-class.mercedes-benz.com, karriere.mercedes-amg.com, mercedes-benz.com, nl.mercedes-amg.com, www.karriere.mercedes-amg.com, www.me.mercedes-benz-macao.com, www.me.mercedes-benz.com.cn, www.mercedes-amg-motorsport.com, www.mercedes-amg.com, www.mercedes-amg.de, www.mercedes-benz-merbag-adliswil.ch, www.mercedes-benz-pontresina.ch, www.mercedes-benz.com, www.mercedes.me, www.mercedesbenzplaces.com

Certificate is issued by a trusted CA

Got: CN=YR1,O=Let's Encrypt,C=US

Without stapling, the browser performs a separate OCSP roundtrip on first connection -- adding latency and leaking the visited host to the CA. Enable OCSP stapling on your TLS server.

Why this matters

Without OCSP stapling, every first-time visitor pays an extra OCSP roundtrip — and the CA learns who's visiting your site.

Learn more ▾

OCSP stapling has the server fetch its own revocation status from the CA and attach the signed response to the TLS handshake. Without it, browsers contact the CA directly: extra latency for the user and a privacy leak (the CA sees who connected). Enable ssl_stapling on (nginx) / SSLUseStapling On (Apache) / OCSPStapling = on (Caddy auto-enables).

Source: RFC 6961 / Mozilla Server-Side TLS guide

Connection

Protocol

TLS 1.3

Cipher Suite

TLS_CHACHA20_POLY1305_SHA256

HTTP Version

h2 (HTTP/2)

Certificate Chain

Leaf Certificate

Subject CN=www.mercedes-benz.comIssuer CN=YR1,O=Let's Encrypt,C=USValid 2026-06-26T12:24:48Z → 2026-09-24T12:24:47ZExpires in 30 days SANs customerracing.mercedes-amg.com, experience.mercedes-amg.com, fleetsales-vans.mercedes-benz.com, g-class-test.mercedes-benz.com, g-class.mercedes-benz.com, karriere.mercedes-amg.com, mercedes-benz.com, nl.mercedes-amg.com, www.karriere.mercedes-amg.com, www.me.mercedes-benz-macao.com, www.me.mercedes-benz.com.cn, www.mercedes-amg-motorsport.com, www.mercedes-amg.com, www.mercedes-amg.de, www.mercedes-benz-merbag-adliswil.ch, www.mercedes-benz-pontresina.ch, www.mercedes-benz.com, www.mercedes.me, www.mercedesbenzplaces.comSignature SHA256-RSASerial 5c0bcb867f39755df8ab6dca27445fb9955

Intermediate (CA Certificate)

Subject CN=YR1,O=Let's Encrypt,C=USIssuer CN=Root YR,O=ISRG,C=USValid 2025-09-03T00:00:00Z → 2028-09-02T23:59:59ZExpires in 740 days Signature SHA256-RSASerial a20253f15f2691c05dc1ce13b9bcca4e

Intermediate (CA Certificate)

Subject CN=Root YR,O=ISRG,C=USIssuer CN=ISRG Root X1,O=Internet Security Research Group,C=USValid 2026-05-13T00:00:00Z → 2032-09-02T23:59:59ZExpires in 2201 days Signature SHA256-RSASerial f24b6d17f9d9ad7cb1c9fea78782699f

A+

Cookie Security

No cookies set — no cookie security risks

PASS

No cookies set — no cookie security risks

No cookies detected — no cookie security risks to report.

A+

Cookie Hygiene

No cookies set -- cookie-hygiene check is N/A

PASS

No cookies set -- cookie-hygiene check is N/A

No cookies set

A+

Cross-Origin Tab Safety

No new-tab links found -- no tabnabbing surface

PASS

No new-tab links found -- no tabnabbing surface

No new-tab links present

A+

CSP Inline-Style Readiness

No inline style attributes -- strict CSP is feasible

PASS

No inline style attributes -- strict CSP is feasible

No inline style attributes detected

A+

Soft-404 Detection

HTTP status is non-2xx -- soft-404 check is N/A

PASS

HTTP status is non-2xx -- soft-404 check is N/A

A+

Empty Page Detection

Page has substantive body text and no placeholder / template-leak signals

PASS

Page has substantive body text and no placeholder / template-leak signals

A+

Geo-Restriction Detection

No geo-restriction signals detected -- scan reached the page from an allowed region

PASS

No geo-restriction signals detected -- scan reached the page from an allowed region

No geo-restriction detected

A+

Maintenance Mode Detection

No maintenance-mode signals detected -- scan reached a normal page

PASS

No maintenance-mode signals detected -- scan reached a normal page

No maintenance-mode signals detected

A+

Subresource Integrity Adoption

Page has no third-party scripts or stylesheets -- SRI not applicable

PASS

Page has no third-party scripts or stylesheets -- SRI not applicable

No third-party scripts or stylesheets to protect with SRI

A+

CORS Depth

No CORS response headers -- the resource is same-origin-only by browser default

PASS

No CORS response headers -- the resource is same-origin-only by browser default

A+

Source Map Exposure

Source-map probe didn't run on this scan

PASS

Source-map probe didn't run on this scan

A+

HTML Version Disclosure

No software-version disclosures in HTML

PASS

No software-version disclosures in HTML

A+

Open Redirect Surface

No redirect-shaped query parameters in DOM links

PASS

No redirect-shaped query parameters in DOM links

A+

Auth Security

Page is not a login form -- auth-security checks are N/A

PASS

Page is not a login form -- auth-security checks are N/A

Page does not appear to be a login form

A+

Subresource Integrity

No external resources

PASS

No external resources

No external resources to protect

SRI Coverage No external resources — SRI not applicable

A+

JS Library Vulnerabilities

No known vulnerabilities

PASS

No known vulnerabilities

No known JavaScript library vulnerabilities detected

No known JavaScript library vulnerabilities detected.

A+

Information Leakage

No exposures

PASS

No exposures

No security.txt found

Consider adding a security.txt at /.well-known/security.txt.

No sensitive files exposed

No sensitive files exposed — all paths returned 404.

Path	Status	Category	Risk
/.git/HEAD	✓ Not found	Version Control	—
/.git/config	✓ Not found	Version Control	—
/.svn/entries	✓ Not found	Version Control	—
/.env	✓ Not found	Configuration	—
/.env.local	✓ Not found	Configuration	—
/.env.production	✓ Not found	Configuration	—
/wp-config.php	✓ Not found	Configuration	—
/.htaccess	✓ Not found	Configuration	—
/phpinfo.php	✓ Not found	Debug	—
/server-status	✓ Not found	Debug	—
/server-info	✓ Not found	Debug	—
/.well-known/security.txt	✓ Not found	Security Policy	—
/package.json	✓ Not found	dependency-manifest	—
/composer.json	✓ Not found	dependency-manifest	—
/Gemfile	✓ Not found	dependency-manifest	—
/Gemfile.lock	✓ Not found	dependency-manifest	—
/requirements.txt	✓ Not found	dependency-manifest	—
/pom.xml	✓ Not found	dependency-manifest	—
/.gitlab-ci.yml	✓ Not found	ci-config	—
/.travis.yml	✓ Not found	ci-config	—

A+

API Surface

No API specs or GraphQL introspection found (probed 11 candidate path(s))

PASS

No API specs or GraphQL introspection found (probed 11 candidate path(s))

No API specs or GraphQL introspection found (probed 11 path(s))

A+

Transport Security

HTTP/3, HSTS, and TLS version analysis

PASS

HTTP/3, HSTS, and TLS version analysis

HTTP/3 (QUIC) supported

The server advertises HTTP/3 via Alt-Svc for faster connections on mobile networks.

HSTS enabled (base policy)

HSTS missing includeSubDomains

Without includeSubDomains, HSTS only protects the exact domain.

TLS 1.3 in use (fastest handshake, 1-RTT)