Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BRedirect Chain2 redirect(s), 536 ms totalREVIEW
https://continental.com
104 ms · HTTP/1.1
https://www.continental.com//
154 ms · HTTP/1.1
https://www.continental.com/en/
278 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://continental.com | 301 | 104 ms | HTTP/1.1 | Apache |
| 2 | https://www.continental.com// | 301 | 154 ms | HTTP/1.1 | Apache |
| 3 | https://www.continental.com/en/ | 200 | 278 ms | HTTP/1.1 | Apache |
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
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
BTLS Certificate Expiry & Recommendations75 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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
A+DNS Records1 A records, 53 ms lookupPASS
| A | 3.65.150.226 |
| AAAA | — |
| CNAME | — |
| NS | dns1.cscdns.net, dns2.cscdns.net |
| MX | 0 continental-com.mail.protection.outlook.com |
| TXT | atlassian-domain-verification=h/Kps8flhPcPt3ca8Nmrau1smICGPtjpoJajgtuDYUS5dcmfmy... docusign=c271e5cf-ba72-4465-933c-941b96626390 Google-site-verification=iH1wwK8MsW2ucUAIcKBvqp7AGuQwKf8W2Jgw4-KHQ0k 00D9Q00000IXGA7=1TB9Q0000000Nr3;00Dbh000005SRon=1TBbh000000074n;00D9K00000VPGNt=... docusign=1305dcfa-cdce-47b2-b9b9-4d00580b3923 d365mktkey=rVu1IkuBK91xZeEhFbwPvYWGutaMkZvuuQ7xacEf7W4x SPF v=spf1 include:spf.contiwan.com ip4:81.14.180.92 -all iupW1sEU48rqUh8lF66cHgUyZIasAfklu+4w/G6Qy8UJ69bV0Jf+WNSDMY4MVm2sFQFhwlFTiQt2KHsa... |
| 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+Crawlabilityrobots.txt present, sitemap with 4 URLsPASS
User-Agent: *
Allow: /
# Only allow URLs generated with frontend routing
Disallow: /*?id=*
Disallow: /*&id=*
# L=0 is the default language
Disallow: /*?L=0*
Disallow: /*&L=0*
# Disallow API PageTypes for jobportal
Disallow: */api/*/pagetype-jobs/$
# Disallow folders
# Disallow: /typo3
# Sitemap: International
sitemap: https://www.continental.com/en/xmlsitemap
sitemap: https://www.continental.com/de/xmlsitemap
# Sitemap: America
sitemap: https://www.continental.com/en-us/xmlsitemap
sitemap: https://www.continental.com/es-mx/xmlsitemap
# Sitemap: Asia
sitemap: https://www.continental.com/zh-cn/xmlsitemap
sitemap: https://www.continental.com/ja-jp/xmlsitemap
sitemap: https://www.continental.com/ko-kr/xmlsitemap
#Sitemap: Europe
sitemap: https://www.continental.com/cs-cz/xmlsitemap
sitemap: https://www.continental.com/fr-fr/xmlsitemap
sitemap: https://www.continental.com/hu-hu/xmlsitemap
sitemap: https://www.continental.com/ro-ro/xmlsitemap
#Sitemap: Jobportal
sitemap: https://jobs.continental.com/en/xmlsitemap
sitemap: https://jobs.continental.com/de/xmlsitemap
sitemap: https://jobs.continental.com/cz/xmlsitemap
sitemap: https://jobs.continental.com/zh/xmlsitemap
sitemap: https://jobs.continental.com/fr/xmlsitemap
sitemap: https://jobs.continental.com/es/xmlsitemap
sitemap: https://jobs.continental.com/ja/xmlsitemap
sitemap: https://jobs.continental.com/ko/xmlsitemap
sitemap: https://jobs.continental.com/lt/xmlsitemap
sitemap: https://jobs.continental.com/hu/xmlsitemap
sitemap: https://jobs.continental.com/ro/xmlsitemap
sitemap: https://jobs.continental.com/pt/xmlsitemap
sitemap: https://jobs.continental.com/sk/xmlsitemap
sitemap: https://jobs.continental.com/sr/xmlsitemap
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencecontinental.com — via CSC Corporate Domains, Inc., 28 years, 9 months old, hosted on AWSPASS
179 days
December 10, 2026
75 days
Issued by Let's Encrypt
28 years, 9 months
Registered December 11, 1997
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
3.65.150.226
CSC Corporate Domains, Inc.
Expiry timeline
Recommended actions
- 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