rigol.com

Checked 22 October 2026, 10:31 UTC · via 8.8.8.8
✗Problems found
21 passed 3 warnings 2 failed 5 info

Registration

info

.com generic · Alibaba Cloud Computing (Beijing) Co., Ltd. · expires 2027-08-04

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Alibaba Cloud Computing (Beijing) Co., Ltd.
Registered
4 August 1999
Last changed
12 April 2024
Expires
4 August 2027
Status
active
Registry nameservers
ns3.dnsv4.com, ns4.dnsv4.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-08-04 #3
    The registration is valid until 2027-08-04 (286 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

ns3.dnsv4.com, ns4.dnsv4.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns3.dnsv4.com, ns4.dnsv4.com
NS in the zone
ns3.dnsv4.com, ns4.dnsv4.com
NameserverAddressesNetwork (AS)Glue
ns3.dnsv4.com1.12.0.25 36.155.149.53 1.12.0.24 1.13.76.53 124.64.205.153 125.94.59.153 43.134.249.54 2402:4e00:1470:2::10AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS56046 CMNET-Jiangsu-AP - China Mobile communications corporation, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS4808 CHINA169-BJ - China Unicom Beijing Province Network, CN AS4134 CHINANET-BACKBONE - No.31,Jin-rong Street, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN1.12.0.24 1.12.0.25 1.13.76.53 124.64.205.153 125.94.59.153 2402:4e00:1470:2::10 36.155.149.53 43.134.249.54
ns4.dnsv4.com111.13.203.53 101.227.168.53 1.12.0.23 1.12.0.26 43.130.172.54 117.135.128.153 220.196.136.53 49.7.107.153 163.177.5.53 2402:4e00:111:fff::dAS9808 CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., CN AS4811 CHINANET-SHANGHAI-MAN - China Telecom (Group), 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 AS9808 CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., CN AS140979 UNICOM-SHFT-IDC - China Unicom Shanghai FuTe IDC network, CN AS23724 CHINANET-IDC-BJ-AP - IDC, China Telecommunications Corporation, CN AS136958 UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN1.12.0.23 1.12.0.26 101.227.168.53 111.13.203.53 117.135.128.153 163.177.5.53 220.196.136.53 2402:4e00:111:fff::d 43.130.172.54 49.7.107.153

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns3.dnsv4.com, ns4.dnsv4.com.
    #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 13 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): 6 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): 3 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 .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

17 of 18 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns3.dnsv4.com 1.12.0.25NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv4.com 36.155.149.53NOERROR, 244 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv4.com 1.12.0.24NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv4.com 1.13.76.53no responsenono / no--
ns3.dnsv4.com 124.64.205.153NOERROR, 182 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv4.com 125.94.59.153NOERROR, 212 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv4.com 43.134.249.54NOERROR, 167 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv4.com 2402:4e00:1470:2::10NOERROR, 205 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 111.13.203.53NOERROR, 148 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 101.227.168.53NOERROR, 199 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 1.12.0.23NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 1.12.0.26NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 43.130.172.54NOERROR, 100 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 117.135.128.153NOERROR, 242 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 220.196.136.53NOERROR, 257 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 49.7.107.153NOERROR, 149 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 163.177.5.53NOERROR, 224 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 2402:4e00:111:fff::dNOERROR, 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: ns3.dnsv4.com (1.13.76.53): read udp 46.225.38.91:55955->1.13.76.53: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.dnsv4.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; ns4.dnsv4.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 1789629799 · primary ns3.dnsv4.com

Found

Primary (MNAME)
ns3.dnsv4.com
Contact (RNAME)
enterprise2dnsadmin.dnspod.com
Serial
1789629799
Refresh / retry
3600 s / 180 s
Expire
1209600 s
Negative TTL
180 s

Serial per nameserver

NameserverSerial
ns3.dnsv4.com (1.12.0.25)1789629799
ns3.dnsv4.com (36.155.149.53)1789629799
ns3.dnsv4.com (1.12.0.24)1789629799
ns3.dnsv4.com (124.64.205.153)1789629799
ns3.dnsv4.com (125.94.59.153)1789629799
ns3.dnsv4.com (43.134.249.54)1789629799
ns3.dnsv4.com (2402:4e00:1470:2::10)1789629799
ns4.dnsv4.com (111.13.203.53)1789629799
ns4.dnsv4.com (101.227.168.53)1789629799
ns4.dnsv4.com (1.12.0.23)1789629799
ns4.dnsv4.com (1.12.0.26)1789629799
ns4.dnsv4.com (43.130.172.54)1789629799
ns4.dnsv4.com (117.135.128.153)1789629799
ns4.dnsv4.com (220.196.136.53)1789629799
ns4.dnsv4.com (49.7.107.153)1789629799
ns4.dnsv4.com (163.177.5.53)1789629799
ns4.dnsv4.com (2402:4e00:111:fff::d)1789629799

Checks

  • ✓ Serial 1789629799 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.dnsv4.com is one of the listed nameservers.
  • ✓ Contact enterprise2dnsadmin@dnspod.com #25
    The SOA RNAME enterprise2dnsadmin.dnspod.com means enterprise2dnsadmin@dnspod.com.
  • ✓ Timestamp serial #26
    The serial 1789629799 is a Unix timestamp (2026-09-17 07:23 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

8 records at the apex

Found

Read from
1.12.0.25:53
TypeValueTTL
SOAns3.dnsv4.com. enterprise2dnsadmin.dnspod.com. 1789629799 3600 180 1209600 180180
NSns4.dnsv4.com.86400
NSns3.dnsv4.com.86400
MX1 rigol-com.mail.protection.outlook.com.600
TXT"v=spf1 ip4:58.210.178.0/24 ip4:112.80.19.0/24 ip4:123.57.153.8 ip4:106.14.105.121 ip4:123.57.75.220 ip4:47.75.97.35 ip4:93.240.53.36 ip4:219.142.131.90 ip4:13.251.173.253/32 ip4:54.255.74.198 ip4:69.63.212.160 ip4:154.21.84.105 include:spf.protection.outl" "ook.com include:spf.corp-email.com include:spfb.corp-email.com include:_spf.act-on.net include:_spf.salesforce.com ~all"600
TXT"verification-code-site-App_feishu=CK10kkIMztrmtu0YJOqX"600
TXT"google-site-verification=8slT2qfMOVCe3DJT2gxvaDC4QgVpNtF2QXIiBLWNDMA"600
TXT"google-site-verification=v_IMNCFx7Gidr0hp8lvEKfMypEVgqU0NhQD_jKI92uY"600

Checks

  • ✓ TTLs within range #32
    TTLs: MX 10m, NS 1d. The NS TTL at the parent is 2d and in the zone 1d; resolvers may use either.
  • ✗
    CNAME at the apex
    The zone apex is a CNAME to www.rigol.com.w.cdngslb.com. A CNAME can't coexist with the SOA and NS records (RFC 1034); use your provider's ALIAS/flattening feature instead.
    #33
  • ✓ 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