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 Chain1 redirect(s), 1294 ms totalREVIEW
https://qt.io
413 ms · HTTP/1.1
https://www.qt.io/
881 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://qt.io | 301 | 413 ms | HTTP/1.1 | Apache |
| 2 | https://www.qt.io/ | 200 | 881 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
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, sitemap with 4065 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
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: *
Disallow: /qt-microncontrollers-mcu
Disallow: /faq/tag/quality-assurance-tools
Disallow: /_hcms/preview/
Disallow: /hs/manage-preferences/
Disallow: /hs/preferences-center/
Disallow: /*?*hs_preview=*
Disallow: /*?*hsCacheBuster=*
- https://www.qt.io/ja-jp/software-insights/why-cyber-resilience-requires-a-cultural-shift
- https://www.qt.io/hubfs/axivion-static-code.svg
- https://www.qt.io/hubfs/axivion-architecture.svg
- https://www.qt.io/hubfs/Qt%20Foundation%20Images%20Cybersecurity%20tinified.webp
- https://www.qt.io/hubfs/cybersecurity-featured.webp
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations72 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- 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, 91 ms lookupPASS
| A | 52.18.144.254 |
| AAAA | — |
| CNAME | — |
| NS | ns-175-a.gandi.net, ns-243-b.gandi.net, ns-49-c.gandi.net |
| MX | 11 qt-io.mail.protection.outlook.com |
| TXT | d358f430575bfe0c07fe7d85e526cda4 MS=ms34905030 google-site-verification=x8WScTrJ9ix9wGVVMih54OmbjQlcTb93z1HWxVZSOKo google-site-verification=bIhnm2Ko3OmLAEP0Dqp0_aJNyJz9zj6KyJKAb1Lo-es adobe-idp-site-verification=5a9d3918e132584ef70084471019760d1f5fb941fe9b3ddc4a77... apple-domain-verification=GWcDIO9uyCe4GGpL google-site-verification=XaLRKRce2ApHGZ6a8Q9VYSPgfygWOFbPYBRA8eE4Zvg arcules-domain-verification=92HOwpXQ4tbPBwDdib1idz8C7aQti4XGrIdVw6iaDQ3 google-site-verification=dnHgPPxUI9getHLFrlO7Fpx8GY4Pd9230AELyJkvgNs google-site-verification=d8jqwffKE2mRhvhJdZTPxD9XLjwpsYON51TAzNZZfx8 atlassian-domain-verification=KRzg78ZwrC/vsGe46xjVujbUKgaktsrwFKVMEyxTJJDtHGMYpG... heroku-domain-verification=0acrf/kb66cr7//nvtsxtsgd9y25ko9anug/jektua miro-verification=1c7af488d2ace09f31a534a1368692bc11edf243 99276D386F mongodb-site-verification=0qQyK8XwDiC6yjd0jk6jDkCbChQvLmgc bw=hR3GkePw0j1SPsYgU6F4JKXXIp2P39YapY8zrdhsWlPa _hzw8eeg9uhc5xj936jv9ppo0ou0mj4m onetrust-domain-verification=27fb6526511f414991230f79866be4b6 atlassian-domain-verification=i8pPqj4ggCz3/YBvj8DMzCG58lyu3fzsJPutfJTAkiaPAOQu08... anthropic-domain-verification-ch5kez=eYXhvn33RZy2cVDWORssUT311 atlassian-domain-verification=yYhrDkw8Rnnyok67W7yQhZpOtA6NL0Kie9/lt/IqUNx0PyL16B... SPF v=spf1 include:spf.protection.outlook.com ip4:217.11.52.118 ip4:109.75.234.198 i... atlassian-domain-verification=qOx2x54JGZLNHHWOtVunc0TVNvi5l7J5x8eunJ7Qo6Dd5Rpvka... _uke11iecfkh76pdy9fvt1scsxjv5guz hpe-greenlake-domain-verification=52335378636f3149675a5679637a7863696c6e44696131... |
| 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+Domain Intelligenceqt.io — via Gandi SAS, 12 years, 8 months old, hosted on AWSPASS
111 days
October 5, 2026
72 days
Issued by Let's Encrypt
12 years, 8 months
Registered October 5, 2013
Status unknown
Protects against DNS spoofing
AWS
ASN AS16509
52.18.144.254
Gandi SAS
Expiry timeline
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Registrar lock (clientTransferProhibited et al.) prevents unauthorized domain transfers — strongest defense against domain hijacking.
Source: ICANN / domain-security best practice