live.com

Checked 22 October 2026, 09:40 UTC · via 8.8.8.8
!Passed with warnings
29 passed 2 warnings 0 failed 3 info

Registration

info

.com generic · CSC Corporate Domains, Inc. · expires 2026-12-27

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
CSC Corporate Domains, Inc.
Registered
28 December 1994
Last changed
1 May 2026
Expires
27 December 2026
Status
client delete prohibited, client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited
Registry nameservers
ns1-37.azure-dns.com, ns2-37.azure-dns.net, ns3-37.azure-dns.org, ns4-37.azure-dns.info
RDAP server
https://rdap.verisign.com/com/v1/

Checks

  • i
    .com is a generic TLD (gTLD)
    Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2026-12-27 #3
    The registration is valid until 2026-12-27 (65 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

ns1-37.azure-dns.com, ns2-37.azure-dns.net, ns3-37.azure-dns.org, ns4-37.azure-dns.info

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1-37.azure-dns.com, ns2-37.azure-dns.net, ns3-37.azure-dns.org, ns4-37.azure-dns.info
NS in the zone
ns1-37.azure-dns.com, ns2-37.azure-dns.net, ns3-37.azure-dns.org, ns4-37.azure-dns.info
NameserverAddressesNetwork (AS)Glue
ns1-37.azure-dns.com150.171.10.37 2603:1061:0:10::25AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US150.171.10.37 2603:1061:0:10::25
ns2-37.azure-dns.net150.171.16.37 2620:1ec:8ec:10::25AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns3-37.azure-dns.org13.107.222.37 2a01:111:4000:10::25AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns4-37.azure-dns.info13.107.206.37 2620:1ec:bda:10::25AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1-37.azure-dns.com, ns2-37.azure-dns.net, ns3-37.azure-dns.org, ns4-37.azure-dns.info.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 4 IPv4 /24s and 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US): 8 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • ✓ Nameserver names under 4 TLDs #12
    Nameserver names use the TLDs .com, .info, .net, .org.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1-37.azure-dns.com 150.171.10.37NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns1-37.azure-dns.com 2603:1061:0:10::25NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns2-37.azure-dns.net 150.171.16.37NOERROR, 13 ms, authoritativenoyes / yesrefusedKnot DNS 3.1.2.1770717641.d6b376aff
ns2-37.azure-dns.net 2620:1ec:8ec:10::25NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-37.azure-dns.org 13.107.222.37NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns3-37.azure-dns.org 2a01:111:4000:10::25NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns4-37.azure-dns.info 13.107.206.37NOERROR, 4 ms, authoritativenoyes / yesrefusedKnot DNS 3.1.2.1770717641.d6b376aff
ns4-37.azure-dns.info 2620:1ec:bda:10::25NOERROR, 5 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 8 nameserver addresses answered.
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns2-37.azure-dns.net: "Knot DNS 3.1.2.1770717641.d6b376aff"; ns4-37.azure-dns.info: "Knot DNS 3.1.2.1770717641.d6b376aff". Hide or replace the version string.
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 2017971531 · primary ns1-37.azure-dns.com

Found

Primary (MNAME)
ns1-37.azure-dns.com
Contact (RNAME)
msnhst.microsoft.com
Serial
2017971531
Refresh / retry
300 s / 120 s
Expire
2419200 s
Negative TTL
60 s

Serial per nameserver

NameserverSerial
ns1-37.azure-dns.com (150.171.10.37)2017971531
ns1-37.azure-dns.com (2603:1061:0:10::25)2017971531
ns2-37.azure-dns.net (150.171.16.37)2017971531
ns2-37.azure-dns.net (2620:1ec:8ec:10::25)2017971531
ns3-37.azure-dns.org (13.107.222.37)2017971531
ns3-37.azure-dns.org (2a01:111:4000:10::25)2017971531
ns4-37.azure-dns.info (13.107.206.37)2017971531
ns4-37.azure-dns.info (2620:1ec:bda:10::25)2017971531

Checks

  • ✓ Serial 2017971531 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 5m is outside 20m–1d; negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 5m, retry 2m, expire 28d, negative TTL 1m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1-37.azure-dns.com is one of the listed nameservers.
  • ✓ Contact msnhst@microsoft.com #25
    The SOA RNAME msnhst.microsoft.com means msnhst@microsoft.com.
  • ✓ Timestamp serial #26
    The serial 2017971531 is a Unix timestamp (2033-12-12 03:38 UTC).

DNSSEC

pass

Signed, DS published at parent

Found

Validated by resolver
yes
Signatures valid until
23 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
28654ECDSAP256SHA256 (13)SHA256 71026DFAAF7A081B…yes

DNSKEY in the zone

Key tagRoleAlgorithm
28654KSK (257)ECDSAP256SHA256 (13)
44331ZSK (256)ECDSAP256SHA256 (13)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 28654 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Short-lived signatures (online signing) #30
    Signatures are valid for 50h0m0s and created on demand; the current one was made at 2026-10-21 08:38 UTC and expires at 2026-10-23 10:38 UTC.

Records

info

21 records at the apex

Found

Read from
150.171.10.37:53
TypeValueTTL
SOAns1-37.azure-dns.com. msnhst.microsoft.com. 2017971531 300 120 2419200 6060
NSns1-37.azure-dns.com.300
NSns2-37.azure-dns.net.300
NSns3-37.azure-dns.org.300
NSns4-37.azure-dns.info.300
A204.79.197.2123600
MX2 live-com.olc.protection.outlook.com.3600
TXT"google-site-verification=N9kowue62gCm511Op0_N2LO1JZTcjA2GYzOE22SBaiI"300
TXT"v=spf1 include:spf-a.hotmail.com include:spf-b.hotmail.com include:spf-c.hotmail.com include:spf-d.hotmail.com include:spf.protection.outlook.com ~all"300
TXT"facebook-domain-verification=atvthxwtzc3u4ubnsozavn76cusuaj"300
TXT"google-site-verification=0mLTLcpaFxdFNO4m1TfqB2WQ4rGtz7xpPmFwDJ9O_9Q"300
TXT"google-site-verification=DVGpQUbbQCBRPGlmWiTVUMyQGfLPlEVw6Z4pm39AAj4"300
TXT"google-site-verification=er-XGn5evjhwRiwIPwWyQjyHB1pigvhw-mp8saZxLCA"300
TXT"google-site-verification=aqgIxrIS1nghF9FDjR5tN7t6xgIVr3Dg254rmyDNwRU"300
CAA0 iodef "mailto:domains@microsoft.com"300
CAA0 issue "entrust.net"300
CAA0 issue "digicert.com"300
CAA0 issue "globalsign.com"300
CAA0 issue "microsoft.com"300
CAA0 issue "dtrust.de"300
CAA0 contactemail "caarecordaware@microsoft.com"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, MX 1h, NS 5m. The NS TTL at the parent is 2d and in the zone 5m; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: entrust.net, digicert.com, globalsign.com, microsoft.com, dtrust.de.