View on GitHub

DNSViz: A DNS visualization tool

ugent.be

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (5)
  • ugent.be/A
  • ugent.be/MX
  • ugent.be/NS
  • ugent.be/SOA
  • ugent.be/TXT
Secure (1)
  • be/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • NSEC3 proving non-existence of ugent.be/DS
  • be/DNSKEY (alg 8, id 12664)
  • be/DNSKEY (alg 8, id 32769)
  • be/DNSKEY (alg 8, id 41553)
  • 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 ugent.be
Secure (1)
  • . to be

NoticesNotices

Errors (3)
  • NSEC3 proving non-existence of ugent.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 ugent.be/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • ugent.be/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (13)
  • NSEC3 proving non-existence of ugent.be/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of ugent.be/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • be to ugent.be: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the be zone): ugdns1.ugent.be, ns.belnet.be See RFC 1034, Sec. 4.2.2.
  • be to ugent.be: The following NS name(s) were found in the delegation NS RRset (i.e., in the be zone), but not in the authoritative NS RRset: ns1.belnet.be, ns2.belnet.be, ns3.belnet.be See RFC 1034, Sec. 4.2.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): 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.
  • ugent.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