malavida.com

Checked 22 October 2026, 09:42 UTC · via 8.8.8.8
!Passed with warnings
25 passed 2 warnings 0 failed 4 info

Registration

info

.com generic · Soluciones Corporativas IP, SL · expires 2029-05-31

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Soluciones Corporativas IP, SL
Registered
31 May 2001
Last changed
9 April 2024
Expires
31 May 2029
Status
client transfer prohibited
Registry nameservers
a1-3.akam.net, a2-64.akam.net, a24-65.akam.net, a26-66.akam.net, a3-67.akam.net, a7-64.akam.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 2029-05-31 #3
    The registration is valid until 2029-05-31 (952 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

info

a1-3.akam.net, a2-64.akam.net, a24-65.akam.net, a26-66.akam.net, a3-67.akam.net, a7-64.akam.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
a1-3.akam.net, a2-64.akam.net, a24-65.akam.net, a26-66.akam.net, a3-67.akam.net, a7-64.akam.net
NS in the zone
a1-3.akam.net, a2-64.akam.net, a24-65.akam.net, a26-66.akam.net, a3-67.akam.net, a7-64.akam.net
NameserverAddressesNetwork (AS)Glue
a1-3.akam.net193.108.91.3 2600:1401:2::3AS20940 AKAMAI-ASN1 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a2-64.akam.net95.100.174.64 2600:1480:7000::40AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a24-65.akam.net2.16.130.65 2600:1480:9800::41AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a26-66.akam.net23.74.25.66 2600:1480:b800::42AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a3-67.akam.net96.7.49.67 2600:1408:1c::43AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a7-64.akam.net23.61.199.64 2600:1406:32::40AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-

Checks

  • ✓ 6 nameservers #6
    Delegated to a1-3.akam.net, a2-64.akam.net, a24-65.akam.net, a26-66.akam.net, a3-67.akam.net, a7-64.akam.net.
  • ✓ 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 6 IPv4 /24s and 6 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS20940 (AKAMAI-ASN1 - Akamai International B.V., NL): 1 address; AS21342 (AKAMAI-ASN2 - Akamai International B.V., NL): 11 addresses.
  • 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

warn

12 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
a1-3.akam.net 193.108.91.3NOERROR, 3 ms, authoritativenoyes / yesrefused41824.6
a1-3.akam.net 2600:1401:2::3NOERROR, 5 ms, authoritativenoyes / yesrefused41824.10
a2-64.akam.net 95.100.174.64NOERROR, 3 ms, authoritativenoyes / yesrefused48878.29
a2-64.akam.net 2600:1480:7000::40NOERROR, 3 ms, authoritativenoyes / yesrefused48878.32
a24-65.akam.net 2.16.130.65NOERROR, 4 ms, authoritativenoyes / yesrefused48878.30
a24-65.akam.net 2600:1480:9800::41NOERROR, 4 ms, authoritativenoyes / yesrefused48878.33
a26-66.akam.net 23.74.25.66NOERROR, 3 ms, authoritativenoyes / yesrefused48878.31
a26-66.akam.net 2600:1480:b800::42NOERROR, 4 ms, authoritativenoyes / yesrefused48878.31
a3-67.akam.net 96.7.49.67NOERROR, 3 ms, authoritativenoyes / yesrefused41824.7
a3-67.akam.net 2600:1408:1c::43NOERROR, 4 ms, authoritativenoyes / yesrefused41824.4
a7-64.akam.net 23.61.199.64NOERROR, 3 ms, authoritativenoyes / yesrefused41824.10
a7-64.akam.net 2600:1406:32::40NOERROR, 4 ms, authoritativenoyes / yesrefused41824.10

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-3.akam.net: "41824.6"; a1-3.akam.net: "41824.10"; a2-64.akam.net: "48878.29"; a2-64.akam.net: "48878.32"; a24-65.akam.net: "48878.30"; a24-65.akam.net: "48878.33"; a26-66.akam.net: "48878.31"; a3-67.akam.net: "41824.7"; a3-67.akam.net: "41824.4"; a7-64.akam.net: "41824.10". 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

pass

serial 2017021508 · primary a1-3.akam.net

Found

Primary (MNAME)
a1-3.akam.net
Contact (RNAME)
dnsadmin.malavida.com
Serial
2017021508
Refresh / retry
3200 s / 1600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
a1-3.akam.net (193.108.91.3)2017021508
a1-3.akam.net (2600:1401:2::3)2017021508
a2-64.akam.net (95.100.174.64)2017021508
a2-64.akam.net (2600:1480:7000::40)2017021508
a24-65.akam.net (2.16.130.65)2017021508
a24-65.akam.net (2600:1480:9800::41)2017021508
a26-66.akam.net (23.74.25.66)2017021508
a26-66.akam.net (2600:1480:b800::42)2017021508
a3-67.akam.net (96.7.49.67)2017021508
a3-67.akam.net (2600:1408:1c::43)2017021508
a7-64.akam.net (23.61.199.64)2017021508
a7-64.akam.net (2600:1406:32::40)2017021508

Checks

  • ✓ Serial 2017021508 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 53m20s, retry 26m40s, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver a1-3.akam.net is one of the listed nameservers.
  • ✓ Contact dnsadmin@malavida.com #25
    The SOA RNAME dnsadmin.malavida.com means dnsadmin@malavida.com.
  • ✓ Date-based serial #26
    The serial 2017021508 follows the YYYYMMDDnn convention (2017-02-15).

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

13 records at the apex

Found

Read from
193.108.91.3:53
TypeValueTTL
SOAa1-3.akam.net. dnsadmin.malavida.com. 2017021508 3200 1600 604800 3600300
NSa1-3.akam.net.300
NSa26-66.akam.net.300
NSa24-65.akam.net.300
NSa3-67.akam.net.300
NSa2-64.akam.net.300
NSa7-64.akam.net.300
A91.192.108.161300
AAAA2a00:1d70:c01c::108:161300
MX10 mail.malavida.com.300
TXT"ahrefs-site-verification_21564fe34ec8ccb9345948c303eb13c70f3efdce35742d680b2c0b8bbab630d0"300
TXT"google-site-verification=_Wttmva5F1VUKsMibdKQINLAz5ucVnSrhtZPPdMorRM"300
TXT"v=spf1 mx include:_netblocks.google.com include:_netblocks2.google.com include:_netblocks3.google.com a:mail.malavida.com ip4:195.78.228.0/22 ip4:77.81.116.0/22 ip4:91.192.108.0/22 ip4:93.93.64.0/21 ip4:5.145.168.0/21 ip6:2a00:1d70::/32 -all"300

Checks

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