View on GitHub

DNSViz: A DNS visualization tool

bnl.gov

« 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)
  • bnl.gov/A
  • bnl.gov/MX
  • bnl.gov/NS
  • bnl.gov/SOA
  • bnl.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (17)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 48903)
  • bnl.gov/DNSKEY (alg 7, id 17217)
  • bnl.gov/DNSKEY (alg 7, id 19104)
  • bnl.gov/DNSKEY (alg 7, id 30666)
  • bnl.gov/DNSKEY (alg 7, id 34596)
  • bnl.gov/DNSKEY (alg 7, id 9399)
  • bnl.gov/DS (alg 7, id 19104)
  • bnl.gov/DS (alg 7, id 19104)
  • bnl.gov/DS (alg 7, id 30666)
  • bnl.gov/DS (alg 7, id 30666)
  • bnl.gov/DS (alg 7, id 34596)
  • bnl.gov/DS (alg 7, id 34596)
  • gov/DNSKEY (alg 8, id 40176)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

Secure (2)
  • . to gov
  • gov to bnl.gov

NoticesNotices

Errors (4)
  • gov/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:500:12::d0d, UDP_-_NOEDNS_)
  • bnl.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • 1ktpz0fqdm.bnl.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • bnl.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (35)
  • RRSIG bnl.gov/A alg 7, id 9399: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bnl.gov/DNSKEY alg 7, id 30666: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bnl.gov/DNSKEY alg 7, id 30666: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bnl.gov/DNSKEY alg 7, id 30666: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bnl.gov/DNSKEY alg 7, id 30666: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bnl.gov/DNSKEY alg 7, id 30666: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bnl.gov/DNSKEY alg 7, id 9399: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bnl.gov/DNSKEY alg 7, id 9399: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bnl.gov/DNSKEY alg 7, id 9399: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bnl.gov/DNSKEY alg 7, id 9399: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bnl.gov/DNSKEY alg 7, id 9399: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bnl.gov/MX alg 7, id 9399: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bnl.gov/NS alg 7, id 9399: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bnl.gov/SOA alg 7, id 9399: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bnl.gov/TXT alg 7, id 9399: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • bnl.gov/DS (alg 7, id 19104): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bnl.gov/DS (alg 7, id 19104): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bnl.gov/DS (alg 7, id 19104): 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.
  • bnl.gov/DS (alg 7, id 19104): 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.
  • bnl.gov/DS (alg 7, id 30666): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bnl.gov/DS (alg 7, id 30666): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bnl.gov/DS (alg 7, id 30666): 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.
  • bnl.gov/DS (alg 7, id 30666): 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.
  • bnl.gov/DS (alg 7, id 34596): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bnl.gov/DS (alg 7, id 34596): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bnl.gov/DS (alg 7, id 34596): 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.
  • bnl.gov/DS (alg 7, id 34596): 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.
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): 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.
  • gov/DS (alg 8, id 7698): 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.
  • bnl.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • bnl.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 1ktpz0fqdm.bnl.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • bnl.gov/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