vivo.com

Checked 22 October 2026, 11:22 UTC · via 8.8.8.8
!Passed with warnings
20 passed 4 warnings 0 failed 7 info

Registration

info

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

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Alibaba Cloud Computing (Beijing) Co., Ltd.
Registered
7 April 1998
Last changed
28 July 2026
Expires
6 April 2029
Status
active
Registry nameservers
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 2029-04-06 #3
    The registration is valid until 2029-04-06 (896 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

warn

ns3.dnsv5.com, ns4.dnsv5.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns3.dnsv5.com, ns4.dnsv5.com
NS in the zone
ns3.dnsv5.com, ns4.dnsv5.com
NameserverAddressesNetwork (AS)Glue
ns3.dnsv5.com1.12.0.18 13.37.58.163 162.62.49.74 15.160.102.38 18.134.75.163 163.177.5.52 1.12.14.18 1.12.14.17 1.12.0.17 240d:c000:3011::10AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, 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 162.62.49.12 13.48.202.4 1.12.14.19 1.12.0.19 1.12.14.16 18.194.2.137 63.34.1.181 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 AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS16509 AMAZON-02 - Amazon.com, Inc., US 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

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns3.dnsv5.com, ns4.dnsv5.com.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • !
    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.0.18, 13.37.58.163, 162.62.49.74, 15.160.102.38, 18.134.75.163, 163.177.5.52, 1.12.14.18, 1.12.14.17, 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, 162.62.49.12, 13.48.202.4, 1.12.14.19, 1.12.0.19, 1.12.14.16, 18.194.2.137, 63.34.1.181, 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
  • ✓ 4 autonomous systems #11
    The nameservers are spread over: AS132203 (TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN): 7 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): 5 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

warn

19 of 19 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns3.dnsv5.com 1.12.0.18NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv5.com 13.37.58.163NOERROR, 11 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv5.com 162.62.49.74NOERROR, 3 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv5.com 15.160.102.38NOERROR, 14 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv5.com 18.134.75.163NOERROR, 15 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv5.com 163.177.5.52NOERROR, 222 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv5.com 1.12.14.18NOERROR, 206 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv5.com 1.12.14.17NOERROR, 200 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, 96 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv5.com 1.12.0.16NOERROR, 3 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv5.com 162.62.49.12NOERROR, 4 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.19NOERROR, 207 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 1.12.14.16NOERROR, 221 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 63.34.1.181NOERROR, 23 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv5.com 240d:c000:3011::fNOERROR, 99 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01

Checks

  • ✓ All respond #14
    All 19 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: 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 1792390354 · primary ns3.dnsv5.com

Found

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

Serial per nameserver

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

Checks

  • ✓ Serial 1792390354 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 1792390354 is a Unix timestamp (2026-10-19 06:12 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

12 records at the apex

Found

Read from
1.12.0.18:53
TypeValueTTL
SOAns3.dnsv5.com. enterprise3dnsadmin.dnspod.com. 1792390354 3600 180 1209600 180180
NSns4.dnsv5.com.86400
NSns3.dnsv5.com.86400
A8.209.72.150600
MX5 vivo-com.mail.protection.outlook.com.600
TXT"google-site-verification=cU1uqDUpq4yEd7t7K7WoAvABtFswLCu7jliO7zpGeyQ"600
TXT"zalo-platform-site-verification=JD6z6OZ-1mzhmO9Llyy3NshbqaY6amOUCpKv"600
TXT"figma-domain-verification=11757a22c93475f59161e5f479d5cedbf69f12f71ae1b293e3e0631a8d16b086-1762916652"600
TXT"v=spf1 include:spf.protection.outlook.com -all"600
TXT"zoho-verification=zb58384051.zmverify.zoho.com"600
TXT"openai-domain-verification=dv-8bZPqk1K8pWVe3HyMJ76xXTu"600
TXT"openai-domain-verification=dv-v0ogvQbbJUvXn7RCy1x6ixhT"600

Checks

  • ✓ TTLs within range #32
    TTLs: A 10m, MX 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.
  • 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