View on GitHub

DNSViz: A DNS visualization tool

ugent.be

Updated: 2023-04-19 11:38:24 UTC (621 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)
  • 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 (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • NSEC3 proving non-existence of ugent.be/DS
  • be/DNSKEY (alg 8, id 12664)
  • be/DNSKEY (alg 8, id 17184)
  • be/DNSKEY (alg 8, id 19206)
  • be/DNSKEY (alg 8, id 46029)
  • be/DNSKEY (alg 8, id 52756)
  • be/DS (alg 8, id 12664)
  • be/DS (alg 8, id 52756)

Delegation statusDelegation status

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

NoticesNotices

Warnings (2)
  • 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): ugdns3.ugent.be, ugdns2.ugent.be, 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.

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