msn.com

Checked 22 October 2026, 09:53 UTC · via 8.8.8.8
!Passed with warnings
25 passed 4 warnings 0 failed 2 info

Registration

info

.com generic · MarkMonitor Inc. · expires 2027-06-04

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
MarkMonitor Inc.
Registered
10 November 1994
Last changed
3 May 2026
Expires
4 June 2027
Status
client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited
Registry nameservers
dns1.p09.nsone.net, ns1-204.azure-dns.com, ns2-204.azure-dns.net, ns3-204.azure-dns.org, ns4-204.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 2027-06-04 #3
    The registration is valid until 2027-06-04 (225 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client transfer prohibited, client update 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

warn

dns1.p09.nsone.net, ns1-204.azure-dns.com, ns2-204.azure-dns.net, ns3-204.azure-dns.org, ns4-204.azure-dns.info

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
dns1.p09.nsone.net, ns1-204.azure-dns.com, ns2-204.azure-dns.net, ns3-204.azure-dns.org, ns4-204.azure-dns.info
NS in the zone
dns1.p08.nsone.net, dns2.p08.nsone.net, dns3.p08.nsone.net, dns4.p08.nsone.net, ns1-204.azure-dns.com, ns2-204.azure-dns.net, ns3-204.azure-dns.org, ns4-204.azure-dns.info
NameserverAddressesNetwork (AS)Glue
dns1.p08.nsone.net (zone only)198.51.44.8 2620:4d:4000:6259:7:8:0:1AS62597 NSONE - NSONE Inc, US AS62597 NSONE - NSONE Inc, US-
dns1.p09.nsone.net (parent only)198.51.44.9 2620:4d:4000:6259:7:9:0:1AS62597 NSONE - NSONE Inc, US AS62597 NSONE - NSONE Inc, US-
dns2.p08.nsone.net (zone only)198.51.45.8 2a00:edc0:6259:7:8::2AS62597 NSONE - NSONE Inc, US AS62597 NSONE - NSONE Inc, US-
dns3.p08.nsone.net (zone only)198.51.44.72 2620:4d:4000:6259:7:8:0:3AS62597 NSONE - NSONE Inc, US AS62597 NSONE - NSONE Inc, US-
dns4.p08.nsone.net (zone only)198.51.45.72 2a00:edc0:6259:7:8::4AS62597 NSONE - NSONE Inc, US AS62597 NSONE - NSONE Inc, US-
ns1-204.azure-dns.com13.107.236.204 2603:1061:0:700::ccAS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US13.107.236.204 2603:1061:0:700::cc
ns2-204.azure-dns.net150.171.21.204 2620:1ec:8ec:700::ccAS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns3-204.azure-dns.org204.14.183.204 2a01:111:4000:700::ccAS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns4-204.azure-dns.info208.84.5.204 2620:1ec:bda:700::ccAS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-

Checks

  • ✓ 5 nameservers #6
    Delegated to dns1.p09.nsone.net, ns1-204.azure-dns.com, ns2-204.azure-dns.net, ns3-204.azure-dns.org, ns4-204.azure-dns.info.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: dns1.p09.nsone.net; only in the zone: dns1.p08.nsone.net, dns2.p08.nsone.net, dns3.p08.nsone.net, dns4.p08.nsone.net. dns1.p08.nsone.net, dns1.p09.nsone.net, dns2.p08.nsone.net, dns3.p08.nsone.net, dns4.p08.nsone.net, ns1-204.azure-dns.com, ns2-204.azure-dns.net, ns3-204.azure-dns.org, ns4-204.azure-dns.info report NS dns1.p08.nsone.net dns2.p08.nsone.net dns3.p08.nsone.net dns4.p08.nsone.net ns1-204.azure-dns.com ns2-204.azure-dns.net ns3-204.azure-dns.org ns4-204.azure-dns.info.
    #7
  • ✓ 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 6 IPv4 /24s and 6 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS62597 (NSONE - NSONE Inc, US): 10 addresses; AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US): 8 addresses.
  • ✓ 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

18 of 18 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns1.p08.nsone.net 198.51.44.8NOERROR, 7 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
dns1.p08.nsone.net 2620:4d:4000:6259:7:8:0:1NOERROR, 6 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
dns1.p09.nsone.net 198.51.44.9NOERROR, 4 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
dns1.p09.nsone.net 2620:4d:4000:6259:7:9:0:1NOERROR, 7 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
dns2.p08.nsone.net 198.51.45.8NOERROR, 4 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
dns2.p08.nsone.net 2a00:edc0:6259:7:8::2NOERROR, 5 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
dns3.p08.nsone.net 198.51.44.72NOERROR, 5 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
dns3.p08.nsone.net 2620:4d:4000:6259:7:8:0:3NOERROR, 5 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
dns4.p08.nsone.net 198.51.45.72NOERROR, 4 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
dns4.p08.nsone.net 2a00:edc0:6259:7:8::4NOERROR, 4 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
ns1-204.azure-dns.com 13.107.236.204NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1-204.azure-dns.com 2603:1061:0:700::ccNOERROR, 5 ms, authoritativenoyes / yesrefused-
ns2-204.azure-dns.net 150.171.21.204NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns2-204.azure-dns.net 2620:1ec:8ec:700::ccNOERROR, 5 ms, authoritativenoyes / yesrefused-
ns3-204.azure-dns.org 204.14.183.204NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns3-204.azure-dns.org 2a01:111:4000:700::ccNOERROR, 5 ms, authoritativenoyes / yesrefused-
ns4-204.azure-dns.info 208.84.5.204NOERROR, 4 ms, authoritativenoyes / yesrefusedKnot DNS 3.1.2.1770717641.d6b376aff
ns4-204.azure-dns.info 2620:1ec:bda:700::ccNOERROR, 5 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 18 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: ns4-204.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 1654633312 · primary dns1.p09.nsone.net

Found

Primary (MNAME)
dns1.p09.nsone.net
Contact (RNAME)
hostmaster.nsone.net
Serial
1654633312
Refresh / retry
86400 s / 7200 s
Expire
2419200 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
dns1.p08.nsone.net (198.51.44.8)1654633312
dns1.p08.nsone.net (2620:4d:4000:6259:7:8:0:1)1654633312
dns1.p09.nsone.net (198.51.44.9)1654633312
dns1.p09.nsone.net (2620:4d:4000:6259:7:9:0:1)1654633312
dns2.p08.nsone.net (198.51.45.8)1654633312
dns2.p08.nsone.net (2a00:edc0:6259:7:8::2)1654633312
dns3.p08.nsone.net (198.51.44.72)1654633312
dns3.p08.nsone.net (2620:4d:4000:6259:7:8:0:3)1654633312
dns4.p08.nsone.net (198.51.45.72)1654633312
dns4.p08.nsone.net (2a00:edc0:6259:7:8::4)1654633312
ns1-204.azure-dns.com (13.107.236.204)1
ns1-204.azure-dns.com (2603:1061:0:700::cc)1
ns2-204.azure-dns.net (150.171.21.204)1
ns2-204.azure-dns.net (2620:1ec:8ec:700::cc)1
ns3-204.azure-dns.org (204.14.183.204)1
ns3-204.azure-dns.org (2a01:111:4000:700::cc)1
ns4-204.azure-dns.info (208.84.5.204)1
ns4-204.azure-dns.info (2620:1ec:bda:700::cc)1

Checks

  • !
    Serials differ
    The nameservers serve different versions of the zone: 1 on ns1-204.azure-dns.com (13.107.236.204), ns1-204.azure-dns.com (2603:1061:0:700::cc), ns2-204.azure-dns.net (150.171.21.204), ns2-204.azure-dns.net (2620:1ec:8ec:700::cc), ns3-204.azure-dns.org (204.14.183.204), ns3-204.azure-dns.org (2a01:111:4000:700::cc), ns4-204.azure-dns.info (208.84.5.204), ns4-204.azure-dns.info (2620:1ec:bda:700::cc); 1654633312 on dns1.p08.nsone.net (198.51.44.8), dns1.p08.nsone.net (2620:4d:4000:6259:7:8:0:1), dns1.p09.nsone.net (198.51.44.9), dns1.p09.nsone.net (2620:4d:4000:6259:7:9:0:1), dns2.p08.nsone.net (198.51.45.8), dns2.p08.nsone.net (2a00:edc0:6259:7:8::2), dns3.p08.nsone.net (198.51.44.72), dns3.p08.nsone.net (2620:4d:4000:6259:7:8:0:3), dns4.p08.nsone.net (198.51.45.72), dns4.p08.nsone.net (2a00:edc0:6259:7:8::4). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 2h, expire 28d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns1.p09.nsone.net is one of the listed nameservers.
  • ✓ Contact hostmaster@nsone.net #25
    The SOA RNAME hostmaster.nsone.net means hostmaster@nsone.net.
  • ✓ Timestamp serial #26
    The serial 1654633312 is a Unix timestamp (2022-06-07 20:21 UTC).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Records

info

21 records at the apex

Found

Read from
198.51.44.8:53
TypeValueTTL
SOAdns1.p09.nsone.net. hostmaster.nsone.net. 1654633312 86400 7200 2419200 36003600
NSns4-204.azure-dns.info.86400
NSns3-204.azure-dns.org.86400
NSns2-204.azure-dns.net.86400
NSns1-204.azure-dns.com.86400
NSdns1.p08.nsone.net.86400
NSdns2.p08.nsone.net.86400
NSdns3.p08.nsone.net.86400
NSdns4.p08.nsone.net.86400
A204.79.197.2193600
MX2 msn-com.olc.protection.outlook.com.3600
TXT"AFDVALIDATION=IcePrime"3600
TXT"facebook-domain-verification=q715hqwb3sc3mkxajcokcksu21c8r2"3600
TXT"globalsign-domain-verification=KaParXxs1OHDy7o8CMbPpHBN-2m_mzwdPqKMMQ66a6"3600
TXT"google-site-verification=3lJkn9Ti3ZZZEzyGfgndcatwCZ93RLqWOYjIckfeKlM"3600
TXT"google-site-verification=snWRecgPSoBabrLXKCz4W8SZYabue7JrtXQM36fq6PE"3600
TXT"v=spf1 include:spf.protection.outlook.com include:spf-a.hotmail.com include:spf-b.hotmail.com include:spf-c.hotmail.com include:spf-d.hotmail.com include:_spf-ssg-a.microsoft.com ~all"3600
CAA0 contactemail "caarecordaware@microsoft.com"3600
CAA0 issue "digicert.com"3600
CAA0 issue "globalsign.com"3600
CAA0 issue "microsoft.com"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, MX 1h, NS 1d. The NS TTL at the parent is 2d and in the zone 1d; 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: digicert.com, globalsign.com, microsoft.com.