View on GitHub

DNSViz: A DNS visualization tool

santanderrio.com.ar

Updated: 2020-09-08 23:11:20 UTC (1565 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (5)
  • santanderrio.com.ar/A
  • santanderrio.com.ar/MX
  • santanderrio.com.ar/NS
  • santanderrio.com.ar/SOA
  • santanderrio.com.ar/TXT
Secure (2)
  • com.ar/SOA
  • com.ar/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (9)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • 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 statusDelegation status

Insecure (1)
  • com.ar to santanderrio.com.ar
Secure (2)
  • . to ar
  • ar to com.ar

NoticesNotices

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.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph