Skip to content
https://mercedes-benz.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
9
PASS
7
INFO
0
Probed from New York, United Stated
403 Forbidden
Checks
17
7 PASS 9 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 23.212.249.197 does not match any cert SAN: a23-212-249-197.deploy.static.akamaitechnologies.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 403 Expected: 301 redirect to HTTPS

www / non-www

403https://www.mercedes-benz.com/
200https://mercedes-benz.com/

HTTP → HTTPS

403http://mercedes-benz.com/

HTTP version does not redirect to HTTPS

B
TLS Certificate Expiry & Recommendations
30 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

30
days left
0d 30d 60d 90d+

Recommended actions

  • Renew certificate — 30 days remaining
  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
A+
DNS Records
1 A records, 86 ms lookup
PASS
1 A records, 86 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.212.249.197
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns3.corpinter.net, ns2.corpinter.de, ns4.corpinter.de, ns1.corpinter.net
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 86 ms
Got: 86 ms
A23.212.249.197
AAAA
CNAME
NSns3.corpinter.net, ns2.corpinter.de, ns4.corpinter.de, ns1.corpinter.net
MX
0 one.mail-in.corpinter.net
0 two.mail-in.corpinter.net
TXT
autodesk-domain-verification=YmxyRF1KC95BoeNFPHeb
mongodb-site-verification=adiurx3rN7Gi0713MDHKbUhB3UNJhtmQ
_q4qvxpq6b14xvim5odx0b59g2jp7pce
cisco-ci-domain-verification=878c26d09ac4bbfc340f4a39516ad2a4be09379bcfbe77077ae...
bw=hUMsqhVyULyfYdcsBtKuRYi64Y8Pd4lCFaYdOzANop11
00D3N0000008mzh=1TBhE00000002g9
atlassian-domain-verification=yqM4YvwXs0ztgzqU6sG55pK1DevTpTDF5D2Pk+IeY0TR7AFpzK...
QuoVadis=6bbde5e1-0c44-4a1b-af09-fc1b66a6c87a
figma-domain-verification=6ac09327201f2e09d80749d1ac3b8b1787e26d6c866bc08280645c...
_skc2rrt4zvycjx1p3ynxb4ihj16xkb7
00DhE000000KqC9=1TBhE00000003lt;00D7Z0000004r7Z=1TB9Z0000000B5C;00D0D0000004Y0y=...
_jjniu44dn9b50qzsazr1shj07xw7vsi
_l9j2hinjhf25prwzr02zqaacro78s1j
mongodb-site-verification=qCLSse4Ig5lhafvT3AfcnI4nDj3BKHbm
C98Sb4ucEsN7ovpCHiSQsSp8JxIY2etc9gBghhF393L5
_2c9xzirxpituymx00murdaix06fs3jg
apple-domain-verification=QzjDx9YZ5zEj7pOt
_d45z3f77pgmwb6qfmlgxltrwai1u5b3
_sa03aump69hvrxg1b15x5u76yhx7l36
_hx5dbo0chnv2hg27le7dmt4gu2t76dy
SPF v=spf1 include:spf1.corpinter.net include:amazonses.com include:cust-spf.exactta...
MS=ms55145870
6gqx90kmxv6j7n72f6qcfzz60xt8nfgq
2ctjysp7tlmcw1754yrs8pxqjnqdf79f
adobe-sign-verification=259c5de2eb3b734828be86a8833a7c8e
Dynatrace-site-verification=3ae56f3e-9cb5-4f23-92c7-2f30172a6408__r88geturb7a0gq...
_lixwqk8uklrhfgm9arfa3sg56wwz422
bw=zs1CzTUZCoUZRR2DOxLbw3IiXVxijTWw5KNsl9aiVH4H
5238u2r90uli2cq1gvrg8cq6g1
atlassian-domain-verification=HWRid0T68KPt0tlxLiI24rYOqzux5IufCi6oHOdImax6Tgw3Mb...
google-site-verification=lqCsItUjF1RKw2IdQIiCVNHdXMYnVXw3A4C-fglJj1M
brevo-code:ba173f68e6b3ee388a9665d6d27f0dbb
_pyvk67f4zhef6kxz4jeqzzscud4xndk
adobe-idp-site-verification=98751110d46d127b486658a7b79f6f4ee8d6bbe7f2e6129b1cd2...
lrctk7kwk9vzv2t8v5jfws53t1k2ykwk
_32mrp3jxfqblaeaysmxo1i14tbaqjhr
TkJJzWmf2shqVgoa/D53XX1n4O8IpQQ3X0/ey4zc6rzpa72/Az3HykRXyKckMcvwbQGOn+M5hseTrjPi...
docusign=3fea104d-aad3-4de2-8b9b-1a2ef5f8dc63
cisco-ci-domain-verification=297a419516011b11798908289d0829fd876071eea76ef394c06...
_h6ep2r9pah2ohjif1ayq8167b32113l
_srvkzcazlv5uf3uu5lo6wcjsmsmnero
slack-domain-verification=dO9QoZaR8XRaGzQhWqfpuewjmHjPYil6rr7V0lW3
42219c8y3yz9jjvdd5w1vwgnhd2t9tmw
airtable-verification=04ccd98e74d1a2d7056beb7cd3b734f5
biBZ13gDDYog6XvQuy_w2rx948TJJwtO2oBzSn2idsc
_344n1dwu3j46w75lpa7owpwonx5t71q
openai-domain-verification=dv-WPu1yUWrWail3Ji9IXehBb2J
QuoVadis=44e4cbf1-6dd5-4084-9fbb-10624df7a8b1
cnhky9r3htmvm427p2t3fsxzbx1z8vpv
QuoVadis=42f2010f-0c2f-4ca7-84d2-7efb8e579fb5
yandex-verification: 1bea86ec2bf53817
_xru24ougigte5zyjiw1yhmedzjtobpd
google-site-verification=KsIMpiGbKaUJa0i5-aUWQJlcxlSCOGSYC0IqXzDwAZA
facebook-domain-verification=tp909dis1jat771ten1ucn6uczko20
_x7ya8gkb2eanjh2scvk3tfy6pf8hn32
cloudflare_dashboard_sso=f972e20c2a04f97c3d5b1b9a265fb315
jsvk4prqj8dzts5nj9v4lq90sjq3tz7r
CAALookup not available with standard resolver
Resolved in 86 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 3ms across 3 resolvers (spread 6ms)
PASS
Mean 3ms across 3 resolvers (spread 6ms)
Info::
Quad9: 1ms
Got: 1ms via 9.9.9.9:53
Info::
Cloudflare: 2ms
Got: 2ms via 1.1.1.1:53
Info::
Google: 7ms
Got: 7ms via 8.8.8.8:53
A+
Redirect Chain
0 redirect(s), 46 ms total
PASS
0 redirect(s), 46 ms total

