zumvu.com

Checked 22 October 2026, 11:44 UTC · via 8.8.8.8
!Passed with warnings
21 passed 2 warnings 0 failed 8 info

Registration

info

.com generic · eNom, LLC · expires 2028-02-25

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
eNom, LLC
Registered
25 February 2013
Last changed
26 September 2026
Expires
25 February 2028
Status
client transfer prohibited
Registry nameservers
12.sucuridns.com, 13.sucuridns.com, 16.sucuridns.com, 17.sucuridns.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 2028-02-25 #3
    The registration is valid until 2028-02-25 (490 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

12.sucuridns.com, 13.sucuridns.com, 16.sucuridns.com, 17.sucuridns.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
12.sucuridns.com, 13.sucuridns.com, 16.sucuridns.com, 17.sucuridns.com
NS in the zone
12.sucuridns.com, 13.sucuridns.com, 16.sucuridns.com, 17.sucuridns.com
NameserverAddressesNetwork (AS)Glue
12.sucuridns.com192.161.0.12 193.19.225.12 2a02:fe80:2010::12AS30148 SUCURI-SEC - Sucuri, US AS30148 SUCURI-SEC - Sucuri, US AS30148 SUCURI-SEC - Sucuri, US192.161.0.12 2a02:fe80:2010::12
13.sucuridns.com193.19.225.13 192.161.0.13 2a02:fe80:2010::13AS30148 SUCURI-SEC - Sucuri, US AS30148 SUCURI-SEC - Sucuri, US AS30148 SUCURI-SEC - Sucuri, US192.161.0.13 2a02:fe80:2010::13
16.sucuridns.com193.19.225.16 192.161.0.16 2a02:fe80:2010::16AS30148 SUCURI-SEC - Sucuri, US AS30148 SUCURI-SEC - Sucuri, US AS30148 SUCURI-SEC - Sucuri, US192.161.0.16 193.19.225.16 2a02:fe80:2010::16
17.sucuridns.com193.19.225.17 192.161.0.17 2a02:fe80:2010::17AS30148 SUCURI-SEC - Sucuri, US AS30148 SUCURI-SEC - Sucuri, US AS30148 SUCURI-SEC - Sucuri, US192.161.0.17 193.19.225.17 2a02:fe80:2010::17

Checks

  • ✓ 4 nameservers #6
    Delegated to 12.sucuridns.com, 13.sucuridns.com, 16.sucuridns.com, 17.sucuridns.com.
  • ✓ 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: 12.sucuridns.com (glue 192.161.0.12, 2a02:fe80:2010::12, zone 192.161.0.12, 193.19.225.12, 2a02:fe80:2010::12); 13.sucuridns.com (glue 192.161.0.13, 2a02:fe80:2010::13, zone 193.19.225.13, 192.161.0.13, 2a02:fe80:2010::13). 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 2a02:fe80:2010::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS30148 (SUCURI-SEC - Sucuri, US): 12 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • 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

info

12 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
12.sucuridns.com 192.161.0.12NOERROR, 3 ms, authoritativenoyes / yesrefused-
12.sucuridns.com 193.19.225.12NOERROR, 4 ms, authoritativenoyes / yesrefused-
12.sucuridns.com 2a02:fe80:2010::12NOERROR, 4 ms, authoritativenoyes / yesrefused-
13.sucuridns.com 193.19.225.13NOERROR, 4 ms, authoritativenoyes / yesrefused-
13.sucuridns.com 192.161.0.13NOERROR, 4 ms, authoritativenoyes / yesrefused-
13.sucuridns.com 2a02:fe80:2010::13NOERROR, 4 ms, authoritativenoyes / yesrefusedSucuri DNS
16.sucuridns.com 193.19.225.16NOERROR, 4 ms, authoritativenoyes / yesrefusedSucuri DNS
16.sucuridns.com 192.161.0.16NOERROR, 5 ms, authoritativenoyes / yesrefusedSucuri DNS
16.sucuridns.com 2a02:fe80:2010::16NOERROR, 4 ms, authoritativenoyes / yesrefusedSucuri DNS
17.sucuridns.com 193.19.225.17NOERROR, 3 ms, authoritativenoyes / yesrefusedSucuri DNS
17.sucuridns.com 192.161.0.17NOERROR, 4 ms, authoritativenoyes / yesrefused-
17.sucuridns.com 2a02:fe80:2010::17NOERROR, 4 ms, authoritativenoyes / yesrefusedSucuri DNS

Checks

  • ✓ All respond #14
    All 12 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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: 13.sucuridns.com: "Sucuri DNS"; 16.sucuridns.com: "Sucuri DNS"; 17.sucuridns.com: "Sucuri DNS".
    #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

info

serial 2023042613 · primary 10.sucuridns.com

Found

Primary (MNAME)
10.sucuridns.com
Contact (RNAME)
soc.sucuri.net
Serial
2023042613
Refresh / retry
14400 s / 7200 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
12.sucuridns.com (192.161.0.12)2023042613
12.sucuridns.com (193.19.225.12)2023042613
12.sucuridns.com (2a02:fe80:2010::12)2023042613
13.sucuridns.com (193.19.225.13)2023042613
13.sucuridns.com (192.161.0.13)2023042613
13.sucuridns.com (2a02:fe80:2010::13)2023042613
16.sucuridns.com (193.19.225.16)2023042613
16.sucuridns.com (192.161.0.16)2023042613
16.sucuridns.com (2a02:fe80:2010::16)2023042613
17.sucuridns.com (193.19.225.17)2023042613
17.sucuridns.com (192.161.0.17)2023042613
17.sucuridns.com (2a02:fe80:2010::17)2023042613

Checks

  • ✓ Serial 2023042613 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 2h, expire 14d, negative TTL 1d.
  • i
    Hidden master
    The primary nameserver 10.sucuridns.com is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact soc@sucuri.net #25
    The SOA RNAME soc.sucuri.net means soc@sucuri.net.
  • ✓ Date-based serial #26
    The serial 2023042613 follows the YYYYMMDDnn convention (2023-04-26).

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

10 records at the apex

Found

Read from
192.161.0.12:53
TypeValueTTL
SOA10.sucuridns.com. soc.sucuri.net. 2023042613 14400 7200 1209600 864007200
NS16.sucuridns.com.7200
NS12.sucuridns.com.7200
NS13.sucuridns.com.7200
NS17.sucuridns.com.7200
A192.124.249.14360
MX1 aspmx.l.google.com.7200
TXT"google-site-verification=h20oK2xXpUiV2tnmQIyh9BbdV7tcjVdutZCMyCk0o3w"3600
TXT"google-site-verification=FYp_UB9k7yYRwohlN8otPAh494AuVivzHekJVerK3Go"3600
TXT"v=spf1 +ip4:66.96.84.154 +include:_spf.google.com ~all"3600

Checks

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