DNS Spy
Connectivity: 100%
The following nameservers are available and responding correctly for DNS queries for your domain xboxlive.com.
| Nameserver | IP address(es) | SOA serial |
|---|---|---|
| ns1-205.azure-dns.com. |
40.90.4.205
2603:1061:0:700::cd |
1 |
| ns2-205.azure-dns.net. |
64.4.48.205
2620:1ec:8ec:700::cd |
1 |
| ns3-205.azure-dns.org. |
13.107.24.205
2a01:111:4000:700::cd |
1 |
| ns4-205.azure-dns.info. |
13.107.160.205
2620:1ec:bda:700::cd |
1 |
Good news, no warnings or errors were found.
We could not find any recommendations at this time.
Good news, we detected the following achievements in your DNS configuration. Each of these checks has increased your DNS Spy score.
- All nameservers reply with the same SOA serial number.
- The nameserver IPs are distributed across multiple subnets.
- All nameservers are online.
- Nameservers are available over IPv4.
- Nameservers are available over IPv6.
Performance: 100%
We tested each nameserver and measured the following response times.
| Nameserver | IP address(es) | Response time |
|---|---|---|
| ns1-205.azure-dns.com. |
40.90.4.205
2603:1061:0:700::cd |
35ms
27ms |
| ns2-205.azure-dns.net. |
64.4.48.205
2620:1ec:8ec:700::cd |
39ms
19ms |
| ns3-205.azure-dns.org. |
13.107.24.205
2a01:111:4000:700::cd |
51ms
19ms |
| ns4-205.azure-dns.info. |
13.107.160.205
2620:1ec:bda:700::cd |
31ms
27ms |
Good news, no warnings or errors were found.
We detected some possible recommendations for you to consider. No penalties were given for these, but resolving them can give you a higher DNS score.
- Nameserver ns3-205.azure-dns.org. (13.107.24.205) replied reasonably fast (< 150ms), but you should aim for < 50ms response times.
Good news, we detected the following achievements in your DNS configuration. Each of these checks has increased your DNS Spy score.
- Nameserver ns1-205.azure-dns.com. (40.90.4.205) replied quickly (< 50ms).
- Nameserver ns1-205.azure-dns.com. (2603:1061:0:700::cd) replied in a reasonable time.
- Nameserver ns2-205.azure-dns.net. (64.4.48.205) replied quickly (< 50ms).
- Nameserver ns2-205.azure-dns.net. (2620:1ec:8ec:700::cd) replied in a reasonable time.
- Nameserver ns3-205.azure-dns.org. (2a01:111:4000:700::cd) replied in a reasonable time.
- Nameserver ns4-205.azure-dns.info. (13.107.160.205) replied quickly (< 50ms).
- Nameserver ns4-205.azure-dns.info. (2620:1ec:bda:700::cd) replied in a reasonable time.
Resilience & Security: 67%
These are the locations and providers of your nameservers.
| Nameserver | Location | ISP |
|---|---|---|
| ns1-205.azure-dns.com. |
IPv4: US
IPv6: US |
AS8068 - MICROSOFT-CORP-MSN-AS-BLOCK, US
AS8075 - MICROSOFT-CORP-MSN-AS-BLOCK, US |
| ns2-205.azure-dns.net. |
IPv4: US
IPv6: US |
AS8075 - MICROSOFT-CORP-MSN-AS-BLOCK, US
AS8075 - MICROSOFT-CORP-MSN-AS-BLOCK, US |
| ns3-205.azure-dns.org. |
IPv4: US
IPv6: GB |
AS8068 - MICROSOFT-CORP-MSN-AS-BLOCK, US
AS8075 - MICROSOFT-CORP-MSN-AS-BLOCK, US |
| ns4-205.azure-dns.info. |
IPv4: US
IPv6: US |
AS8068 - MICROSOFT-CORP-MSN-AS-BLOCK, US
AS8075 - MICROSOFT-CORP-MSN-AS-BLOCK, US |
We detected the following errors or warnings about your DNS configuration. These caused your DNS rating to be lowered. Resolving these will grant a higher DNS Spy rating for your domain.
- All IPv6 nameservers are hosted by the same provider (AS8075 - MICROSOFT-CORP-MSN-AS-BLOCK, US). Consider spreading the nameservers across multiple DNS providers for increased redundancy.
- No DNSSEC records found. Consider enabling DNSSEC, as it provides a way to validate DNS responses for data integrity.
We detected some possible recommendations for you to consider. No penalties were given for these, but resolving them can give you a higher DNS score.
- All IPv4 nameservers appear to be hosted in the same country (US). You might want to consider spreading the nameservers geographically.
- No CAA records found. Consider adding CAA records, as it adds increased security by limiting which Certificate Authorities can issue certificates for this domain. (more info)
Good news, we detected the following achievements in your DNS configuration. Each of these checks has increased your DNS Spy score.
- You have more than 1 nameserver.
- The IPv4 nameservers are distributed among multiple providers.
- The IPv6 nameservers are distributed across multiple locations.
- The nameservers are being operated from multiple domains (azure-dns.com, azure-dns.net, azure-dns.org, azure-dns.info).
DNS records: 100%
Our scans detected the following publicly available DNS records.
| Record | TTL | Value | |
|---|---|---|---|
| A | xboxlive.com | 1h |
20.103.85.33 20.112.52.29 20.53.203.50 20.81.111.85 20.84.181.62 |
| NS | xboxlive.com | 172800s |
ns1-205.azure-dns.com. ns2-205.azure-dns.net. ns3-205.azure-dns.org. ns4-205.azure-dns.info. |
| SOA | xboxlive.com | 1h | ns1-205.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 300 |
| TXT | xboxlive.com | 1h | "v=spf1 include:_spf-ssg-a.microsoft.com -all" |
| CNAME | auth.xboxlive.com | 1h | auth360.trafficmanager.net. |
| CNAME | chat.xboxlive.com | 1h | chat.xboxlive.com.akadns.net. |
| CNAME | download.xboxlive.com | 1h | download.xboxlive.com.edgesuite.net. |
| A | forum.xboxlive.com | 1h | 157.55.114.186 |
| CNAME | stats.xboxlive.com | 1h | stats.trafficmanager.net. |
| CNAME | upload.xboxlive.com | 1h | fileupload.trafficmanager.net. |
| CNAME | www.xboxlive.com | 1h | xboxlive.com. |
Good news, no warnings or errors were found.
We detected some possible recommendations for you to consider. No penalties were given for these, but resolving them can give you a higher DNS score.
- No DMARC records have been found. Consider configuring DMARC for improved e-mail authentication.
- No IPv6 record has been found on the zone apex (xboxlive.com). Consider enabling IPv6 in the infrastructure by adding an AAAA record on this domain.
Good news, we detected the following achievements in your DNS configuration. Each of these checks has increased your DNS Spy score.
- The root DNS records points to multiple IPs using Round Robin.
- The NS records have a long TTL (1h+).
- SPF records have been found.
- SPF records are set up restrictively.
- Found a root (apex) DNS record.
- Found a www DNS record.
- The active nameservers match the NS records.
- The DNS records appear to be RFC compliant.
Have a look at other public DNS scans.