View on GitHub

DNSViz: A DNS visualization tool

bradley.edu

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

RRset statusRRset status

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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (13)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • bradley.edu/DNSKEY (alg 10, id 31527)
  • bradley.edu/DNSKEY (alg 10, id 32079)
  • bradley.edu/DNSKEY (alg 10, id 46652)
  • bradley.edu/DNSKEY (alg 10, id 49748)
  • bradley.edu/DS (alg 10, id 31527)
  • bradley.edu/DS (alg 10, id 31527)
  • bradley.edu/DS (alg 10, id 32079)
  • bradley.edu/DS (alg 10, id 32079)
  • edu/DNSKEY (alg 8, id 28065)
  • edu/DNSKEY (alg 8, id 33233)
  • edu/DS (alg 8, id 28065)

Delegation statusDelegation status

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

NoticesNotices

Errors (3)
  • bradley.edu zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:550:1:a::d, 2001:550:1:b::d)
  • bradley.edu/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:550:1:a::d, 2001:550:1:b::d, UDP_-_NOEDNS_)
  • bradley.edu/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:550:1:a::d, 2001:550:1:b::d, UDP_-_NOEDNS_)
Warnings (34)
  • RRSIG bradley.edu/A alg 10, id 46652: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bradley.edu/A alg 10, id 49748: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bradley.edu/DNSKEY alg 10, id 32079: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bradley.edu/DNSKEY alg 10, id 32079: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bradley.edu/DNSKEY alg 10, id 32079: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bradley.edu/DNSKEY alg 10, id 32079: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bradley.edu/DNSKEY alg 10, id 46652: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bradley.edu/DNSKEY alg 10, id 46652: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bradley.edu/DNSKEY alg 10, id 46652: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bradley.edu/DNSKEY alg 10, id 46652: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bradley.edu/DNSKEY alg 10, id 49748: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bradley.edu/DNSKEY alg 10, id 49748: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bradley.edu/DNSKEY alg 10, id 49748: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bradley.edu/DNSKEY alg 10, id 49748: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bradley.edu/MX alg 10, id 46652: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bradley.edu/MX alg 10, id 49748: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bradley.edu/NS alg 10, id 46652: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bradley.edu/NS alg 10, id 49748: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bradley.edu/SOA alg 10, id 46652: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bradley.edu/SOA alg 10, id 49748: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bradley.edu/TXT alg 10, id 46652: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bradley.edu/TXT alg 10, id 49748: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • bradley.edu/DS (alg 10, id 31527): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bradley.edu/DS (alg 10, id 31527): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bradley.edu/DS (alg 10, id 31527): 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.
  • bradley.edu/DS (alg 10, id 31527): 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.
  • bradley.edu/DS (alg 10, id 32079): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bradley.edu/DS (alg 10, id 32079): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bradley.edu/DS (alg 10, id 32079): 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.
  • bradley.edu/DS (alg 10, id 32079): 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.
  • bradley.edu/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • bradley.edu/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 03vuxarw7y.bradley.edu/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • bradley.edu/AAAA 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