https://mercedes-benz.com

46 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mercedes-benz.com40346 msHTTP/1.1
A+
Domain Intelligence
mercedes-benz.com — via Key-Systems GmbH, 32 years, 2 months old, hosted on Akamai
PASS
mercedes-benz.com — via Key-Systems GmbH, 32 years, 2 months old, hosted on Akamai
Info::
Domain registered until Dec 8, 2034 (8 years, 4 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Key-Systems GmbH
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: Akamai
Got: AS20940
Domain expiry

3026 days

December 8, 2034

SSL certificate

30 days

Issued by Let's Encrypt

Domain age

32 years, 2 months

Registered December 9, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Akamai

ASN AS20940

23.212.249.197

Registrar

Key-Systems GmbH

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the TLS certificate or verify auto-renewal is working
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Key-Systems GmbH
Created December 9, 1994 (32 years, 2 months ago)
Expires December 8, 2034 (8 years, 4 months)
Last Updated January 30, 2025
Name Servers ns1.corpinter.net, ns2.corpinter.de, ns3.corpinter.net, ns4.corpinter.de
DNSSEC Not enabled
Hosting
IP Address 23.212.249.197
ASN AS20940 (AKAMAI-ASN1 - Akamai International B.V., NL)
Provider Akamai
Data source: rdap (0.7s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 146 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
10 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
7 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
22 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
146 ms
Total Time Total request time from DNS lookup through full response.
146 ms

Connection waterfall

DNS Lookup 10 ms TCP Connect 7 ms TLS Handshake 22 ms Server Processing 107 ms Content Transfer 0 ms
A+
Health Check Endpoint
Auth-protected health endpoint at https://mercedes-benz.com/health (HTTP 403)
PASS
Auth-protected health endpoint at https://mercedes-benz.com/health (HTTP 403)
Info::
Auth-protected health endpoint exposed at https://mercedes-benz.com/health
Got: https://mercedes-benz.com/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback