leiphone.com

Checked 22 October 2026, 09:34 UTC · via 8.8.8.8
✗Problems found
19 passed 4 warnings 2 failed 6 info

Registration

info

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

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Alibaba Cloud Computing (Beijing) Co., Ltd.
Registered
1 October 2009
Last changed
22 March 2024
Expires
1 October 2029
Status
active
Registry nameservers
f1g1ns1.dnspod.net, f1g1ns2.dnspod.net
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 2029-10-01 #3
    The registration is valid until 2029-10-01 (1075 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

info

f1g1ns1.dnspod.net, f1g1ns2.dnspod.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
f1g1ns1.dnspod.net, f1g1ns2.dnspod.net
NS in the zone
f1g1ns1.dnspod.net, f1g1ns2.dnspod.net
NameserverAddressesNetwork (AS)Glue
f1g1ns1.dnspod.net117.135.128.235 125.94.59.235 163.177.5.35 1.14.119.35 111.13.13.35 1.12.0.4 2402:4e00:1470:2::eAS9808 CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., CN AS4134 CHINANET-BACKBONE - No.31,Jin-rong Street, CN AS136958 UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS9808 CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN-
f1g1ns2.dnspod.net106.39.207.235 111.206.98.235 1.12.0.1 101.227.168.35 1.13.76.35 220.196.136.35 36.155.149.35 2402:4e00:111:fff::cAS23724 CHINANET-IDC-BJ-AP - IDC, China Telecommunications Corporation, CN AS4808 CHINA169-BJ - China Unicom Beijing Province Network, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS4811 CHINANET-SHANGHAI-MAN - China Telecom (Group), CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, 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, CN-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: f1g1ns1.dnspod.net, f1g1ns2.dnspod.net.
    #6
  • ✓ 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 12 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 10 autonomous systems #11
    The nameservers are spread over: AS132203 (TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN): 1 address; 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; 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): 2 addresses.
  • i
    All nameserver names under .net
    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

14 of 15 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
f1g1ns1.dnspod.net 117.135.128.235NOERROR, 246 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
f1g1ns1.dnspod.net 125.94.59.235NOERROR, 200 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
f1g1ns1.dnspod.net 163.177.5.35NOERROR, 220 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
f1g1ns1.dnspod.net 1.14.119.35NOERROR, 237 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
f1g1ns1.dnspod.net 111.13.13.35NOERROR, 145 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
f1g1ns1.dnspod.net 1.12.0.4NOERROR, 6 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
f1g1ns1.dnspod.net 2402:4e00:1470:2::eNOERROR, 223 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
f1g1ns2.dnspod.net 106.39.207.235NOERROR, 142 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
f1g1ns2.dnspod.net 111.206.98.235NOERROR, 217 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
f1g1ns2.dnspod.net 1.12.0.1NOERROR, 6 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
f1g1ns2.dnspod.net 101.227.168.35NOERROR, 164 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
f1g1ns2.dnspod.net 1.13.76.35NOERROR, 210 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
f1g1ns2.dnspod.net 220.196.136.35NOERROR, 197 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
f1g1ns2.dnspod.net 36.155.149.35no responsenono / no--
f1g1ns2.dnspod.net 2402:4e00:111:fff::cNOERROR, 194 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: f1g1ns2.dnspod.net (36.155.149.35): read udp 46.225.38.91:44941->36.155.149.35: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: f1g1ns1.dnspod.net: "DNSPod AUTHORITY DNS 7.3.2512.01"; f1g1ns2.dnspod.net: "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 1783018042 · primary f1g1ns1.dnspod.net

Found

Primary (MNAME)
f1g1ns1.dnspod.net
Contact (RNAME)
freednsadmin.dnspod.com
Serial
1783018042
Refresh / retry
3600 s / 180 s
Expire
1209600 s
Negative TTL
180 s

Serial per nameserver

NameserverSerial
f1g1ns1.dnspod.net (117.135.128.235)1783018042
f1g1ns1.dnspod.net (125.94.59.235)1783018042
f1g1ns1.dnspod.net (163.177.5.35)1783018042
f1g1ns1.dnspod.net (1.14.119.35)1783018042
f1g1ns1.dnspod.net (111.13.13.35)1783018042
f1g1ns1.dnspod.net (1.12.0.4)1783018042
f1g1ns1.dnspod.net (2402:4e00:1470:2::e)1783018042
f1g1ns2.dnspod.net (106.39.207.235)1783018042
f1g1ns2.dnspod.net (111.206.98.235)1783018042
f1g1ns2.dnspod.net (1.12.0.1)1783018042
f1g1ns2.dnspod.net (101.227.168.35)1783018042
f1g1ns2.dnspod.net (1.13.76.35)1783018042
f1g1ns2.dnspod.net (220.196.136.35)1783018042
f1g1ns2.dnspod.net (2402:4e00:111:fff::c)1783018042

Checks

  • ✓ Serial 1783018042 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 f1g1ns1.dnspod.net is one of the listed nameservers.
  • ✓ Contact freednsadmin@dnspod.com #25
    The SOA RNAME freednsadmin.dnspod.com means freednsadmin@dnspod.com.
  • ✓ Timestamp serial #26
    The serial 1783018042 is a Unix timestamp (2026-07-02 18:47 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

fail

9 records at the apex

Found

Read from
117.135.128.235:53
TypeValueTTL
SOAf1g1ns1.dnspod.net. freednsadmin.dnspod.com. 1783018042 3600 180 1209600 180180
NSf1g1ns1.dnspod.net.86400
NSf1g1ns2.dnspod.net.86400
MX5 mxbiz1.qq.com.10
MX10 mxbiz2.qq.com.10
TXT"_globalsign-domain-verification=nC75rTDmY4slTiYG9kE8B3PCAXq7vA6fYl3Y5STMJY"600
TXT"v=spf1 include:spf.mail.qq.com ~all"600
TXT"verification-code-site-App_feishu=bAxVBUl4SJng47v7GElu"600
TXT"google-site-verification=lQerN--VegRxvOmKMbWZltK9vaO7ejGzvnM8LaWCw6w"600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: MX (10s). 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
  • ✗
    CNAME at the apex
    The zone apex is a CNAME to 446bbe0e649930ef29037a24aec22008.qcloudwzgj.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