wechat.com

Checked 22 October 2026, 11:25 UTC · via 8.8.8.8
✗Problems found
23 passed 2 warnings 2 failed 4 info

Registration

info

.com generic · MarkMonitor Information Technology (Shanghai) Co., Ltd. · expires 2032-11-28

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
MarkMonitor Information Technology (Shanghai) Co., Ltd.
Registered
28 November 2003
Last changed
17 April 2026
Expires
28 November 2032
Status
client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited
Registry nameservers
ns1.wechat.com, ns2.wechat.com, ns3.wechat.com, ns4.wechat.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 2032-11-28 #3
    The registration is valid until 2032-11-28 (2229 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

info

ns1.wechat.com, ns2.wechat.com, ns3.wechat.com, ns4.wechat.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.wechat.com, ns2.wechat.com, ns3.wechat.com, ns4.wechat.com
NS in the zone
ns1.wechat.com, ns2.wechat.com, ns3.wechat.com, ns4.wechat.com
NameserverAddressesNetwork (AS)Glue
ns1.wechat.com43.166.55.2 203.205.220.251 183.60.116.2 180.153.217.98 112.90.13.140 2402:4e00:c050:7a00::3AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS4134 CHINANET-BACKBONE - No.31,Jin-rong Street, CN AS4811 CHINANET-SHANGHAI-MAN - China Telecom (Group), CN AS136958 UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN112.90.13.140 180.153.217.98 183.60.116.2 203.205.220.251 2402:4e00:c050:7a00::3 43.166.55.2
ns2.wechat.com43.159.167.132 1.12.96.10 49.7.250.140 43.129.131.210 240e:9f:c600::8AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS23724 CHINANET-IDC-BJ-AP - IDC, China Telecommunications Corporation, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS134420 CHINATELECOM-Chongqing-IDC - Chongqing Telecom, CN1.12.96.10 240e:9f:c600::8 43.129.131.210 43.159.167.132 49.7.250.140
ns3.wechat.com43.134.249.22 120.204.7.98 43.159.167.11 120.233.255.187AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS9808 CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS56040 CMNET-GuangDong-AP - China Mobile communications corporation, CN120.204.7.98 120.233.255.187 43.134.249.22 43.159.167.11
ns4.wechat.com116.169.38.235 43.130.172.24 43.161.3.25 61.135.196.3 183.60.116.5AS4837 CHINA169-Backbone - CHINA UNICOM China169 Backbone, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS4808 CHINA169-BJ - China Unicom Beijing Province Network, CN AS4134 CHINANET-BACKBONE - No.31,Jin-rong Street, CN116.169.38.235 183.60.116.5 43.130.172.24 43.161.3.25 61.135.196.3

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1.wechat.com, ns2.wechat.com, ns3.wechat.com, ns4.wechat.com.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns1.wechat.com, ns2.wechat.com, ns3.wechat.com, ns4.wechat.com.
  • ✓ 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.
  • ✓ 11 autonomous systems #11
    The nameservers are spread over: AS132203 (TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN): 8 addresses; AS134420 (CHINATELECOM-Chongqing-IDC - Chongqing Telecom, CN): 1 address; AS136958 (UNICOM-GuangZhou-IDC - China Unicom Guangdong IP 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): 2 addresses; AS45090 (TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN): 2 addresses; AS4808 (CHINA169-BJ - China Unicom Beijing Province Network, CN): 1 address; AS4811 (CHINANET-SHANGHAI-MAN - China Telecom (Group), CN): 1 address; AS4837 (CHINA169-Backbone - CHINA UNICOM China169 Backbone, CN): 1 address; AS56040 (CMNET-GuangDong-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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns3.wechat.com, ns4.wechat.com.
    #13

Nameservers

fail

18 of 20 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.wechat.com 43.166.55.2NOERROR, 287 ms, authoritativenoyes / yesrefused-
ns1.wechat.com 203.205.220.251NOERROR, 250 ms, authoritativenoyes / yesrefused-
ns1.wechat.com 183.60.116.2NOERROR, 189 ms, authoritativenono / yesrefused-
ns1.wechat.com 180.153.217.98NOERROR, 188 ms, authoritativenoyes / yesrefused-
ns1.wechat.com 112.90.13.140NOERROR, 211 ms, authoritativenono / yesrefused-
ns1.wechat.com 2402:4e00:c050:7a00::3NOERROR, 147 ms, authoritativenono / yesrefused-
ns2.wechat.com 43.159.167.132NOERROR, 257 ms, authoritativenoyes / yesrefused-
ns2.wechat.com 1.12.96.10NOERROR, 205 ms, authoritativenono / yesrefused-
ns2.wechat.com 49.7.250.140NOERROR, 157 ms, authoritativenoyes / yesrefused-
ns2.wechat.com 43.129.131.210NOERROR, 263 ms, authoritativenoyes / yesrefused-
ns2.wechat.com 240e:9f:c600::8no responsenono / no--
ns3.wechat.com 43.134.249.22NOERROR, 250 ms, authoritativenoyes / yesrefused-
ns3.wechat.com 120.204.7.98NOERROR, 227 ms, authoritativenono / yesrefused-
ns3.wechat.com 43.159.167.11NOERROR, 161 ms, authoritativenoyes / yesrefused-
ns3.wechat.com 120.233.255.187NOERROR, 205 ms, authoritativenoyes / yesrefused-
ns4.wechat.com 116.169.38.235NOERROR, 215 ms, authoritativenoyes / yesrefused-
ns4.wechat.com 43.130.172.24NOERROR, 101 ms, authoritativenoyes / yesrefused-
ns4.wechat.com 43.161.3.25NOERROR, 255 ms, authoritativenoyes / yesrefused-
ns4.wechat.com 61.135.196.3no responsenono / no--
ns4.wechat.com 183.60.116.5NOERROR, 215 ms, authoritativenoyes / yesrefused-

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns2.wechat.com (240e:9f:c600::8): read udp [2a01:4f8:1c1c:eebf::1]:33447->[240e:9f:c600::8]:53: i/o timeout; ns4.wechat.com (61.135.196.3): read udp 46.225.38.91:38227->61.135.196.3: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.
  • ✓ 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: ns1.wechat.com (183.60.116.2): dial tcp 183.60.116.2:53: i/o timeout; ns1.wechat.com (112.90.13.140): dial tcp 112.90.13.140:53: i/o timeout; ns1.wechat.com (2402:4e00:c050:7a00::3): dial tcp [2402:4e00:c050:7a00::3]:53: i/o timeout; ns2.wechat.com (1.12.96.10): dial tcp 1.12.96.10:53: i/o timeout; ns3.wechat.com (120.204.7.98): dial tcp 120.204.7.98: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 1357633970 · primary ns1.wechat.com

Found

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

Serial per nameserver

NameserverSerial
ns1.wechat.com (43.166.55.2)1357633970
ns1.wechat.com (203.205.220.251)1357633970
ns1.wechat.com (183.60.116.2)1357633970
ns1.wechat.com (180.153.217.98)1357633970
ns1.wechat.com (112.90.13.140)1357633970
ns1.wechat.com (2402:4e00:c050:7a00::3)1357633970
ns2.wechat.com (43.159.167.132)1357633970
ns2.wechat.com (1.12.96.10)1357633970
ns2.wechat.com (49.7.250.140)1357633970
ns2.wechat.com (43.129.131.210)1357633970
ns3.wechat.com (43.134.249.22)1357633970
ns3.wechat.com (120.204.7.98)1357633970
ns3.wechat.com (43.159.167.11)1357633970
ns3.wechat.com (120.233.255.187)1357633970
ns4.wechat.com (116.169.38.235)1357633970
ns4.wechat.com (43.130.172.24)1357633970
ns4.wechat.com (43.161.3.25)1357633970
ns4.wechat.com (183.60.116.5)1357633970

Checks

  • ✓ Serial 1357633970 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. Current values: refresh 5m, retry 10m, expire 1d, negative TTL 1d.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.wechat.com is one of the listed nameservers.
  • ✓ Contact webmaster@qq.com #25
    The SOA RNAME webmaster.qq.com means webmaster@qq.com.
  • ✓ Timestamp serial #26
    The serial 1357633970 is a Unix timestamp (2013-01-08 08:32 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

info

10 records at the apex

Found

Read from
43.166.55.2:53
TypeValueTTL
SOAns1.wechat.com. webmaster.qq.com. 1357633970 300 600 86400 8640086400
NSns1.wechat.com.7200
NSns2.wechat.com.7200
NSns3.wechat.com.7200
NSns4.wechat.com.7200
A43.163.181.74300
A43.163.178.94300
MX10 mxbiz2.qq.com.600
MX5 mxbiz1.qq.com.600
TXT"v=spf1 include:spf.mail.qq.com ~all"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 10m, 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.
  • ✓ 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