sns.qzone.qq.com

Zone qzone.qq.com · Checked 22 October 2026, 10:45 UTC · via 8.8.8.8
✗Problems found
21 passed 2 warnings 2 failed 6 info

Registration

warn

.com generic · MarkMonitor Information Technology (Shanghai) Co., Ltd. · expires 2034-07-27

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
MarkMonitor Information Technology (Shanghai) Co., Ltd.
Registered
4 May 1995
Last changed
22 October 2026
Expires
27 July 2034
Status
client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited
Registry nameservers
ns1.qq.com, ns2.qq.com, ns3.qq.com, ns4.qq.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 2034-07-27 #3
    The registration is valid until 2034-07-27 (2834 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 differ
    Only at the registry: ns1.qq.com, ns2.qq.com, ns3.qq.com, ns4.qq.com; only in the parent zone: ns-cmn1.qq.com, ns-cnc1.qq.com, ns-os1.qq.com, ns-tel1.qq.com. The registry database and the published delegation should be identical; a pending change may not have been published yet.
    #5

Delegation

info

ns-cmn1.qq.com, ns-cnc1.qq.com, ns-os1.qq.com, ns-tel1.qq.com

Found

Parent zone
qq.com
Delegation from
ns1.qq.com (43.166.55.2)
NS at the parent
ns-cmn1.qq.com, ns-cnc1.qq.com, ns-os1.qq.com, ns-tel1.qq.com
NameserverAddressesNetwork (AS)Glue
ns-cmn1.qq.com (parent only)42.187.235.2 43.140.54.204 43.142.212.27 2402:4e00:111:ff4::3AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN-
ns-cnc1.qq.com (parent only)157.255.6.102 61.135.196.2 140.207.180.96 240e:e1:aa00:2002::3AS136958 UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, CN AS4808 CHINA169-BJ - China Unicom Beijing Province Network, CN AS140979 UNICOM-SHFT-IDC - China Unicom Shanghai FuTe IDC network, CN AS4812 CHINANET-SH-AP - China Telecom (Group), CN-
ns-os1.qq.com (parent only)43.134.249.23 43.161.3.26 43.129.131.16 203.205.220.26 43.159.167.10 43.166.55.3 43.159.167.133 43.130.172.23 2402:4e00:111:ff4::3AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN-
ns-tel1.qq.com (parent only)49.7.250.139 101.227.161.254 14.116.238.220 240e:e1:aa00:2002::3AS23724 CHINANET-IDC-BJ-AP - IDC, China Telecommunications Corporation, CN AS4811 CHINANET-SHANGHAI-MAN - China Telecom (Group), CN AS4134 CHINANET-BACKBONE - No.31,Jin-rong Street, CN AS4812 CHINANET-SH-AP - China Telecom (Group), CN-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns-cmn1.qq.com, ns-cnc1.qq.com, ns-os1.qq.com, ns-tel1.qq.com.
  • ✓ 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 16 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 9 autonomous systems #11
    The nameservers are spread over: AS132203 (TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN): 8 addresses; AS136958 (UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, CN): 1 address; AS140979 (UNICOM-SHFT-IDC - China Unicom Shanghai FuTe IDC network, CN): 1 address; AS23724 (CHINANET-IDC-BJ-AP - IDC, China Telecommunications Corporation, 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; AS4812 (CHINANET-SH-AP - China Telecom (Group), CN): 2 addresses.
  • 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

21 of 21 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns-cmn1.qq.com 42.187.235.2NOERROR, 167 ms, authoritativenoyes / yesrefused-
ns-cmn1.qq.com 43.140.54.204NOERROR, 193 ms, authoritativenoyes / yesrefused-
ns-cmn1.qq.com 43.142.212.27NOERROR, 197 ms, authoritativenoyes / yesrefused-
ns-cmn1.qq.com 2402:4e00:111:ff4::3NOERROR, 193 ms, authoritativenono / yesrefused-
ns-cnc1.qq.com 157.255.6.102NOERROR, 157 ms, authoritativenono / yesrefused-
ns-cnc1.qq.com 61.135.196.2NOERROR, 130 ms, authoritativenoyes / yesrefused-
ns-cnc1.qq.com 140.207.180.96NOERROR, 163 ms, authoritativenoyes / yesrefused-
ns-cnc1.qq.com 240e:e1:aa00:2002::3NOERROR, 164 ms, authoritativenono / yesrefused-
ns-os1.qq.com 43.134.249.23NOERROR, 161 ms, authoritativenoyes / yesrefused-
ns-os1.qq.com 43.161.3.26NOERROR, 265 ms, authoritativenoyes / yesrefused-
ns-os1.qq.com 43.129.131.16NOERROR, 255 ms, authoritativenoyes / yesrefused-
ns-os1.qq.com 203.205.220.26NOERROR, 249 ms, authoritativenono / yesrefused-
ns-os1.qq.com 43.159.167.10NOERROR, 157 ms, authoritativenoyes / yesrefused-
ns-os1.qq.com 43.166.55.3NOERROR, 287 ms, authoritativenoyes / yesrefused-
ns-os1.qq.com 43.159.167.133NOERROR, 157 ms, authoritativenoyes / yesrefused-
ns-os1.qq.com 43.130.172.23NOERROR, 100 ms, authoritativenoyes / yesrefused-
ns-os1.qq.com 2402:4e00:111:ff4::3NOERROR, 197 ms, authoritativenono / yesrefused-
ns-tel1.qq.com 49.7.250.139NOERROR, 136 ms, authoritativenono / yesrefused-
ns-tel1.qq.com 101.227.161.254NOERROR, 184 ms, authoritativenoyes / yesrefused-
ns-tel1.qq.com 14.116.238.220NOERROR, 182 ms, authoritativenoyes / yesrefused-
ns-tel1.qq.com 240e:e1:aa00:2002::3NOERROR, 167 ms, authoritativenono / yesrefused-

Checks

  • ✓ All respond #14
    All 21 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.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns-cmn1.qq.com (2402:4e00:111:ff4::3): dial tcp [2402:4e00:111:ff4::3]:53: connect: connection refused; ns-cnc1.qq.com (157.255.6.102): read tcp 46.225.38.91:35010->157.255.6.102:53: i/o timeout; ns-cnc1.qq.com (240e:e1:aa00:2002::3): dial tcp [240e:e1:aa00:2002::3]:53: connect: connection refused; ns-os1.qq.com (203.205.220.26): read tcp 46.225.38.91:51018->203.205.220.26:53: i/o timeout; ns-os1.qq.com (2402:4e00:111:ff4::3): dial tcp [2402:4e00:111:ff4::3]:53: connect: connection refused; ns-tel1.qq.com (49.7.250.139): read tcp 46.225.38.91:58368->49.7.250.139:53: i/o timeout; ns-tel1.qq.com (240e:e1:aa00:2002::3): dial tcp [240e:e1:aa00:2002::3]:53: connect: connection refused.
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 1768984747 · primary qq.com

Found

Primary (MNAME)
qq.com
Contact (RNAME)
webmaster.qq.com
Serial
1768984747
Refresh / retry
300 s / 600 s
Expire
86400 s
Negative TTL
180 s

Serial per nameserver

NameserverSerial
ns-cmn1.qq.com (42.187.235.2)1768984747
ns-cmn1.qq.com (43.140.54.204)1768984747
ns-cmn1.qq.com (43.142.212.27)1768984747
ns-cmn1.qq.com (2402:4e00:111:ff4::3)1768984747
ns-cnc1.qq.com (157.255.6.102)1768984747
ns-cnc1.qq.com (61.135.196.2)1768984747
ns-cnc1.qq.com (140.207.180.96)1768984747
ns-cnc1.qq.com (240e:e1:aa00:2002::3)1768984747
ns-os1.qq.com (43.134.249.23)1768984747
ns-os1.qq.com (43.161.3.26)1768984747
ns-os1.qq.com (43.129.131.16)1768984747
ns-os1.qq.com (203.205.220.26)1768984747
ns-os1.qq.com (43.159.167.10)1768984747
ns-os1.qq.com (43.166.55.3)1768984747
ns-os1.qq.com (43.159.167.133)1768984747
ns-os1.qq.com (43.130.172.23)1768984747
ns-os1.qq.com (2402:4e00:111:ff4::3)1768984747
ns-tel1.qq.com (49.7.250.139)1768984747
ns-tel1.qq.com (101.227.161.254)1768984747
ns-tel1.qq.com (14.116.238.220)1768984747
ns-tel1.qq.com (240e:e1:aa00:2002::3)1768984747

Checks

  • ✓ Serial 1768984747 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 5m is outside 20m–1d; retry 10m should be shorter than refresh 5m; expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down; negative caching TTL (minimum) 3m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 5m, retry 10m, expire 1d, negative TTL 3m.
    #23
  • i
    Hidden master
    The primary nameserver qq.com is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact webmaster@qq.com #25
    The SOA RNAME webmaster.qq.com means webmaster@qq.com.
  • ✓ Timestamp serial #26
    The serial 1768984747 is a Unix timestamp (2026-01-21 08:39 UTC).

DNSSEC

info

DNS query for qzone.qq.com failed: read udp 46.225.38.91:51661->8.8.8.8:53: i/o timeout

Checks

  • i
    Could not be checked
    The DNSSEC lookup failed, so this could not be checked: DNS query for qzone.qq.com failed: read udp 46.225.38.91:51661->8.8.8.8:53: i/o timeout
    #27

Records

fail

1 record at the apex

Found

Read from
42.187.235.2:53
TypeValueTTL
SOAqq.com. webmaster.qq.com. 1768984747 300 600 86400 180180

Checks

  • ✓ TTLs within range #32
    TTLs: .
  • ✗
    CNAME at the apex
    The zone apex is a CNAME to qzs.tc.qq.com. A CNAME can't coexist with the SOA and NS records (RFC 1034); use your provider's ALIAS/flattening feature instead.
    #33
  • 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