0dvis.com

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

Registration

info

.com generic · DNSPod, Inc. · expires 2027-10-15

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
DNSPod, Inc.
Registered
15 October 2021
Last changed
8 June 2026
Expires
15 October 2027
Status
active
Registry nameservers
chips.dnspod.net, line.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 2027-10-15 #3
    The registration is valid until 2027-10-15 (358 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

chips.dnspod.net, line.dnspod.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
chips.dnspod.net, line.dnspod.net
NS in the zone
chips.dnspod.net, line.dnspod.net
NameserverAddressesNetwork (AS)Glue
chips.dnspod.net1.14.119.35 111.13.13.35 1.12.0.4 117.89.178.35 220.196.136.35 2402:4e00:1470:2::eAS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS9808 CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS134756 ChinaNet-NANJING-JISHAN-IDC - CHINANET Nanjing Jishan IDC network, CN AS17621 CNCGROUP-SH - China Unicom Shanghai network, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN-
line.dnspod.net111.206.98.235 1.12.0.1 101.227.168.35 36.155.149.35 1.13.76.35 2402:4e00:111:fff::cAS4808 CHINA169-BJ - China Unicom Beijing Province Network, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS4811 CHINANET-SHANGHAI-MAN - China Telecom (Group), CN AS56046 CMNET-Jiangsu-AP - China Mobile communications corporation, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, 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: chips.dnspod.net, line.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 9 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 8 autonomous systems #11
    The nameservers are spread over: AS132203 (TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN): 1 address; AS134756 (ChinaNet-NANJING-JISHAN-IDC - CHINANET Nanjing Jishan IDC network, CN): 1 address; AS17621 (CNCGROUP-SH - China Unicom Shanghai network, 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): 1 address.
  • 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

11 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
chips.dnspod.net 1.14.119.35NOERROR, 241 ms, authoritativenoyes / yesrefused-
chips.dnspod.net 111.13.13.35no responsenono / no--
chips.dnspod.net 1.12.0.4NOERROR, 5 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
chips.dnspod.net 117.89.178.35NOERROR, 178 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
chips.dnspod.net 220.196.136.35NOERROR, 261 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
chips.dnspod.net 2402:4e00:1470:2::eNOERROR, 194 ms, authoritativenoyes / yesrefused-
line.dnspod.net 111.206.98.235NOERROR, 137 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
line.dnspod.net 1.12.0.1NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
line.dnspod.net 101.227.168.35NOERROR, 175 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
line.dnspod.net 36.155.149.35NOERROR, 201 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
line.dnspod.net 1.13.76.35NOERROR, 202 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
line.dnspod.net 2402:4e00:111:fff::cNOERROR, 187 ms, authoritativenoyes / yesrefused-

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: chips.dnspod.net (111.13.13.35): read udp 46.225.38.91:38389->111.13.13.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: chips.dnspod.net: "DNSPod AUTHORITY DNS 7.3.2512.01"; line.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 1786369082 · primary chips.dnspod.net

Found

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

Serial per nameserver

NameserverSerial
chips.dnspod.net (1.14.119.35)1786369082
chips.dnspod.net (1.12.0.4)1786369082
chips.dnspod.net (117.89.178.35)1786369082
chips.dnspod.net (220.196.136.35)1786369082
chips.dnspod.net (2402:4e00:1470:2::e)1786369082
line.dnspod.net (111.206.98.235)1786369082
line.dnspod.net (1.12.0.1)1786369082
line.dnspod.net (101.227.168.35)1786369082
line.dnspod.net (36.155.149.35)1786369082
line.dnspod.net (1.13.76.35)1786369082
line.dnspod.net (2402:4e00:111:fff::c)1786369082

Checks

  • ✓ Serial 1786369082 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 chips.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 1786369082 is a Unix timestamp (2026-08-10 13:38 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

4 records at the apex

Found

Read from
1.14.119.35:53
TypeValueTTL
SOAchips.dnspod.net. freednsadmin.dnspod.com. 1786369082 3600 180 1209600 180180
NSline.dnspod.net.86400
NSchips.dnspod.net.86400
A124.221.78.91600

Checks

  • ✓ TTLs within range #32
    TTLs: A 10m, NS 1d. The NS TTL at the parent is 2d and in the zone 1d; 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