View on GitHub

DNSViz: A DNS visualization tool

brainhealth.gov

Updated: 2020-12-14 18:11:54 UTC (1437 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

Secure (4)
  • brainhealth.gov/A
  • brainhealth.gov/NS
  • brainhealth.gov/SOA
  • brainhealth.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • brainhealth.gov/DNSKEY (alg 7, id 19296)
  • brainhealth.gov/DNSKEY (alg 7, id 52568)
  • brainhealth.gov/DNSKEY (alg 7, id 54135)
  • brainhealth.gov/DS (alg 7, id 19296)
  • brainhealth.gov/DS (alg 7, id 19296)
  • brainhealth.gov/DS (alg 7, id 24096)
  • gov/DNSKEY (alg 8, id 15489)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
Non_existent (1)
  • brainhealth.gov/DNSKEY (alg 7, id 24096)

Delegation statusDelegation status

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

NoticesNotices

Errors (4)
  • brainhealth.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • f8hzc4mr70.brainhealth.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • brainhealth.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • brainhealth.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (29)
  • RRSIG brainhealth.gov/A alg 7, id 52568: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG brainhealth.gov/DNSKEY alg 7, id 19296: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG brainhealth.gov/DNSKEY alg 7, id 19296: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG brainhealth.gov/DNSKEY alg 7, id 19296: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG brainhealth.gov/DNSKEY alg 7, id 52568: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG brainhealth.gov/DNSKEY alg 7, id 52568: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG brainhealth.gov/DNSKEY alg 7, id 52568: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG brainhealth.gov/DNSKEY alg 7, id 54135: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG brainhealth.gov/DNSKEY alg 7, id 54135: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG brainhealth.gov/DNSKEY alg 7, id 54135: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG brainhealth.gov/NS alg 7, id 52568: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG brainhealth.gov/SOA alg 7, id 52568: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG brainhealth.gov/TXT alg 7, id 52568: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • brainhealth.gov/DNSKEY (alg 7, id 19296): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2607:f220:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D_K)
  • brainhealth.gov/DNSKEY (alg 7, id 52568): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2607:f220:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D_K)
  • brainhealth.gov/DNSKEY (alg 7, id 54135): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2607:f220:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D_K)
  • brainhealth.gov/DS (alg 7, id 19296): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • brainhealth.gov/DS (alg 7, id 19296): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • brainhealth.gov/DS (alg 7, id 19296): 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.
  • brainhealth.gov/DS (alg 7, id 19296): 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.
  • brainhealth.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • f8hzc4mr70.brainhealth.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • brainhealth.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • brainhealth.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • brainhealth.gov/CNAME 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