Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FRedirect ChainAction4 redirect(s), 744 ms totalFIX
https://thieme-connect.com
98 ms · HTTP/1.1
https://www.thieme.de/connect/en
211 ms · HTTP/1.1
http://www.thieme.de/en/thieme-connect/h...
71 ms · HTTP/1.0
https://www.thieme.de/en/thieme-connect/...
151 ms · HTTP/1.1
https://www.thieme.com/en-us/who-we-serv...
213 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://thieme-connect.com | 302 | 98 ms | HTTP/1.1 | Apache |
| 2 | https://www.thieme.de/connect/en | 301 | 211 ms | HTTP/1.1 | |
| 3 | http://www.thieme.de/en/thieme-connect/h... | 301 | 71 ms | HTTP/1.0 | |
| 4 | https://www.thieme.de/en/thieme-connect/... | 301 | 151 ms | HTTP/1.1 | |
| 5 | https://www.thieme.com/en-us/who-we-serv... | 200 | 213 ms | HTTP/1.1 | AmazonS3 |
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
Redirect directly from https://thieme-connect.com to https://www.thieme.com/en-us/who-we-serve
Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.
Source: 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
BCrawlabilityrobots.txt present, no sitemapREVIEW
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
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
User-agent: PetalBot
Disallow: /
User-agent: Twitterbot
Disallow: /
User-agent: Amazonbot
Disallow: /
User-agent: meta-externalagent
Disallow: /
User-agent: meta-webindexer
Disallow: /
User-agent: meta-externalads
Disallow: /
User-agent: meta-externalfetcher
Disallow: /
User-agent: GPTBot
Disallow: /
User-agent: ChatGPT-User
Disallow: /
User-agent: Applebot
Disallow: /
User-agent: AhrefsBot
Disallow: /
User-agent: AcademicBotRTU
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: bingbot
Disallow: /
User-agent: YandexBot
Disallow: /
User-agent: Yandex
Disallow: /
User-agent: OAI-SearchBot
Disallow: /
User-agent: Amazonbot
Disallow: /
User-agent: amazon-kendra-web-crawler
Disallow: /
User-agent: Amzn-SearchBot
Disallow: /
User-agent: SemrushBot
Disallow: /
User-agent: SemrushBot-BA
Disallow: /
User-agent: SemrushBot-SI
Disallow: /
User-agent: SemrushBot-SWA
Disallow: /
User-agent: SemrushBot-OCOB
Disallow: /
User-agent: SiteAuditBot
Disallow: /
User-agent: SplitSignalBot
Disallow: /
User-agent: dotbot
Disallow: /
User-agent: DotBot
Disallow: /
User-agent: CCBot
Disallow: /
User-agent: SERankingBacklinksBot
Disallow: /
User-agent: SERankingBot
Disallow: /
User-agent: *
Disallow: /vbsadmin/
Disallow: /DOI/
Disallow: /rss/
Disallow: /bilder/
Disallow: /media/
Disallow: /preview/
Disallow: /assets/
Crawl-delay: 2
No sitemap found
Adding a sitemap helps search engines discover your pages.
BTLS Certificate Expiry & Recommendations77 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- 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
A+DNS Records1 A records, 53 ms lookupPASS
| A | 141.66.193.71 |
| AAAA | — |
| CNAME | — |
| NS | ns.udag.de, ns.udag.org, ns.udag.net |
| MX | 10 mx.thieme.de 30 mxa.thieme.de 30 mxb.thieme.de |
| TXT | 37llmwr98d4hd34z258sslswnnbkl7lt SPF v=spf1 mx include:_spf.thieme.de -all n9dzxhrggqnlsbs6vh97hfqzd5w8g9fh google-site-verification=fZc6F6VFkxuYz7PYlrbA8Xy5Ozie7FbmPuN7zzKdM5Y _vd21sgliwg7082a5o6po0j2h66mt30l |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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
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 Intelligencethieme-connect.com — via united-domains GmbH, 26 years, 11 months old, hosted on ASN-FIZ, DEPASS
88 days
October 8, 2026
77 days
Issued by DigiCert Inc
26 years, 11 months
Registered October 8, 1999
Not enabled
Protects against DNS spoofing
ASN-FIZ, DE
ASN AS13040
141.66.193.71
united-domains GmbH
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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