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.
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
CCrawlabilityActionrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.
Learn more ▾ ▴
Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.
Source: sitemaps.org / Google Search Central
An empty sitemap provides no value. Add <url> entries for your pages.
An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.
Learn more ▾ ▴
Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.
Source: Google Search Central / sitemaps.org
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
<html>
<head>
<META NAME="robots" CONTENT="noindex,nofollow">
<script src="/_Incapsula_Resource?SWJIYLWA=5074a744e2e3d891814e9a2dace20bd4,719d34d31c8e3a6e6fffd425f7e032f3">
</script>
<body>
</body></html>
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations36 days until leaf cert expires — 2 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+DNS Records2 A records, 69 ms lookupPASS
| A | 107.154.76.60, 107.154.214.60 |
| AAAA | — |
| CNAME | — |
| NS | ns1.thalesgroup.com, ns2.thalesgroup.com, nsa.perf1.fr, nsb.perf1.com, nsc.perf1.com |
| MX | 10 mx01.thalesgroup.com 10 mx02.thalesgroup.com |
| TXT | h9pjos01vgfld5qmp5otsg8goi hvs9elcn2us2bmmr4lb217iqbr n3r0i5dfdh6s2j147759bjqc9g sira8n255q3eerml42cnap84vq _d49pol435n49yiy9w1qv5ne99s3lml3 SPF v=spf1 include:_spf.thalesgroup.com -all status-page-domain-verification=6c590zq20csn docusign=a706bb1e-98da-4486-bf34-bc3ba14c1a42 google-gws-recovery-domain-verification=40875700 google-gws-recovery-domain-verification=41180339 mongodb-site-verification=urJggNtlDng5wmv1jcjrXmBo9Eb0XGwN onetrust-domain-verification=e84c2e4e1c404b7f89251829627370e5 monday-com-verification=WGu507HMpAaVXhGlx3MFTj8N_gTWVc4P169OBWSGq4w parkable-domain-verification=KuSRPxVkcuVRN7997PFq7HuEKE_3Nr96aSjoHl4C-_c= pardot128881=d94d95cd1e95d1ba52129899fa698283281594bb461c87806c0e9e5cb1de73a7 stripe-verification=61B187947CCA16D0A3A2474834921E83DC33DCDA485DB744E9FC35ABE133... box-domain-verification=1488c4fa92053c9774352272eebca47a72f4c4f8e3dc3be8aa1ec3f6... box-domain-verification=acc4ffbec3edacf60e2e9e692a949a186d731f1ae02ae4b527301ec7... adobe-idp-site-verification=84253922d9f14b77c7b36641372e8c6c92f90e6ec02b32b46f25... cisco-ci-domain-verification=40f4f333defc02ef6e3f607ee7bbc5dbaecd4ba7a838156e4c3... cisco-ci-domain-verification=7dfc7f852b0e0d4d8ee4813ed29133d2775615bbb24903c07b2... atlassian-domain-verification=C8udnPAPnyatzbI4a0shdz5eVoY9BNckAvgfI99VAKwR3QiHSn... atlassian-domain-verification=QeBfwUoyAGJnMRmwGDlvGZQt9aOGErqK0xbA/Qj3WVKAwPPfn4... atlassian-domain-verification=owkhwuAcFuyTiUw4/EgbOofPLoJBM6ysS9MH1qLWXs3RAvZ14t... atlassian-domain-verification=rBJE2yFc7keNCJbkJbMD8pT1rBUjapGaz1gwCEY26VMJEiSW8a... atlassian-domain-verification=vLY7nBwvQAoPuK077ly9s1x3MDaKBP3iSkDrigs82hcW51Z7p5... |
| 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.
ARedirect Chain1 redirect(s), 31 ms totalPASS
https://thalesgroup.com
20 ms · HTTP/1.1
https://www.thalesgroup.com/
11 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://thalesgroup.com | 301 | 20 ms | HTTP/1.1 | |
| 2 | https://www.thalesgroup.com/ | 200 | 11 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
A+Domain Intelligencethalesgroup.com — via CSC Corporate Domains, Inc., 25 years, 9 months old, hosted on INCAPSULA - Incapsula Inc, USPASS
112 days
November 7, 2026
36 days
Issued by GlobalSign nv-sa
25 years, 9 months
Registered November 7, 2000
Enabled
Protects against DNS spoofing
INCAPSULA - Incapsula Inc, US
ASN AS19551
107.154.76.60
CSC Corporate Domains, Inc.
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