mikecrm.com

Checked 22 October 2026, 09:51 UTC · via 8.8.8.8
✗Problems found
19 passed 5 warnings 1 failed 6 info

Registration

info

.com generic · Alibaba Cloud Computing (Beijing) Co., Ltd. · expires 2030-09-01

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Alibaba Cloud Computing (Beijing) Co., Ltd.
Registered
1 September 2012
Last changed
29 July 2024
Expires
1 September 2030
Status
active
Registry nameservers
ns3.dnsv3.com, ns4.dnsv3.com
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 2030-09-01 #3
    The registration is valid until 2030-09-01 (1409 days).
  • i
    No transfer lock
    The domain has no transfer lock (status: active). A registrar lock protects against unauthorized transfers.
    #4
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns3.dnsv3.com, ns4.dnsv3.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns3.dnsv3.com, ns4.dnsv3.com
NS in the zone
ns3.dnsv3.com, ns4.dnsv3.com
NameserverAddressesNetwork (AS)Glue
ns3.dnsv3.com101.227.168.54 43.140.78.54 1.12.0.27 163.177.5.54 49.7.107.154 43.130.172.55 220.196.136.54 36.155.149.54 2402:4e00:1470:2::11AS4811 CHINANET-SHANGHAI-MAN - China Telecom (Group), CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS136958 UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, CN AS23724 CHINANET-IDC-BJ-AP - IDC, China Telecommunications Corporation, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS17621 CNCGROUP-SH - China Unicom Shanghai network, CN AS56046 CMNET-Jiangsu-AP - China Mobile communications corporation, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN1.12.0.27 101.227.168.54 163.177.5.54 220.196.136.54 2402:4e00:1470:2::11 36.155.149.55 43.130.172.55 43.140.78.54 49.7.107.154
ns4.dnsv3.com1.13.76.54 117.135.128.154 43.134.249.55 111.13.203.54 125.94.59.154 124.64.205.154 1.12.0.28 2402:4e00:111:fff::eAS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS24400 CMNET-V4shanghai-AS-AP - Shanghai Mobile Communications Co.,Ltd., CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS9808 CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., CN AS4134 CHINANET-BACKBONE - No.31,Jin-rong Street, CN AS4808 CHINA169-BJ - China Unicom Beijing Province Network, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN1.12.0.28 1.13.76.54 111.13.203.54 117.135.128.154 124.64.205.154 125.94.59.154 2402:4e00:111:fff::e 43.134.249.55

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns3.dnsv3.com, ns4.dnsv3.com.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • !
    Glue differs from the zone
    The addresses at the parent (glue) differ from the addresses in the zone: ns3.dnsv3.com (glue 1.12.0.27, 101.227.168.54, 163.177.5.54, 220.196.136.54, 2402:4e00:1470:2::11, 36.155.149.55, 43.130.172.55, 43.140.78.54, 49.7.107.154, zone 101.227.168.54, 43.140.78.54, 1.12.0.27, 163.177.5.54, 49.7.107.154, 43.130.172.55, 220.196.136.54, 36.155.149.54, 2402:4e00:1470:2::11). Update the glue at your registrar.
    #8
  • ✓ 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 14 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 11 autonomous systems #11
    The nameservers are spread over: AS132203 (TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN): 3 addresses; AS136958 (UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, CN): 1 address; AS17621 (CNCGROUP-SH - China Unicom Shanghai network, CN): 1 address; AS23724 (CHINANET-IDC-BJ-AP - IDC, China Telecommunications Corporation, CN): 1 address; AS24400 (CMNET-V4shanghai-AS-AP - Shanghai Mobile Communications Co.,Ltd., CN): 1 address; AS4134 (CHINANET-BACKBONE - No.31,Jin-rong Street, CN): 1 address; AS45090 (TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN): 5 addresses; AS4808 (CHINA169-BJ - China Unicom Beijing Province Network, CN): 1 address; AS4811 (CHINANET-SHANGHAI-MAN - China Telecom (Group), CN): 1 address; AS56046 (CMNET-Jiangsu-AP - China Mobile communications corporation, CN): 1 address; AS9808 (CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., CN): 1 address.
  • i
    All nameserver names under .com
    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

