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
BTLS Certificate Expiry & Recommendations320 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
ADNS Records3 A records, 38 ms lookupPASS
| A | 52.43.133.118, 54.69.113.251, 54.148.77.250 |
| 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)
ARedirect Chain1 redirect(s), 777 ms totalPASS
https://www.twitch.com
711 ms · HTTP/1.1
https://www.twitch.tv:443/
66 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.twitch.com | 302 | 711 ms | HTTP/1.1 | awselb/2.0 |
| 2 | https://www.twitch.tv:443/ | 200 | 66 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
A+Crawlabilityrobots.txt present, sitemap with 8 URLsPASS
User-Agent: *
Allow: /
Allow: /directory
Allow: /directory/all
Allow: /directory/*
Allow: /.well-known/assetlinks.json
Disallow: /admin/*
Disallow: /email-unsubscribe/
Disallow: /login$
Disallow: /message/*
Disallow: /signup$
Disallow: /user/*
Disallow: /wv/*
Sitemap: https://www.twitch.tv/sitemapv2_index.xml.gz
- https://www.twitch.tv/sitemapv2_prod_v6_...
- https://www.twitch.tv/sitemapv2_prod_v6_...
- https://www.twitch.tv/sitemapv2_prod_v6_...
- https://www.twitch.tv/sitemapv2_prod_v6_...
- https://www.twitch.tv/sitemapv2_prod_v6_...
- https://www.twitch.tv/sitemapv2_prod_v6_...
- https://www.twitch.tv/sitemapv2_prod_v6_...
- https://www.twitch.tv/sitemapv2_prod_v6_...
AURL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: www
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
ADomain Intelligencetwitch.com — via MarkMonitor Inc., 29 years, 3 months old, hosted on AWSPASS
EXPIRED
May 27, 2026
320 days
Issued by Amazon
29 years, 3 months
Registered May 28, 1997
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
54.69.113.251
MarkMonitor Inc.
Expiry timeline
Recommended actions
- Domain has EXPIRED — renew immediately to avoid total site outage
- Enable DNSSEC to protect visitors from DNS spoofing
Consider enabling auto-renewal to prevent accidental expiration.
Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.
Source: ICANN renewal policy
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