midea.com

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

Registration

info

.com generic · Beijing Brandma International Networking Technology Ltd. · expires 2028-05-10

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Beijing Brandma International Networking Technology Ltd.
Registered
11 May 1998
Last changed
6 July 2026
Expires
10 May 2028
Status
client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited
Registry nameservers
gtmcnc.midea.com.cn, gtmct.midea.com.cn, gtmnhcnc.midea.com.cn, gtmnhct.midea.com.cn
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 2028-05-10 #3
    The registration is valid until 2028-05-10 (565 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

gtmcnc.midea.com.cn, gtmct.midea.com.cn, gtmnhcnc.midea.com.cn, gtmnhct.midea.com.cn

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
gtmcnc.midea.com.cn, gtmct.midea.com.cn, gtmnhcnc.midea.com.cn, gtmnhct.midea.com.cn
NS in the zone
gtmcnc.midea.com.cn, gtmct.midea.com.cn, gtmhk.midea.com.cn, gtmnhcnc.midea.com.cn, gtmnhct.midea.com.cn, gtmpccw.midea.com.cn
NameserverAddressesNetwork (AS)Glue
gtmcnc.midea.com.cn58.252.101.8AS17816 CHINA169-GZ - China Unicom IP network China169 Guangdong province, CN-
gtmct.midea.com.cn202.104.30.87AS4134 CHINANET-BACKBONE - No.31,Jin-rong Street, CN-
gtmhk.midea.com.cn (zone only)159.138.156.91AS136907 HWCLOUDS-AS-AP - HUAWEI CLOUDS, HK-
gtmnhcnc.midea.com.cn157.122.158.5AS17816 CHINA169-GZ - China Unicom IP network China169 Guangdong province, CN-
gtmnhct.midea.com.cn218.13.19.5AS4134 CHINANET-BACKBONE - No.31,Jin-rong Street, CN-
gtmpccw.midea.com.cn (zone only)159.138.32.114AS136907 HWCLOUDS-AS-AP - HUAWEI CLOUDS, HK-

Checks

  • ✓ 4 nameservers #6
    Delegated to gtmcnc.midea.com.cn, gtmct.midea.com.cn, gtmnhcnc.midea.com.cn, gtmnhct.midea.com.cn.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: gtmhk.midea.com.cn, gtmpccw.midea.com.cn. gtmcnc.midea.com.cn, gtmct.midea.com.cn, gtmhk.midea.com.cn, gtmnhcnc.midea.com.cn, gtmnhct.midea.com.cn, gtmpccw.midea.com.cn report NS gtmcnc.midea.com.cn gtmct.midea.com.cn gtmhk.midea.com.cn gtmnhcnc.midea.com.cn gtmnhct.midea.com.cn gtmpccw.midea.com.cn.
    #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 0 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS136907 (HWCLOUDS-AS-AP - HUAWEI CLOUDS, HK): 2 addresses; AS17816 (CHINA169-GZ - China Unicom IP network China169 Guangdong province, CN): 2 addresses; AS4134 (CHINANET-BACKBONE - No.31,Jin-rong Street, CN): 2 addresses.
  • i
    All nameserver names under .cn
    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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

fail

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
gtmcnc.midea.com.cn 58.252.101.8NOERROR, 154 ms, authoritativenono / yesrefused9.16.33
gtmct.midea.com.cn 202.104.30.87NOERROR, 193 ms, authoritativenono / yesrefused9.16.33
gtmhk.midea.com.cn 159.138.156.91NOERROR, 268 ms, authoritativenoyes / yesrefused9.16.33
gtmnhcnc.midea.com.cn 157.122.158.5NOERROR, 172 ms, authoritativenono / yesrefused9.16.33
gtmnhct.midea.com.cn 218.13.19.5NOERROR, 200 ms, authoritativenono / yesrefused9.16.33
gtmpccw.midea.com.cn 159.138.32.114NOERROR, 265 ms, authoritativenoyes / yesrefused9.16.33

Checks

  • ✓ All respond #14
    All 6 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: gtmcnc.midea.com.cn: "9.16.33"; gtmct.midea.com.cn: "9.16.33"; gtmhk.midea.com.cn: "9.16.33"; gtmnhcnc.midea.com.cn: "9.16.33"; gtmnhct.midea.com.cn: "9.16.33"; gtmpccw.midea.com.cn: "9.16.33". Hide or replace the version string.
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: gtmcnc.midea.com.cn (58.252.101.8): dial tcp 58.252.101.8:53: i/o timeout; gtmct.midea.com.cn (202.104.30.87): dial tcp 202.104.30.87:53: i/o timeout; gtmnhcnc.midea.com.cn (157.122.158.5): dial tcp 157.122.158.5:53: i/o timeout; gtmnhct.midea.com.cn (218.13.19.5): dial tcp 218.13.19.5:53: i/o timeout.
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 2026102202 · primary gtmct.midea.com.cn

Found

Primary (MNAME)
gtmct.midea.com.cn
Contact (RNAME)
hostmaster.gtmct.midea.com.cn
Serial
2026102202
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
60 s

Serial per nameserver

NameserverSerial
gtmcnc.midea.com.cn (58.252.101.8)2026102202
gtmct.midea.com.cn (202.104.30.87)2026102202
gtmhk.midea.com.cn (159.138.156.91)2026102202
gtmnhcnc.midea.com.cn (157.122.158.5)2026102202
gtmnhct.midea.com.cn (218.13.19.5)2026102202
gtmpccw.midea.com.cn (159.138.32.114)2026102202

Checks

  • ✓ Serial 2026102202 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 3h, retry 1h, expire 7d, negative TTL 1m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver gtmct.midea.com.cn is one of the listed nameservers.
  • ✓ Contact hostmaster@gtmct.midea.com.cn #25
    The SOA RNAME hostmaster.gtmct.midea.com.cn means hostmaster@gtmct.midea.com.cn.
  • ✓ Date-based serial #26
    The serial 2026102202 follows the YYYYMMDDnn convention (2026-10-22).

DNSSEC

info

Not signed

Found

Validated by resolver
no
Lookup error: read udp 46.225.38.91:56625->58.252.101.8:53: i/o timeout

Checks

  • i
    Could not be checked
    The DNSSEC lookup failed, so this could not be checked: read udp 46.225.38.91:56625->58.252.101.8:53: i/o timeout
    #27

Records

warn

15 records at the apex

Found

Read from
58.252.101.8:53
TypeValueTTL
SOAgtmct.midea.com.cn. hostmaster.gtmct.midea.com.cn. 2026102202 10800 3600 604800 603600
NSgtmcnc.midea.com.cn.3600
NSgtmnhcnc.midea.com.cn.3600
NSgtmct.midea.com.cn.3600
NSgtmpccw.midea.com.cn.3600
NSgtmnhct.midea.com.cn.3600
NSgtmhk.midea.com.cn.3600
A15.197.207.9230
MX5 mxnh1.midea.com.3600
MX15 mxhk1.midea.com.3600
MX15 mxhk2.midea.com.3600
MX10 mxsd1.midea.com.3600
TXT"v=spf1 include:spf.midea.com -all"300
TXT"e6Mbvq84qOwW+r7YbKmoAaKd0B0MeSxUvEX+ZVWXFyiSQbrOwtMlAt/ySy37UCf5RvAClOi6HU21DtEMqgAc1w=="300
TXT"google-gws-recovery-domain-verification=65557205"300

Checks

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