meituan.com

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

Registration

info

.com generic · eName Technology Co., Ltd. · expires 2027-03-29

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
eName Technology Co., Ltd.
Registered
29 March 2009
Last changed
22 February 2021
Expires
29 March 2027
Status
client delete prohibited, client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited
Registry nameservers
edns1.sankuai.com, edns2.sankuai.com, ns3.dnsv5.com, ns4.dnsv5.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 2027-03-29 #3
    The registration is valid until 2027-03-29 (157 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client transfer 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

edns1.sankuai.com, edns2.sankuai.com, ns3.dnsv5.com, ns4.dnsv5.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
edns1.sankuai.com, edns2.sankuai.com, ns3.dnsv5.com, ns4.dnsv5.com
NS in the zone
ns3.dnsv5.com, ns4.dnsv5.com
NameserverAddressesNetwork (AS)Glue
edns1.sankuai.com (parent only)103.37.136.254AS4808 CHINA169-BJ - China Unicom Beijing Province Network, CN103.37.136.254
edns2.sankuai.com (parent only)103.202.144.22AS4811 CHINANET-SHANGHAI-MAN - China Telecom (Group), CN103.202.144.22
ns3.dnsv5.com1.12.14.17 15.160.102.38 1.12.0.18 18.134.75.163 13.37.58.163 163.177.5.52 162.62.49.74 1.12.14.18 1.12.0.17 240d:c000:3011::10AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS16509 AMAZON-02 - Amazon.com, Inc., US AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS16509 AMAZON-02 - Amazon.com, Inc., US AS16509 AMAZON-02 - Amazon.com, Inc., US AS136958 UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, 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 AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN1.12.0.17 1.12.0.18 1.12.14.17 1.12.14.18 101.227.168.52 108.136.87.44 163.177.5.52 220.196.136.52 2402:4e00:1470:2::f 35.165.107.227
ns4.dnsv5.com1.12.0.16 1.12.0.19 63.34.1.181 162.62.49.12 13.48.202.4 1.12.14.16 1.12.14.19 18.194.2.137 240d:c000:3011::fAS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS16509 AMAZON-02 - Amazon.com, Inc., US AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS16509 AMAZON-02 - Amazon.com, Inc., US AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS16509 AMAZON-02 - Amazon.com, Inc., US AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN1.12.0.16 1.12.0.19 1.12.14.16 1.12.14.19 117.135.128.152 124.64.205.152 13.37.58.163 2402:4e00:111:fff::8 49.7.107.152

Checks

  • ✓ 4 nameservers #6
    Delegated to edns1.sankuai.com, edns2.sankuai.com, ns3.dnsv5.com, ns4.dnsv5.com.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: edns1.sankuai.com, edns2.sankuai.com. ns3.dnsv5.com, ns4.dnsv5.com report NS ns3.dnsv5.com ns4.dnsv5.com.
    #7
  • !
    Glue differs from the zone
    The addresses at the parent (glue) differ from the addresses in the zone: ns3.dnsv5.com (glue 1.12.0.17, 1.12.0.18, 1.12.14.17, 1.12.14.18, 101.227.168.52, 108.136.87.44, 163.177.5.52, 220.196.136.52, 2402:4e00:1470:2::f, 35.165.107.227, zone 1.12.14.17, 15.160.102.38, 1.12.0.18, 18.134.75.163, 13.37.58.163, 163.177.5.52, 162.62.49.74, 1.12.14.18, 1.12.0.17, 240d:c000:3011::10); ns4.dnsv5.com (glue 1.12.0.16, 1.12.0.19, 1.12.14.16, 1.12.14.19, 117.135.128.152, 124.64.205.152, 13.37.58.163, 2402:4e00:111:fff::8, 49.7.107.152, zone 1.12.0.16, 1.12.0.19, 63.34.1.181, 162.62.49.12, 13.48.202.4, 1.12.14.16, 1.12.14.19, 18.194.2.137, 240d:c000:3011::f). Update the glue at your registrar.
    #8
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • i
    One address family in one network
    all IPv6 addresses are in 240d:c000:3011::/48, while the other address family is spread over several networks.
    #10
  • ✓ 6 autonomous systems #11
    The nameservers are spread over: AS132203 (TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN): 11 addresses; AS136958 (UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, CN): 1 address; AS16509 (AMAZON-02 - Amazon.com, Inc., US): 6 addresses; AS45090 (TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN): 1 address; AS4808 (CHINA169-BJ - China Unicom Beijing Province Network, CN): 1 address; AS4811 (CHINANET-SHANGHAI-MAN - China Telecom (Group), 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: edns1.sankuai.com, edns2.sankuai.com.
    #13

Nameservers

fail

19 of 21 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
edns1.sankuai.com 103.37.136.254no responsenono / no--
edns2.sankuai.com 103.202.144.22no responsenono / no--
ns3.dnsv5.com 1.12.14.17NOERROR, 200 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv5.com 15.160.102.38NOERROR, 13 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv5.com 1.12.0.18NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv5.com 18.134.75.163NOERROR, 16 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv5.com 13.37.58.163NOERROR, 12 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv5.com 163.177.5.52NOERROR, 207 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv5.com 162.62.49.74NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv5.com 1.12.14.18NOERROR, 195 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv5.com 1.12.0.17NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv5.com 240d:c000:3011::10NOERROR, 98 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv5.com 1.12.0.16NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv5.com 1.12.0.19NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv5.com 63.34.1.181NOERROR, 23 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv5.com 162.62.49.12NOERROR, 3 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv5.com 13.48.202.4NOERROR, 24 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv5.com 1.12.14.16NOERROR, 229 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv5.com 1.12.14.19NOERROR, 193 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv5.com 18.194.2.137NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv5.com 240d:c000:3011::fNOERROR, 98 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: edns1.sankuai.com (103.37.136.254): read udp 46.225.38.91:38667->103.37.136.254:53: i/o timeout; edns2.sankuai.com (103.202.144.22): read udp 46.225.38.91:60116->103.202.144.22: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.dnsv5.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; ns4.dnsv5.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 1792643466 · primary ns3.dnsv5.com

Found

Primary (MNAME)
ns3.dnsv5.com
Contact (RNAME)
enterprise3dnsadmin.dnspod.com
Serial
1792643466
Refresh / retry
3600 s / 180 s
Expire
1209600 s
Negative TTL
180 s

Serial per nameserver

NameserverSerial
ns3.dnsv5.com (1.12.14.17)1792643466
ns3.dnsv5.com (15.160.102.38)1792643466
ns3.dnsv5.com (1.12.0.18)1792643466
ns3.dnsv5.com (18.134.75.163)1792643466
ns3.dnsv5.com (13.37.58.163)1792643466
ns3.dnsv5.com (163.177.5.52)1792643466
ns3.dnsv5.com (162.62.49.74)1792643466
ns3.dnsv5.com (1.12.14.18)1792643466
ns3.dnsv5.com (1.12.0.17)1792643466
ns3.dnsv5.com (240d:c000:3011::10)1792643466
ns4.dnsv5.com (1.12.0.16)1792643466
ns4.dnsv5.com (1.12.0.19)1792643466
ns4.dnsv5.com (63.34.1.181)1792643466
ns4.dnsv5.com (162.62.49.12)1792643466
ns4.dnsv5.com (13.48.202.4)1792643466
ns4.dnsv5.com (1.12.14.16)1792643466
ns4.dnsv5.com (1.12.14.19)1792643466
ns4.dnsv5.com (18.194.2.137)1792643466
ns4.dnsv5.com (240d:c000:3011::f)1792643466

Checks

  • ✓ Serial 1792643466 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.dnsv5.com is one of the listed nameservers.
  • ✓ Contact enterprise3dnsadmin@dnspod.com #25
    The SOA RNAME enterprise3dnsadmin.dnspod.com means enterprise3dnsadmin@dnspod.com.
  • ✓ Timestamp serial #26
    The serial 1792643466 is a Unix timestamp (2026-10-22 04:31 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

12 records at the apex

Found

Read from
1.12.14.17:53
TypeValueTTL
SOAns3.dnsv5.com. enterprise3dnsadmin.dnspod.com. 1792643466 3600 180 1209600 180180
NSns3.dnsv5.com.86400
NSns4.dnsv5.com.86400
A43.132.29.159180
MX10 mx1.f5.meituan.com.180
TXT"MS=ms82932649"600
TXT"MS=ms99510167"600
TXT"rjrtgnqi5ko4die1601mj7cjen"600
TXT"umvcibohan7pm89tjtltj4672d"600
TXT"apple-domain-verification=sdez0a7ERL2qRlJt"600
TXT"atlassian-domain-verification=ucMIdhO63YrbU6vtk9altTnIXuGmcQc5rjiI4aMhXPVAfV/Uc2CzBO/aCghg9d6w"600
TXT"v=spf1 include:_spf-a.meituan.com include:_spf-b.meituan.com include:_spf-overseas.meituan.com include:spf.protection.outlook.com -all"600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (3m), MX (3m). 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.
  • ✓ 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