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
<!doctype html>
<html>
<head>
<title>Site Maintenance</title>
<style type="text/css">body { text-align: center; padding: 150px; }h1 { font-size: 40px; }body { font: 16px
Helvetica, sans-serif; color: #333; }#error { display: block; text-align: left; width: 650px; margin: 0 auto; }
</style>
</head>
<body>
<div id="error">
<h1>Oops! Something went wrong</h1>
<div>
<hr>
<p>Please contact your administrator with the error code: 0.8ad73b17.1776898490.579cb60a</p>
</div>
</div>
</body>
</html
BTLS Certificate Expiry & Recommendations232 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
- 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 Records2 A records, 137 ms lookupPASS
| A | 198.208.74.205, 198.208.73.147 |
| AAAA | — |
| CNAME | — |
| NS | nsx3.gm.com, nsx4.gm.com, nsx2.gm.com, nsx1.gm.com |
| MX | 10 chevrolet-com.mail.protection.outlook.com |
| TXT | _uqdcnylfpyx2cgotaae8bxk2f10cecm SPF v=spf1 mx include:_spf-a.gm.com include:_spf-b.gm.com include:spf.protection.out... 00DDn00000DCkt8MAD _zux2pth5au6csqj2djeapbezh6cjtel google-site-verification=9S9tK1dBuwipE9SOmt9mnKIZYcdLTFyVXH6e58mugk4 dtdl8mgrm9lw9xfhxr9v03zqnryx4542 _2v7ajttodprjkhb8wf9alrm6vyzgpw8 google-site-verification=Hle8WZ8JbOHYrt48fIz5OFxwUOgzaoMPIZgO3zIH4u8 atlassian-domain-verification=aaziLZUx/quz/UkqGaX57IZaDo2yc/yVsywalcZdjOcm5AQLpc... _ruu4l8kcygens0d25lmqd7ser3szp9a facebook-domain-verification=ved9sj8oeg9sez7791xrpm1nup4jf3 |
| 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), 728 ms totalPASS
https://chevrolet.com
605 ms · HTTP/1.0
https://www.chevrolet.com/
123 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://chevrolet.com | 301 | 605 ms | HTTP/1.0 | |
| 2 | https://www.chevrolet.com/ | 200 | 123 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 Intelligencechevrolet.com — via CSC Corporate Domains, Inc., 31 years, 9 months old, hosted on GENERAL-MOTORS-CORPORATION - General Motors LLC, USPASS
158 days
December 19, 2026
232 days
Issued by DigiCert Inc
31 years, 9 months
Registered December 20, 1994
Not enabled
Protects against DNS spoofing
GENERAL-MOTORS-CORPORATION - General Motors LLC, US
ASN AS30383
198.208.73.147
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