Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FRedirect ChainAction5 redirect(s), 523 ms totalFIX
https://battle.net
352 ms · HTTP/1.1
https://shop.battle.net?from=root
73 ms · HTTP/1.1
https://eu.shop.battle.net/?from=root
35 ms · HTTP/1.1
https://eu.shop.battle.net/oauth2/author...
11 ms · HTTP/1.1
https://oauth.battle.net/authorize?respo...
37 ms · HTTP/1.1
https://eu.shop.battle.net/login/oauth2/...
14 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://battle.net | 301 | 352 ms | HTTP/1.1 | Apache |
| 2 | https://shop.battle.net?from=root | 302 | 73 ms | HTTP/1.1 | Apache |
| 3 | https://eu.shop.battle.net/?from=root | 302 | 35 ms | HTTP/1.1 | |
| 4 | https://eu.shop.battle.net/oauth2/author... | 302 | 11 ms | HTTP/1.1 | |
| 5 | https://oauth.battle.net/authorize?respo... | 302 | 37 ms | HTTP/1.1 | |
| 6 | https://eu.shop.battle.net/login/oauth2/... | 401 | 14 ms | HTTP/1.1 |
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.
BTLS Certificate Expiry & Recommendations167 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 Records2 A records, 278 ms lookupPASS
| A | 166.117.134.156, 166.117.30.132 |
| AAAA | — |
| CNAME | — |
| NS | ns-1467.awsdns-55.org, ns-1578.awsdns-05.co.uk, ns-599.awsdns-10.net, ns-67.awsdns-08.com |
| MX | 0 mxb-00381101.gslb.pphosted.com 0 mxa-00381101.gslb.pphosted.com |
| TXT | FHtwAyldtP/7jq5sT93uP2GW7/yWbSKfgD2O/6VU1IwZMpWYTGOpGtjGDCj/JeKWYIJyS90KgprRKqgw... MS=ms91053870 _kbwwqmmqtaqzwtwwf3r119kao42ajjd facebook-domain-verification=wr9qqtrkyp1jejv1xr8blfn6dpowbt google-site-verification=5BDURW3z5Ld2Mi_LkCm21d23wHRx9_hqokrh1C68duo google-site-verification=XMBo5g8gfzfd_6yHrk6AD2rMT_1RxWg6j44Zsyuy1yM SPF v=spf1 include:spf1.battle.net include:spf2.battle.net include:spf3.battle.net i... |
| 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+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencebattle.net — via MarkMonitor Inc., 30 years, 6 months old, hosted on AWSPASS
1712 days
March 27, 2031
167 days
Issued by Amazon
30 years, 6 months
Registered March 26, 1996
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
166.117.134.156
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