View on GitHub

DNSViz: A DNS visualization tool

kuleuven.be

« 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 (6)
  • kuleuven.be/A
  • kuleuven.be/AAAA
  • kuleuven.be/MX
  • kuleuven.be/NS
  • kuleuven.be/SOA
  • kuleuven.be/TXT
Secure (1)
  • be/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 48903)
  • NSEC3 proving non-existence of kuleuven.be/DS
  • be/DNSKEY (alg 8, id 12664)
  • be/DNSKEY (alg 8, id 2949)
  • be/DNSKEY (alg 8, id 32769)
  • be/DNSKEY (alg 8, id 47859)
  • be/DNSKEY (alg 8, id 52756)
  • be/DS (alg 8, id 12664)
  • be/DS (alg 8, id 12664)
  • be/DS (alg 8, id 52756)
  • be/DS (alg 8, id 52756)

Delegation statusDelegation status

Insecure (1)
  • be to kuleuven.be
Secure (1)
  • . to be

NoticesNotices

Errors (3)
  • NSEC3 proving non-existence of kuleuven.be/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 kuleuven.be/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • kuleuven.be/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (13)
  • NSEC3 proving non-existence of kuleuven.be/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of kuleuven.be/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • be to kuleuven.be: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (120.29.253.8, UDP_-_EDNS0_4096_D_K)
  • be/DNSKEY: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (120.29.253.8, UDP_-_EDNS0_512_D_K)
  • be/DS (alg 8, id 12664): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • be/DS (alg 8, id 12664): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • be/DS (alg 8, id 12664): 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.
  • be/DS (alg 8, id 12664): 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.
  • be/DS (alg 8, id 52756): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • be/DS (alg 8, id 52756): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • be/DS (alg 8, id 52756): 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.
  • be/DS (alg 8, id 52756): 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.
  • kuleuven.be/DS has warnings; select the "Denial of existence" DNSSEC option to see them.

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