Infrastructure - https://Diehl.com BeaverCheck Audit

F

Redirect Chain

Action

4 redirect(s), 845 ms total

FIX

4 redirect(s), 845 ms total

4 redirects before reaching final URL

Each redirect adds latency. Try to minimize the chain to 1 hop.

WWW normalization redirect

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://www.diehl.com/group/en/

Redirect overhead: 845 ms total

Got: 845 ms

Cross-domain redirect detected

https://Diehl.com

104 ms · HTTP/1.1

301

https://www.diehl.com/

252 ms · HTTP/1.1

301

https://www.diehl.com/group/

349 ms · HTTP/1.1

301

https://www.diehl.com/group/en/

37 ms · HTTP/1.1

302

https://new.diehl.com/group/en/

103 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://Diehl.com	301	104 ms	HTTP/1.1	Apache
2	https://www.diehl.com/	301	252 ms	HTTP/1.1	cloudflare
3	https://www.diehl.com/group/	301	349 ms	HTTP/1.1	cloudflare
4	https://www.diehl.com/group/en/	302	37 ms	HTTP/1.1	cloudflare
5	https://new.diehl.com/group/en/	200	103 ms	HTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

D

CDN & Delivery

Action

No CDN detected

FIX

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)

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)

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.

C

Reverse DNS

Action

0/1 IPs match cert SAN

REVIEW

0/1 IPs match cert SAN

PTR lookup failed for 193.201.238.43: lookup 193.201.238.43: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

C

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

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

Domain Intelligence

Diehl.com — via InterNetX GmbH, 30 years, 5 months old, hosted on DIEHL-CORP-AS, DE

REVIEW

Diehl.com — via InterNetX GmbH, 30 years, 5 months old, hosted on DIEHL-CORP-AS, DE

Domain expires in 0 days

This domain expires on May 16, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.

Got: Expires May 16, 2026

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.

Registrar: InterNetX GmbH

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.

Hosting: DIEHL-CORP-AS, DE

Got: AS25115

Domain expiry

EXPIRED

May 16, 2026

SSL certificate

50 days

Issued by Sectigo Limited

Domain age

30 years, 5 months

Registered May 15, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

DIEHL-CORP-AS, DE

ASN AS25115

193.201.238.43

Registrar

InterNetX GmbH

Unlocked 6 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Domain has EXPIRED — renew immediately to avoid total site outage
Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar InterNetX GmbH

Created May 15, 1996 (30 years, 5 months ago)

Expires May 16, 2026 (EXPIRED)

Last Updated May 17, 2025

Name Servers ns.diehl.com, ns01.diehl.com, ns02.diehl.com, ns10.managed-ip.com, ns11.managed-ip.info, ns12.managed-ip.info

DNSSEC Not enabled

Hosting

IP Address 193.201.238.43

ASN AS25115 (DIEHL-CORP-AS, DE)

Provider DIEHL-CORP-AS, DE

Data source: rdap (0.5s)

This domain expires on May 16, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

B

TLS Certificate Expiry & Recommendations

50 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

50

days left

0d 30d 60d 90d+

Recommended actions

Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
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

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

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, 45 ms lookup

PASS

1 A records, 45 ms lookup

Resolves to 1 IPv4 address(es)

Got: 193.201.238.43

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

6 nameserver(s) configured

Got: ns11.managed-ip.info, ns01.Diehl.com, ns10.managed-ip.com, ns12.managed-ip.info, ns02.Diehl.com, ns.Diehl.com

2 mail exchanger(s) configured

SPF record present in TXT

DNS resolution time: 45 ms

Got: 45 ms

A	193.201.238.43
AAAA	—
CNAME	—
NS	ns11.managed-ip.info, ns01.Diehl.com, ns10.managed-ip.com, ns12.managed-ip.info, ns02.Diehl.com, ns.Diehl.com
MX	10 enterprise02.smtp.Diehl.com 10 enterprise01.smtp.Diehl.com
TXT	SPF v=spf1 mx -all swisssign-check=bxcHRGTeAEmVGM9L1grJzxgGqLU asv=2b6b041553cce57ddedea9468ec65b63 MS=ms74426895 adobe-sign-verification=9785d981ac74a329122ad601f1de0c4d ca3-a472567651b5440b8b81fcb6674f82c0 ca3-f7609326720a495b86bc90fe5cceaa88 docusign=b0b685c8-f86c-4eee-bc22-7e3f727038e4 atlassian-domain-verification=HCsdeZliE/B674da0T08au3wx03ynhEcOQztyJWiSsvVTQgnSb...
CAA	Lookup not available with standard resolver

Resolved in 45 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

No CNAME record present

A+

Multi-Resolver DNS Speed

Mean 45ms across 3 resolvers (spread 11ms)

PASS

Mean 45ms across 3 resolvers (spread 11ms)

Google: 42ms

Got: 42ms via 8.8.8.8:53

Cloudflare: 42ms

Got: 42ms via 1.1.1.1:53

Quad9: 53ms

Got: 53ms via 9.9.9.9:53

A+

Crawlability

robots.txt present, sitemap with 28 URLs

PASS

robots.txt present, sitemap with 28 URLs

robots.txt is present

Got: 107 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 28 entries

Sitemap index with 28 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 107 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed

User-Agent: *
Disallow: /cms/admin/
Disallow: /ecomaXL/admin/

Sitemap: https://www.diehl.com/sitemap.xml

sitemap.xml 200 OK

Type Sitemap Index URLs 28 entries Valid XML Yes

Child Sitemaps:

A+

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

www/non-www redirect configured correctly (preferred: non-www)

HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.Diehl.com/

200https://Diehl.com/

Preferred variant: non-www

HTTP → HTTPS

301http://Diehl.com/ → https://www.diehl.com/

Consistent

A+

HTTP Probe Timing

Total 167 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

45 ms

TCP Connect

29 ms

TLS Handshake

64 ms

Time to First Byte

167 ms

Total Time

168 ms

Connection waterfall

DNS Lookup 45 ms TCP Connect 29 ms TLS Handshake 64 ms Server Processing 29 ms Content Transfer 0 ms

A+

Health Check Endpoint

Auth-protected health endpoint at https://Diehl.com/health (HTTP 401)

PASS

Auth-protected health endpoint at https://Diehl.com/health (HTTP 401)

Auth-protected health endpoint exposed at https://Diehl.com/health

Got: https://Diehl.com/health