valuvdo.com

Checked 22 October 2026, 11:20 UTC · via 8.8.8.8
✗Problems found
20 passed 3 warnings 2 failed 6 info

Registration

info

.com generic · Cloud Yuqu LLC · expires 2029-06-30

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Cloud Yuqu LLC
Registered
30 June 2021
Last changed
25 October 2024
Expires
30 June 2029
Status
active
Registry nameservers
ns1.diymysite.com, ns2.diymysite.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 2029-06-30 #3
    The registration is valid until 2029-06-30 (981 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

ns1.diymysite.com, ns2.diymysite.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.diymysite.com, ns2.diymysite.com
NS in the zone
ns1.diymysite.com, ns2.diymysite.com
NameserverAddressesNetwork (AS)Glue
ns1.diymysite.com118.123.253.132 60.247.150.254 118.123.249.114 240e:d9:c200::2AS38283 CHINANET-SCIDC-AS-AP - CHINANET SiChuan Telecom Internet Data Center, CN AS38283 CHINANET-SCIDC-AS-AP - CHINANET SiChuan Telecom Internet Data Center, CN AS38283 CHINANET-SCIDC-AS-AP - CHINANET SiChuan Telecom Internet Data Center, CN AS38283 CHINANET-SCIDC-AS-AP - CHINANET SiChuan Telecom Internet Data Center, CN118.123.249.114 118.123.253.132 240e:d9:c200::2 60.247.150.254
ns2.diymysite.com211.149.230.100 61.172.183.73 240e:d9:c200:1::2AS38283 CHINANET-SCIDC-AS-AP - CHINANET SiChuan Telecom Internet Data Center, CN AS4811 CHINANET-SHANGHAI-MAN - China Telecom (Group), CN AS38283 CHINANET-SCIDC-AS-AP - CHINANET SiChuan Telecom Internet Data Center, CN211.149.230.100 240e:d9:c200:1::2 61.172.183.73

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.diymysite.com, ns2.diymysite.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.
  • i
    One address family in one network
    all IPv6 addresses are in 240e:d9:c200::/48, while the other address family is spread over several networks.
    #10
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS38283 (CHINANET-SCIDC-AS-AP - CHINANET SiChuan Telecom Internet Data Center, CN): 6 addresses; 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

fail

7 of 7 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.diymysite.com 118.123.253.132NOERROR, 236 ms, authoritativenoyes / yesrefusedv1.1
ns1.diymysite.com 60.247.150.254NOERROR, 208 ms, authoritativenoyes / yesrefusedv1.1
ns1.diymysite.com 118.123.249.114NOERROR, 224 ms, authoritativenono / yesrefused-
ns1.diymysite.com 240e:d9:c200::2NOERROR, 232 ms, authoritativenono / yesrefusedv1.1
ns2.diymysite.com 211.149.230.100NOERROR, 228 ms, authoritativenono / yesrefusedv1.1
ns2.diymysite.com 61.172.183.73NOERROR, 201 ms, authoritativenono / norefusedv1.1
ns2.diymysite.com 240e:d9:c200:1::2NOERROR, 243 ms, authoritativenono / yesrefusedv1.1

Checks

  • ✓ All respond #14
    All 7 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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.diymysite.com: "v1.1"; ns2.diymysite.com: "v1.1". Hide or replace the version string.
    #17
  • ✓ 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.diymysite.com (118.123.249.114): dial tcp 118.123.249.114:53: i/o timeout; ns1.diymysite.com (240e:d9:c200::2): dial tcp [240e:d9:c200::2]:53: i/o timeout; ns2.diymysite.com (211.149.230.100): dial tcp 211.149.230.100:53: i/o timeout; ns2.diymysite.com (61.172.183.73): dial tcp 61.172.183.73:53: i/o timeout; ns2.diymysite.com (240e:d9:c200:1::2): dial tcp [240e:d9:c200:1::2]:53: i/o timeout.
    #19
  • !
    No EDNS
    These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: ns2.diymysite.com (61.172.183.73).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2026020509 · primary ns1.diymysite.com

Found

Primary (MNAME)
ns1.diymysite.com
Contact (RNAME)
dnsconct.diymysite.com
Serial
2026020509
Refresh / retry
3600 s / 300 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.diymysite.com (118.123.253.132)2026020509
ns1.diymysite.com (60.247.150.254)2026020509
ns1.diymysite.com (118.123.249.114)2026020509
ns1.diymysite.com (240e:d9:c200::2)2026020509
ns2.diymysite.com (211.149.230.100)2026020509
ns2.diymysite.com (61.172.183.73)2026020509
ns2.diymysite.com (240e:d9:c200:1::2)2026020509

Checks

  • ✓ Serial 2026020509 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 5m, expire 14d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.diymysite.com is one of the listed nameservers.
  • ✓ Contact dnsconct@diymysite.com #25
    The SOA RNAME dnsconct.diymysite.com means dnsconct@diymysite.com.
  • ✓ Date-based serial #26
    The serial 2026020509 follows the YYYYMMDDnn convention (2026-02-05).

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

3 records at the apex

Found

Read from
118.123.253.132:53
TypeValueTTL
SOAns1.diymysite.com. dnsconct.diymysite.com. 2026020509 3600 300 1209600 36003600
NSns1.diymysite.com.3600
NSns2.diymysite.com.3600

Checks

  • ✓ TTLs within range #32
    TTLs: NS 1h. The NS TTL at the parent is 2d and in the zone 1h; resolvers may use either.
  • ✗
    CNAME at the apex
    The zone apex is a CNAME to valuvdo.gotoip55.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