View on GitHub

DNSViz: A DNS visualization tool

cerebrosano.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 (4)
  • cerebrosano.gov/A
  • cerebrosano.gov/NS
  • cerebrosano.gov/SOA
  • cerebrosano.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • cerebrosano.gov/DNSKEY (alg 7, id 23327)
  • cerebrosano.gov/DNSKEY (alg 7, id 25914)
  • cerebrosano.gov/DNSKEY (alg 7, id 58488)
  • cerebrosano.gov/DS (alg 7, id 58488)
  • cerebrosano.gov/DS (alg 7, id 58488)
  • cerebrosano.gov/DS (alg 7, id 65094)
  • 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)
  • cerebrosano.gov/DNSKEY (alg 7, id 65094)

Delegation statusDelegation status

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

NoticesNotices

Errors (4)
  • oxsgvp1a5b.cerebrosano.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • cerebrosano.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • cerebrosano.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • cerebrosano.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (33)
  • RRSIG cerebrosano.gov/A alg 7, id 23327: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cerebrosano.gov/DNSKEY alg 7, id 23327: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cerebrosano.gov/DNSKEY alg 7, id 23327: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cerebrosano.gov/DNSKEY alg 7, id 23327: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cerebrosano.gov/DNSKEY alg 7, id 25914: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cerebrosano.gov/DNSKEY alg 7, id 25914: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cerebrosano.gov/DNSKEY alg 7, id 25914: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cerebrosano.gov/DNSKEY alg 7, id 58488: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cerebrosano.gov/DNSKEY alg 7, id 58488: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cerebrosano.gov/DNSKEY alg 7, id 58488: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cerebrosano.gov/NS alg 7, id 23327: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cerebrosano.gov/SOA alg 7, id 23327: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cerebrosano.gov/TXT alg 7, id 23327: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • cerebrosano.gov/DNSKEY (alg 7, id 23327): 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. (128.231.64.1, 2607:f220:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D_K)
  • cerebrosano.gov/DNSKEY (alg 7, id 25914): 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. (128.231.64.1, 2607:f220:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D_K)
  • cerebrosano.gov/DNSKEY (alg 7, id 58488): 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. (128.231.64.1, 2607:f220:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D_K)
  • cerebrosano.gov/DS (alg 7, id 58488): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • cerebrosano.gov/DS (alg 7, id 58488): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • cerebrosano.gov/DS (alg 7, id 58488): 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.
  • cerebrosano.gov/DS (alg 7, id 58488): 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.
  • cerebrosano.gov/DS (alg 7, id 65094): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • cerebrosano.gov/DS (alg 7, id 65094): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • cerebrosano.gov/DS (alg 7, id 65094): 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.
  • cerebrosano.gov/DS (alg 7, id 65094): 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.
  • cerebrosano.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • oxsgvp1a5b.cerebrosano.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • cerebrosano.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • cerebrosano.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • cerebrosano.gov/MX 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