View on GitHub

DNSViz: A DNS visualization tool

tamu.edu

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

RRset statusRRset status

Secure (5)
  • tamu.edu/A
  • tamu.edu/MX
  • tamu.edu/NS
  • tamu.edu/SOA
  • tamu.edu/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 9799)
  • edu/DNSKEY (alg 8, id 28065)
  • edu/DNSKEY (alg 8, id 47450)
  • edu/DS (alg 8, id 28065)
  • tamu.edu/DNSKEY (alg 5, id 31695)
  • tamu.edu/DNSKEY (alg 5, id 32956)
  • tamu.edu/DNSKEY (alg 5, id 49980)
  • tamu.edu/DNSKEY (alg 5, id 61533)
  • tamu.edu/DS (alg 5, id 32956)
  • tamu.edu/DS (alg 5, id 32956)
  • tamu.edu/DS (alg 5, id 42433)
Non_existent (1)
  • tamu.edu/DNSKEY (alg 5, id 42433)

Delegation statusDelegation status

Secure (2)
  • . to edu
  • edu to tamu.edu

NoticesNotices

Warnings (26)
  • RRSIG tamu.edu/A alg 5, id 31695: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tamu.edu/DNSKEY alg 5, id 31695: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tamu.edu/DNSKEY alg 5, id 31695: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tamu.edu/DNSKEY alg 5, id 31695: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tamu.edu/DNSKEY alg 5, id 31695: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tamu.edu/DNSKEY alg 5, id 32956: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tamu.edu/DNSKEY alg 5, id 32956: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tamu.edu/DNSKEY alg 5, id 32956: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tamu.edu/DNSKEY alg 5, id 32956: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tamu.edu/MX alg 5, id 31695: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tamu.edu/NS alg 5, id 31695: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tamu.edu/SOA alg 5, id 31695: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tamu.edu/TXT alg 5, id 31695: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • tamu.edu/DS (alg 5, id 32956): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • tamu.edu/DS (alg 5, id 32956): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • tamu.edu/DS (alg 5, id 32956): 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.
  • tamu.edu/DS (alg 5, id 32956): 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.
  • tamu.edu/DS (alg 5, id 42433): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • tamu.edu/DS (alg 5, id 42433): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • tamu.edu/DS (alg 5, id 42433): 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.
  • tamu.edu/DS (alg 5, id 42433): 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.
  • tamu.edu/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 23pgclez49.tamu.edu/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • tamu.edu/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • tamu.edu/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • tamu.edu/NSEC3PARAM 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