Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FRedirect ChainAction4 redirect(s), 3849 ms totalFIX
https://siemens.de
336 ms · HTTP/1.1
https://www.siemens.de/
1017 ms · HTTP/1.1
https://www.siemens.com/de/de.html
1009 ms · HTTP/1.1
https://www.siemens.com/de-de
1301 ms · HTTP/1.1
https://www.siemens.com/de-de/
186 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://siemens.de | 301 | 336 ms | HTTP/1.1 | C2 Comms Cloud ALB (cf3d0181) |
| 2 | https://www.siemens.de/ | 301 | 1017 ms | HTTP/1.1 | C2 Comms Cloud (cf3d0181) |
| 3 | https://www.siemens.com/de/de.html | 302 | 1009 ms | HTTP/1.1 | C2 Comms Cloud (bc8a9c26) |
| 4 | https://www.siemens.com/de-de | 302 | 1301 ms | HTTP/1.1 | C2 Comms Cloud (bc8a9c26) |
| 5 | https://www.siemens.com/de-de/ | 200 | 186 ms | HTTP/1.1 | C2 Comms Cloud (bc8a9c26) |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
If permanent, use 301 instead.
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
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BCrawlabilityno robots.txt, no sitemapREVIEW
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
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.
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
No robots.txt found
This is fine for most sites — a missing robots.txt allows all crawling by default.
No sitemap found
Adding a sitemap helps search engines discover your pages.
BHTTP Probe TimingTotal 843 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations115 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Submit your domain to hstspreload.org to be added to the Chrome preload list
- 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
A+DNS Records2 A records, 30 ms lookupPASS
| A | 99.83.253.123, 75.2.23.197 |
| AAAA | — |
| CNAME | — |
| NS | a13-65.akam.net, a1-16.akam.net, a2-67.akam.net, a28-65.akam.net, ns1.f5cloudservices.com, a10-64.akam.net, a11-66.akam.net, ns2.f5cloudservices.com |
| MX | — |
| TXT | apple-domain-verification=B6zInkqUvZXleUpI vfCYWG3t7+BFlXRdz2uVL/KOjK7FlO9XvzXoYUVAQr3jr1yeSBtlEThD+3s7WIDnMDtbPYxNx4KBQd2W... UGB1HgiDq2zxxakfWxkhRnUa3ps80ndhMpvyjz+KZeaMO/blPadvqSk2jN1VgAX+rtz5FuZnwhbXV9R0... SPF v=spf1 -all google-site-verification=SoZROX3SGoBI8aXI0cM83NcW_G6ScilHQFYzokozmcY MS=ms35647779 |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencesiemens.de — hosted on AWSPASS
Unknown
115 days
Issued by Amazon
Unknown
Status unknown
Protects against DNS spoofing
AWS
ASN AS16509
99.83.253.123
Registrar unknown
Expiry timeline
Recommended actions
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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.
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