Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FRedirect ChainAction4 redirect(s), 2964 ms totalFIX
https://blizzard.com
384 ms · HTTP/1.1
https://sea.blizzard.com/
973 ms · HTTP/1.1
https://us.blizzard.com/
1062 ms · HTTP/1.1
https://www.blizzard.com/
316 ms · HTTP/1.1
https://www.blizzard.com/en-us/
229 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://blizzard.com | 302 | 384 ms | HTTP/1.1 | Apache |
| 2 | https://sea.blizzard.com/ | 301 | 973 ms | HTTP/1.1 | Apache |
| 3 | https://us.blizzard.com/ | 301 | 1062 ms | HTTP/1.1 | Apache |
| 4 | https://www.blizzard.com/ | 307 | 316 ms | HTTP/1.1 | nginx |
| 5 | https://www.blizzard.com/en-us/ | 200 | 229 ms | HTTP/1.1 | nginx |
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
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
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.
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
HTTP → HTTPS
HTTP version does not redirect to HTTPS
BTLS Certificate Expiry & Recommendations184 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 Records4 A records, 589 ms lookupPASS
| A | 166.117.48.155, 166.117.103.183, 99.83.192.184, 166.117.198.189 |
| AAAA | — |
| CNAME | — |
| NS | ns-1095.awsdns-08.org, ns-1691.awsdns-19.co.uk, ns-378.awsdns-47.com, ns-773.awsdns-32.net |
| MX | 0 mxa-00381101.gslb.pphosted.com 0 mxb-00381101.gslb.pphosted.com |
| TXT | 9ast9q6drcirg8pi7k676eoetv MS=ms31706595 MS=ms57970108 ZOOM_verify_hFv9VzxTRgymAdA5pF1Krg _1ffb0v1hbuwrylmch2qwgvyahnoop8y adobe-idp-site-verification=a7a94c669ae11c2259c9fbbd794babb872ffebb9affa731d263b... adobe-sign-verification=94d1e6f5235b1641d50e4d4e8b34fcdc apple-domain-verification=o4oNmfOLCrwVWtrS atlassian-domain-verification=zgWQpzQViZLGaYL2GIW7hKWpr6aAZhVzDaB9pQMftfYI28JPsa... autodesk-domain-verification=0tRCxSswuxIoiqeib9t9 docker-verification=497cc8e0-e420-4776-a0b0-d7fbbc11e5c8 docker-verification=b12f286b-bd43-4b54-a6ca-4be4b58b3922 docusign=ee8255b5-38e2-4297-b5ef-a6bb3e0505e7 facebook-domain-verification=l729zjxb4u0q1pbym3kxkwghuudn5f gather-domain-verification=237057f9-e333-4a58-b15c-0fd742b986af google-site-verification=LQ2nsdsg-oTZXpoS8YnmK2FvFnB_lL-Sh8NF6ft-sHk google-site-verification=Z-JQSYgRHVwUSud5A5E1OMlOeHcj8CdyVkgtlDk3wVo google-site-verification=g3dU2v72gpIA-zCPlbyQ5rLYJJZRkjt3A0Bbdvt8HUQ google-site-verification=s8_eBmRQXEbicVQBwk_mk4hGcOccQ9VbAvnt_11pFb0 gpmmx11kdqr2kjxdqszmj8x8bnx19f65 intersight=e82a08b44f30cab9769fec8b5413d05b60c4607b7e00ef0470ae1bdc32e9d68a jamf-site-verification=GSBqZVNDf4Ui336yhZ5-tw jetbrains-domain-verification=dydj30yj8fk2mr1kuylyt7y9u klaviyo-site-verification=RB6eMp klaviyo-site-verification=RfRHgX klaviyo-site-verification=S7PgSv miro-verification=6755f39b303e499cae6007b1e5d7b2b01504a40c new-relic-domain-verification=47bdcf4d7132446781d8df3d606207ed onetrust-domain-verification=896cdf8e3f5c4a70884c60ff86cefcd1 openai-domain-verification=dv-DYguSNGwsNq65c5fYVRxQTV1 parsec-domain-verification=td_2Ptk7s4u5pSU3rxnq1rAEfVImcx pexip-ms-tenant-domain-verification=e26751a3-fe48-4825-bc2f-a50cbd21a69c sprout-social-676bbea9-a211-43ad-9f20-6d12699f20dd SPF v=spf1 include:spfa.blizzard.com -all wrike-verification=NTE0ODg1ODphOWUzODZmNzcwMGEzNWRkZjRiNTMxYTBlMzVkOTliMTcxM2U0Z... xh9NRkZxUFvgv5XAaFWgjJRaa7fsNY7VCfIED64fJgurgPhf/eZiu03JJXjZiNHJX/VLw4i/BGMricwB... |
| 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.
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
A+Domain Intelligenceblizzard.com — via MarkMonitor Inc., 31 years, 9 months old, hosted on AWSPASS
2336 days
December 8, 2032
184 days
Issued by Amazon
31 years, 9 months
Registered December 9, 1994
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
166.117.30.132
MarkMonitor 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