View on GitHub

DNSViz: A DNS visualization tool

sparkasse.bank

« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Secure (2)
  • sparkasse.bank/NS
  • sparkasse.bank/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 33853)
  • bank/DNSKEY (alg 8, id 24451)
  • bank/DNSKEY (alg 8, id 31071)
  • bank/DS (alg 8, id 24451)
  • bank/DS (alg 8, id 24451)
  • sparkasse.bank/DNSKEY (alg 8, id 3694)
  • sparkasse.bank/DNSKEY (alg 8, id 55218)
  • sparkasse.bank/DNSKEY (alg 8, id 6618)
  • sparkasse.bank/DS (alg 8, id 1033)
  • sparkasse.bank/DS (alg 8, id 3694)
Non_existent (1)
  • sparkasse.bank/DNSKEY (alg 8, id 1033)

Delegation statusDelegation status

Secure (2)
  • . to bank
  • bank to sparkasse.bank

NoticesNotices

Errors (2)
  • bank/DS (alg 8, id 24451): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bank/DS (alg 8, id 24451): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
Warnings (2)
  • bank/DS (alg 8, id 24451): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • bank/DS (alg 8, id 24451): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.

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