list-manage2.com

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

Registration

info

.com generic · MarkMonitor Inc. · expires 2032-05-18

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
MarkMonitor Inc.
Registered
18 May 2009
Last changed
21 October 2024
Expires
18 May 2032
Status
client delete prohibited, client transfer prohibited, client update prohibited
Registry nameservers
a1-205.akam.net, a14-66.akam.net, a4-65.akam.net, a5-65.akam.net, a6-66.akam.net, a7-66.akam.net
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 2032-05-18 #3
    The registration is valid until 2032-05-18 (2035 days).
  • ✓ Transfer locked #4
    Registry status: client delete 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

a1-205.akam.net, a14-66.akam.net, a4-65.akam.net, a5-65.akam.net, a6-66.akam.net, a7-66.akam.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
a1-205.akam.net, a14-66.akam.net, a4-65.akam.net, a5-65.akam.net, a6-66.akam.net, a7-66.akam.net
NS in the zone
a1-205.akam.net, a14-66.akam.net, a4-65.akam.net, a5-65.akam.net, a6-66.akam.net, a7-66.akam.net
NameserverAddressesNetwork (AS)Glue
a1-205.akam.net193.108.91.205 2600:1401:2::cdAS20940 AKAMAI-ASN1 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a14-66.akam.net184.26.161.66 2600:1480:1800::42AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a4-65.akam.net72.246.46.65 2600:1480:9000::41AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a5-65.akam.net95.100.168.65 2600:1480:b000::41AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a6-66.akam.net23.211.133.66 2600:1401:1::42AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a7-66.akam.net23.61.199.66 2600:1406:32::42AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-

Checks

  • ✓ 6 nameservers #6
    Delegated to a1-205.akam.net, a14-66.akam.net, a4-65.akam.net, a5-65.akam.net, a6-66.akam.net, a7-66.akam.net.
  • ✓ 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 6 IPv4 /24s and 6 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS20940 (AKAMAI-ASN1 - Akamai International B.V., NL): 1 address; AS21342 (AKAMAI-ASN2 - Akamai International B.V., NL): 11 addresses.
  • i
    All nameserver names under .net
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

12 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
a1-205.akam.net 193.108.91.205NOERROR, 3 ms, authoritativenoyes / yesrefused41824.6
a1-205.akam.net 2600:1401:2::cdNOERROR, 4 ms, authoritativenoyes / yesrefused41824.7
a14-66.akam.net 184.26.161.66NOERROR, 3 ms, authoritativenoyes / yesrefused48878.26
a14-66.akam.net 2600:1480:1800::42NOERROR, 3 ms, authoritativenoyes / yesrefused48878.26
a4-65.akam.net 72.246.46.65NOERROR, 4 ms, authoritativenoyes / yesrefused48878.31
a4-65.akam.net 2600:1480:9000::41NOERROR, 3 ms, authoritativenoyes / yesrefused48878.30
a5-65.akam.net 95.100.168.65NOERROR, 3 ms, authoritativenoyes / yesrefused41824.7
a5-65.akam.net 2600:1480:b000::41NOERROR, 4 ms, authoritativenoyes / yesrefused41824.9
a6-66.akam.net 23.211.133.66NOERROR, 3 ms, authoritativenoyes / yesrefused48878.32
a6-66.akam.net 2600:1401:1::42NOERROR, 4 ms, authoritativenoyes / yesrefused48878.32
a7-66.akam.net 23.61.199.66NOERROR, 3 ms, authoritativenoyes / yesrefused41824.9
a7-66.akam.net 2600:1406:32::42NOERROR, 4 ms, authoritativenoyes / yesrefused41824.5

Checks

  • ✓ All respond #14
    All 12 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: a1-205.akam.net: "41824.6"; a1-205.akam.net: "41824.7"; a14-66.akam.net: "48878.26"; a4-65.akam.net: "48878.31"; a4-65.akam.net: "48878.30"; a5-65.akam.net: "41824.7"; a5-65.akam.net: "41824.9"; a6-66.akam.net: "48878.32"; a7-66.akam.net: "41824.9"; a7-66.akam.net: "41824.5". 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

pass

serial 2015090138 · primary a1-205.akam.net

Found

Primary (MNAME)
a1-205.akam.net
Contact (RNAME)
domains.mailchimp.com
Serial
2015090138
Refresh / retry
10800 s / 3600 s
Expire
1209600 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
a1-205.akam.net (193.108.91.205)2015090138
a1-205.akam.net (2600:1401:2::cd)2015090138
a14-66.akam.net (184.26.161.66)2015090138
a14-66.akam.net (2600:1480:1800::42)2015090138
a4-65.akam.net (72.246.46.65)2015090138
a4-65.akam.net (2600:1480:9000::41)2015090138
a5-65.akam.net (95.100.168.65)2015090138
a5-65.akam.net (2600:1480:b000::41)2015090138
a6-66.akam.net (23.211.133.66)2015090138
a6-66.akam.net (2600:1401:1::42)2015090138
a7-66.akam.net (23.61.199.66)2015090138
a7-66.akam.net (2600:1406:32::42)2015090138

Checks

  • ✓ Serial 2015090138 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 14d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver a1-205.akam.net is one of the listed nameservers.
  • ✓ Contact domains@mailchimp.com #25
    The SOA RNAME domains.mailchimp.com means domains@mailchimp.com.
  • ✓ Date-based serial #26
    The serial 2015090138 follows the YYYYMMDDnn convention (2015-09-01).

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

14 records at the apex

Found

Read from
193.108.91.205:53
TypeValueTTL
SOAa1-205.akam.net. domains.mailchimp.com. 2015090138 10800 3600 1209600 300300
NSa7-66.akam.net.7200
NSa6-66.akam.net.7200
NSa14-66.akam.net.7200
NSa1-205.akam.net.7200
NSa4-65.akam.net.7200
NSa5-65.akam.net.7200
A205.201.132.963600
MX0 .86400
TXT"google-site-verification=XFUKjyLKeM8ZSPc-pMLGTeZCJss3fNrkpjF9HucUWEI"86400
TXT"_5ztv7l82u6qsfemlfu89jyhrhyho2z1"86400
TXT"_72ru7fr8c0ncfmjg71hyedfisw40m4h"86400
TXT"_lgool0gg7wzos9kz40nbb40e86izja0"86400
TXT"_d8moa35rd30y0xzeb9k94f8ax8oxy7c"86400

Checks

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