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
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.
BTLS Certificate Expiry & Recommendations182 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 Records1 A records, 73 ms lookupPASS
| A | 217.70.184.55 |
| AAAA | — |
| CNAME | — |
| NS | ns-17-b.gandi.net, z.dns.gandi.net, ns-125-a.gandi.net, ns-189-c.gandi.net |
| MX | 10 stellantis-com.mail.protection.outlook.com |
| TXT | atlassian-domain-verification=T4LRzKerOSaB36ful1OsPhzhdHOzMI7T871uWTL3jN6EyK6xzL... google-site-verification=2wQcoCMybWh70ep78lxisJA9dkR-rtJr_DbfaY35e8E MS=ms64248232 airtable-verification=1501575ad97a342c6f28463b42cc3716 218c5173-5d5f-4ff9-9e7c-6ee4ef3288a2 atlassian-domain-verification=vxlTNEwrfSCCb06rxmZLHuBfqonZldHwJHdIjJwbbSaQeR/G8w... confluent-verification=35076ea0-3de4-4af8-8aa2-e24d0e47083a _pw5ti8hpbofvw4jhrlgsmvi5gjf1tmm SPF v=spf1 ip4:62.85.199.146 include:mpsa.com include:_spf.google.com -all atlassian-domain-verification=BXiTZWCYrgCh806pqJBa733Q094j866aD3ETa5ewhYp40f7y3a... apple-domain-verification=UBuAjRVDvGTt4Igs vmware-cloud-verification-c8e3dd4a-2ab0-431c-a2b8-dce1bdb3ef68 NJ3z4/FDFfKKDEfY3Gz1ovd675kCEAzfdEIoaA7JkFNCq08XuVOEmQhpZ3hV1e39JkyQVL+fWYBeYOYx... google-site-verification=_x1Kcw0NfWaWw1lPbUqCyYsI1TcdUVDWluuSdEgjVCk dynatrace-site-verification=67f01756-d8e4-4d55-a35b-35752792003c__9in4hh7tbmv9bk... knowbe4-site-verification=95bb50d6866f531fda7c21b78af059f9 |
| 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.
ARedirect Chain1 redirect(s), 125 ms totalPASS
https://stellantis.com
53 ms · HTTP/1.1
https://www.stellantis.com/
72 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://stellantis.com | 301 | 53 ms | HTTP/1.1 | |
| 2 | https://www.stellantis.com/ | 403 | 72 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencestellantis.com — via Gandi SAS, 20 years, 9 months old, hosted on GANDI-AS Domain name registrar - www.gandi.net, FRPASS
115 days
November 6, 2026
182 days
Issued by Gandi SAS
20 years, 9 months
Registered November 6, 2005
Enabled
Protects against DNS spoofing
GANDI-AS Domain name registrar - www.gandi.net, FR
ASN AS29169
217.70.184.55
Gandi SAS
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