Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction3 redirect(s), 963 ms totalFIX
https://www.rivian.com
218 ms · HTTP/1.1
https://rivian.com:443
247 ms · HTTP/1.1
https://rivian.com:443/fr-FR/
217 ms · HTTP/1.1
https://rivian.com:443/fr-FR
281 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.rivian.com | 308 | 218 ms | HTTP/1.1 | |
| 2 | https://rivian.com:443 | 307 | 247 ms | HTTP/1.1 | CloudFront |
| 3 | https://rivian.com:443/fr-FR/ | 308 | 217 ms | HTTP/1.1 | CloudFront |
| 4 | https://rivian.com:443/fr-FR | 200 | 281 ms | HTTP/1.1 | CloudFront |
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
BCrawlabilityrobots.txt present, sitemap with 2800 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
user-agent: *
allow: /
disallow: /404
disallow: /api/
disallow: /rccg-support
disallow: /experience/r1t
disallow: /experience/r1s
disallow: /trip-visualizer
disallow: /offers/api/
sitemap: https://rivian.com/sitemap.xml
sitemap: https://rivian.com/offers/sitemap.xml
host: rivian.com
BTLS Certificate Expiry & Recommendations311 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
ADNS Records4 A records, 36 ms lookupPASS
| A | 143.204.55.17, 143.204.55.94, 143.204.55.26, 143.204.55.33 |
| AAAA | — |
| CNAME | — |
| NS | — |
| MX | — |
| TXT | — |
| 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.
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.
Learn more ▾ ▴
SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.
Source: RFC 7208 (SPF)
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencerivian.com — via Nom-iq Ltd. dba COM LAUDE, 28 years, 4 months old, hosted on AWSPASS
266 days
April 5, 2027
311 days
Issued by Amazon
28 years, 4 months
Registered April 6, 1998
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
3.165.190.79
Nom-iq Ltd. dba COM LAUDE
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
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