Skip to content
https://xbox.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
95
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Singapore, Singapore
301 Moved Permanently
Checks
9
6 PASS 2 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
Redirect Chain
2 redirect(s), 604 ms total
REVIEW
2 redirect(s), 604 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Redirect overhead: 604 ms total
Got: 604 ms

https://xbox.com

506 ms · HTTP/1.1

301

https://www.xbox.com/

20 ms · HTTP/1.1

307

https://www.xbox.com/zh-TW/

78 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://xbox.com301506 msHTTP/1.1Kestrel
2https://www.xbox.com/30720 msHTTP/1.1
3https://www.xbox.com/zh-TW/20078 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

B
TLS Certificate Expiry & Recommendations
143 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

143
days left
0d 30d 60d 90d+

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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 Records
5 A records, 6 ms lookup
PASS
5 A records, 6 ms lookup
Info::
Resolves to 5 IPv4 address(es)
Got: 20.76.201.171, 20.70.246.20, 20.236.44.162, 20.112.250.133, 20.231.239.246
Info::
Has 5 IPv6 (AAAA) record(s)
Got: 2603:1030:c02:8::14, 2603:1030:b:3::152, 2603:1020:201:10::10f, 2603:1010:3:3::5b, 2603:1030:20e:3::23c
Info::
4 nameserver(s) configured
Got: ns1-205.azure-dns.com, ns2-205.azure-dns.net, ns3-205.azure-dns.org, ns4-205.azure-dns.info
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 6 ms
Got: 6 ms
A20.76.201.171, 20.70.246.20, 20.236.44.162, 20.112.250.133, 20.231.239.246
AAAA2603:1030:c02:8::14, 2603:1030:b:3::152, 2603:1020:201:10::10f, 2603:1010:3:3::5b, 2603:1030:20e:3::23c
CNAME—
NSns1-205.azure-dns.com, ns2-205.azure-dns.net, ns3-205.azure-dns.org, ns4-205.azure-dns.info
MX
10 xbox-com.mail.protection.outlook.com
TXT
b1939PPDAGDjXs+54riWGyuzfCM+s+PE66uPOHEQ+9z264YnfenE2CVrUxq+5UGTDqiOU8JqZ5AKRvfc...
google-site-verification=e70dJcpsqnXzda_PC9I_VO_bpU9hlMlqhtvsxegHEQc
facebook-domain-verification=n2md3enk4k9r4s6kylpqmekhxyyrq7
docusign=c2837ae3-ac1e-446d-b257-c2328dce901a
AFDVALIDATION=Xbox
adobe-idp-site-verification=8aa35c528af5d72beb19b1bd3ed9b86d87ea7f24b2ba3c99ffcd...
facebook-domain-verification=yvcz1zil7qv3biswf68ikkxkh1nsoh
google-site-verification=jRoICv0mMREqo5IthM1McDzE_8rRtEYtSVtHmOTUoJA
SPF v=spf1 ip4:65.55.42.0/24 ip4:65.55.76.0/24 mx:xbox.com include:_spf-ssg-a.micros...
CAALookup not available with standard resolver
Resolved in 6 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
IPv6 Readiness
IPv6 reachable (162 ms)
PASS
IPv6 reachable (162 ms)
Info::
IPv6 is configured and reachable at 2603:1030:c02:8::14, 2603:1030:b:3::152, 2603:1020:201:10::10f, 2603:1010:3:3::5b, 2603:1030:20e:3::23c
Got: 162 ms connect
IPv6 Ready
AAAA Records 2603:1030:c02:8::14, 2603:1030:b:3::152, 2603:1020:201:10::10f, 2603:1010:3:3::5b, 2603:1030:20e:3::23c Connection Reachable (162 ms)
A+
Crawlability
robots.txt present, sitemap with 464 URLs
PASS
robots.txt present, sitemap with 464 URLs
Info::
robots.txt is present
Got: 289 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 464 entries
Info::
Sitemap index with 464 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 289 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /error

Disallow: /*Search?q*

Disallow: /*search?q*

Disallow: /*results?k*

Disallow: /*Results?k*

Disallow: /_layouts/

Disallow: /_vti_bin/

Disallow: /*/contact-us?isChatCallAvailable=false

Disallow: /*/play/user/*

Sitemap: https://www.xbox.com/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 464 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

307https://www.xbox.com/
200https://xbox.com/

HTTP → HTTPS

301http://xbox.com/ → https://www.xbox.com/

Consistent

A+
Domain Intelligence
xbox.com — via CSC Corporate Domains, Inc., 29 years, 9 months old
PASS
xbox.com — via CSC Corporate Domains, Inc., 29 years, 9 months old
Info::
Domain registered until Dec 17, 2026 (8 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: CSC Corporate Domains, Inc.
Warning::
Registrar lock is NOT enabled
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.
Domain expiry

184 days

December 17, 2026

SSL certificate

143 days

Issued by Microsoft Corporation

Domain age

29 years, 9 months

Registered December 18, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2603:1030:b:3::152

Registrar

CSC Corporate Domains, Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar CSC Corporate Domains, Inc.
Created December 18, 1996 (29 years, 9 months ago)
Expires December 17, 2026 (8 months)
Last Updated December 14, 2025
Name Servers ns1-205.azure-dns.com, ns2-205.azure-dns.net, ns3-205.azure-dns.org, ns4-205.azure-dns.info
DNSSEC Not enabled
Hosting
IP Address 2603:1030:b:3::152
Data source: rdap (0.6s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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.

Why this matters

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

A
HTTP Probe Timing
Total 518 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
4 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
169 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
175 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
518 ms
Total Time Total request time from DNS lookup through full response.
518 ms

Connection waterfall

DNS Lookup 4 ms TCP Connect 169 ms TLS Handshake 175 ms Server Processing 170 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback