zacks.com

Checked 22 October 2026, 11:42 UTC · via 8.8.8.8
!Passed with warnings
30 passed 1 warning 0 failed 4 info

Registration

warn

.com generic · GoDaddy.com, LLC · expires 2026-11-08

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
GoDaddy.com, LLC
Registered
9 November 1994
Last changed
27 March 2026
Expires
8 November 2026
Status
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
Registry nameservers
ns1-09.azure-dns.com, ns2-09.azure-dns.net, ns3-09.azure-dns.org, ns4-09.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 in 16 days
    The registration expires on 2026-11-08. Make sure it is renewed.
    #3
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

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

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1-09.azure-dns.com, ns2-09.azure-dns.net, ns3-09.azure-dns.org, ns4-09.azure-dns.info
NS in the zone
ns1-09.azure-dns.com, ns2-09.azure-dns.net, ns3-09.azure-dns.org, ns4-09.azure-dns.info
NameserverAddressesNetwork (AS)Glue
ns1-09.azure-dns.com13.107.236.9 2603:1061:0:700::9AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US13.107.236.9 2603:1061:0:700::9
ns2-09.azure-dns.net150.171.21.9 2620:1ec:8ec:700::9AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns3-09.azure-dns.org204.14.183.9 2a01:111:4000:700::9AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns4-09.azure-dns.info208.84.5.9 2620:1ec:bda:700::9AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1-09.azure-dns.com, ns2-09.azure-dns.net, ns3-09.azure-dns.org, ns4-09.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

pass

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1-09.azure-dns.com 13.107.236.9NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1-09.azure-dns.com 2603:1061:0:700::9NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-09.azure-dns.net 150.171.21.9NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-09.azure-dns.net 2620:1ec:8ec:700::9NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-09.azure-dns.org 204.14.183.9NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-09.azure-dns.org 2a01:111:4000:700::9NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns4-09.azure-dns.info 208.84.5.9NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns4-09.azure-dns.info 2620:1ec:bda:700::9NOERROR, 4 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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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

pass

serial 1 · primary ns1-09.azure-dns.com

Found

Primary (MNAME)
ns1-09.azure-dns.com
Contact (RNAME)
azuredns-hostmaster.microsoft.com
Serial
1
Refresh / retry
3600 s / 300 s
Expire
2419200 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1-09.azure-dns.com (13.107.236.9)1
ns1-09.azure-dns.com (2603:1061:0:700::9)1
ns2-09.azure-dns.net (150.171.21.9)1
ns2-09.azure-dns.net (2620:1ec:8ec:700::9)1
ns3-09.azure-dns.org (204.14.183.9)1
ns3-09.azure-dns.org (2a01:111:4000:700::9)1
ns4-09.azure-dns.info (208.84.5.9)1
ns4-09.azure-dns.info (2620:1ec:bda:700::9)1

Checks

  • ✓ Serial 1 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 5m, expire 28d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1-09.azure-dns.com is one of the listed nameservers.
  • ✓ Contact azuredns-hostmaster@microsoft.com #25
    The SOA RNAME azuredns-hostmaster.microsoft.com means azuredns-hostmaster@microsoft.com.
  • ✓ Counter serial #26
    The serial 1 is a plain counter.

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
23 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
4067ECDSAP256SHA256 (13)SHA256 7256263E24AF6CAA…yes

DNSKEY in the zone

Key tagRoleAlgorithm
4067KSK (257)ECDSAP256SHA256 (13)
8152ZSK (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 4067 (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 10:41 UTC and expires at 2026-10-23 12:41 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

info

24 records at the apex

Found

Read from
13.107.236.9:53
TypeValueTTL
SOAns1-09.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 3003600
NSns1-09.azure-dns.com.172800
NSns2-09.azure-dns.net.172800
NSns3-09.azure-dns.org.172800
NSns4-09.azure-dns.info.172800
A45.223.160.41900
A45.223.180.41900
MX5 mx-02-us-west-2.prod.hydra.sophos.com.1200
MX1 mx-01-us-west-2.prod.hydra.sophos.com.1200
TXT"globalsign-domain-verification=FB8A78E462243830382B1EA807DE0FB0"600
TXT"figma-domain-verification=4fcd3c6ba82dfdb7b0a336f1814ef6b0cbc969c7f2a80fda4a62fe384d77e4ca-1771864346"600
TXT"google-site-verification=cC-7bfnQcEt_hKpOly2oDmUaiKH5g8fmA5mgSAEE6O0"600
TXT"MS=ms83029550"600
TXT"4126f7fe-fa59-4355-8460-578150a76540"600
TXT"v=spf1 ip4:208.85.51.130 ip4:208.85.51.134 include:sendgrid.net include:spf.protection.outlook.com include:_spf_uswest2.prod.hydra.sophos.com ip4:208.65.116.58 ip4:205.201.128.0/20 ip4:198.2.128.0/18 ip4:148.105.8.0/21 include:et._spf.pardot.com include" ":49604619.spf03.hubspotemail.net include:_spf.salesforce.com include:_spf.google.com ~all"600
TXT"globalsign-domain-verification=424514175656CE4DEA9CBB0DF412A31F"600
TXT"google-site-verification=5bZwFfAIb5J4562kabwVz0gKVv8V6r9WRYoANMU7wJ0"600
TXT"anthropic-domain-verification-64ybsy=fh68icam3c3ZlniNIOyJp5uiA"600
TXT"MS=ms46235453"600
TXT"bw=mIamBTZmP8kH3qfWWpgY2sjF1HnL3FlTuqrF8d6Ef98h"600
TXT"sophos-domain-verification=75a71aeb0a5ba33b9db9ed826aaa25e9a481234cd52aefb7297e6660d136fa9d"600
TXT"acf2a7cef629494b820c2615db43db73"600
TXT"logmein-verification-code=1bx6nnjTc4XMSTUewZVljeQH1"600
TXT"google-site-verification=OwkCqdhVSUoTlmWkUE_OLWz3t1RwROjpWHqe4pb3I5I"600

Checks

  • ✓ TTLs within range #32
    TTLs: A 15m, MX 20m, NS 2d.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35