fail

16 of 17 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns3.dnsv3.com 101.227.168.54NOERROR, 215 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv3.com 43.140.78.54NOERROR, 207 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv3.com 1.12.0.27NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv3.com 163.177.5.54NOERROR, 173 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv3.com 49.7.107.154NOERROR, 159 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv3.com 43.130.172.55NOERROR, 100 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv3.com 220.196.136.54NOERROR, 266 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv3.com 36.155.149.54NOERROR, 202 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv3.com 2402:4e00:1470:2::11NOERROR, 172 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv3.com 1.13.76.54NOERROR, 171 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv3.com 117.135.128.154no responsenono / no--
ns4.dnsv3.com 43.134.249.55NOERROR, 167 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv3.com 111.13.203.54NOERROR, 139 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv3.com 125.94.59.154NOERROR, 207 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv3.com 124.64.205.154NOERROR, 187 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv3.com 1.12.0.28NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv3.com 2402:4e00:111:fff::eNOERROR, 217 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns4.dnsv3.com (117.135.128.154): read udp 46.225.38.91:36558->117.135.128.154:53: i/o timeout.
    #14
  • ✓ 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: ns3.dnsv3.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; ns4.dnsv3.com: "DNSPod AUTHORITY DNS 7.3.2512.01". 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 1784440510 · primary ns3.dnsv3.com

Found

Primary (MNAME)
ns3.dnsv3.com
Contact (RNAME)
enterprise1dnsadmin.dnspod.com
Serial
1784440510
Refresh / retry
3600 s / 180 s
Expire
1209600 s
Negative TTL
180 s

Serial per nameserver

NameserverSerial
ns3.dnsv3.com (101.227.168.54)1784440510
ns3.dnsv3.com (43.140.78.54)1784440510
ns3.dnsv3.com (1.12.0.27)1784440510
ns3.dnsv3.com (163.177.5.54)1784440510
ns3.dnsv3.com (49.7.107.154)1784440510
ns3.dnsv3.com (43.130.172.55)1784440510
ns3.dnsv3.com (220.196.136.54)1784440510
ns3.dnsv3.com (36.155.149.54)1784440510
ns3.dnsv3.com (2402:4e00:1470:2::11)1784440510
ns4.dnsv3.com (1.13.76.54)1784440510
ns4.dnsv3.com (43.134.249.55)1784440510
ns4.dnsv3.com (111.13.203.54)1784440510
ns4.dnsv3.com (125.94.59.154)1784440510
ns4.dnsv3.com (124.64.205.154)1784440510
ns4.dnsv3.com (1.12.0.28)1784440510
ns4.dnsv3.com (2402:4e00:111:fff::e)1784440510

Checks

  • ✓ Serial 1784440510 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 3m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1h, retry 3m, expire 14d, negative TTL 3m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns3.dnsv3.com is one of the listed nameservers.
  • ✓ Contact enterprise1dnsadmin@dnspod.com #25
    The SOA RNAME enterprise1dnsadmin.dnspod.com means enterprise1dnsadmin@dnspod.com.
  • ✓ Timestamp serial #26
    The serial 1784440510 is a Unix timestamp (2026-07-19 05:55 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

warn

11 records at the apex

Found

Read from
101.227.168.54:53
TypeValueTTL
SOAns3.dnsv3.com. enterprise1dnsadmin.dnspod.com. 1784440510 3600 180 1209600 180180
NSns4.dnsv3.com.86400
NSns3.dnsv3.com.86400
A43.143.167.3960
A101.43.153.18960
MX5 mxbiz1.qq.com.600
MX5 mxbiz2.qq.com.600
TXT"v=spf1 include:spf.mail.qq.com include:spf.mikecrm-notice.com -all"600
TXT"google-site-verification=ydIGeSi1vklI7yi7rZLZF3Nw8QRKQ74NonOAw6BUHgk"600
TXT"t6imhbfo7jjd9otaspf7ppd06t"600
TXT"QVKMQVAPY9AJAJUVU74RYJCFXTNUVZ8A"600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1d; resolvers may use either.
    #32
  • ✓ 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