NSEC3 proving non-existence of santanderrio.com.ar/DS
ar/DNSKEY (alg 8, id 14574)
ar/DNSKEY (alg 8, id 19606)
ar/DS (alg 8, id 19606)
com.ar/DNSKEY (alg 8, id 1474)
com.ar/DNSKEY (alg 8, id 19503)
com.ar/DS (alg 8, id 1474)
Delegation status
Insecure (1)
com.ar to santanderrio.com.ar
Secure (2)
. to ar
ar to com.ar
Notices
Errors (7)
NSEC3 proving non-existence of santanderrio.com.ar/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of santanderrio.com.ar/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
santanderrio.com.ar zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (200.61.38.33, 200.61.38.43)
santanderrio.com.ar/DNSKEY: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (200.61.38.43, TCP_-_EDNS0_4096_D_K)
santanderrio.com.ar/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (200.61.38.33, 200.61.38.43, TCP_-_EDNS0_4096_D)
santanderrio.com.ar/DS has errors; select the "Denial of existence" DNSSEC option to see them.
santanderrio.com.ar/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
ar to com.ar: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the ar zone): f.dns.ar See RFC 1034, Sec. 4.2.2.
com.ar to santanderrio.com.ar: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the com.ar zone): fry.bancorio.com.ar, zoidberg.bancorio.com.ar See RFC 1034, Sec. 4.2.2.
com.ar to santanderrio.com.ar: The following NS name(s) were found in the delegation NS RRset (i.e., in the com.ar zone), but not in the authoritative NS RRset: fry.santanderrio.com.ar, zoidberg.santanderrio.com.ar See RFC 1034, Sec. 4.2.2.
com.ar/DS (alg 8, id 1474): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
com.ar/DS (alg 8, id 1474): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.