Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.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.
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
HTTP → HTTPS
HTTP version does not redirect to HTTPS
BTLS Certificate Expiry & Recommendations74 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
BCDN & DeliveryAkamaiREVIEW
A+DNS Records2 A records, 36 ms lookupPASS
| A | 2.17.112.13, 2.17.112.39 |
| AAAA | 2a02:26f0:2380:d::211:7049, 2a02:26f0:2380:d::211:705d |
| CNAME | — |
| NS | a9-66.akam.net, a1-127.akam.net, a13-67.akam.net, a18-64.akam.net, a28-65.akam.net, a12-66.akam.net |
| MX | 1 aspmx.l.google.com 5 alt1.aspx.l.google.com 5 alt2.aspmx.l.google.com 10 aspmx2.googlemail.com 10 aspmx3.googlemail.com |
| TXT | google-site-verification=q9DUzemhBxxc345W41MPTn3fzRuQaID_5R4GLRSgl80 google-site-verification=291PSk69uu3M3SOrPTBsYGz8yvl16K1ZhbP6YMQytxU google-site-verification=3qYuZ0m5YJdjmVslnraXZKQtXmO_3YI9wv6nCY1CPHM google-site-verification=4WbE24gb_6cUVXrWnFJ__9_I6dzVBEhlIAQvtZdA97U SPF v=spf1 include:_spf.google.com include:mail.zendesk.com ip4:208.72.12.43 ip4:208... google-site-verification=GohBbB11BuN1VTA3oFWu3tmiM_pM4Bw_nzKAonQmDb8 google-site-verification=ave4Otl9BlVJ0Zd2j4GVdJ4s4brlgM3fqPZ-_mM6EFY |
| 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.
A+Redirect Chain0 redirect(s), 14 ms totalPASS
https://starwars.com
14 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://starwars.com | 403 | 14 ms | HTTP/1.1 | AkamaiGHost |
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+Domain Intelligencestarwars.com — via CSC Corporate Domains, Inc., 30 years oldPASS
47 days
September 3, 2026
74 days
Issued by Let's Encrypt
30 years
Registered September 4, 1996
Not enabled
Protects against DNS spoofing
Unknown
2a02:26f0:2380:d::211:7049
CSC Corporate Domains, Inc.
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- 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