View on GitHub

DNSViz: A DNS visualization tool

diabetescommittee.gov

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

RRset statusRRset status

Secure (6)
  • diabetescommittee.gov/A
  • diabetescommittee.gov/AAAA
  • diabetescommittee.gov/NS
  • diabetescommittee.gov/NSEC3PARAM
  • diabetescommittee.gov/SOA
  • diabetescommittee.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (14)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 9799)
  • diabetescommittee.gov/DNSKEY (alg 7, id 27120)
  • diabetescommittee.gov/DNSKEY (alg 7, id 29390)
  • diabetescommittee.gov/DNSKEY (alg 7, id 37550)
  • diabetescommittee.gov/DNSKEY (alg 7, id 44673)
  • diabetescommittee.gov/DNSKEY (alg 7, id 48903)
  • diabetescommittee.gov/DNSKEY (alg 8, id 51454)
  • diabetescommittee.gov/DS (alg 7, id 48903)
  • diabetescommittee.gov/DS (alg 7, id 48903)
  • diabetescommittee.gov/DS (alg 7, id 62811)
  • gov/DNSKEY (alg 8, id 7030)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
Non_existent (1)
  • diabetescommittee.gov/DNSKEY (alg 7, id 62811)

Delegation statusDelegation status

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

NoticesNotices

Errors (9)
  • diabetescommittee.gov/A: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (128.231.64.1, 128.231.128.251, 165.112.4.230, 2607:f220:402:1801::a570:4e6, 2607:f220:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D_KN)
  • diabetescommittee.gov/AAAA: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (128.231.64.1, 128.231.128.251, 165.112.4.230, 2607:f220:402:1801::a570:4e6, 2607:f220:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D_KN)
  • diabetescommittee.gov/NS: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (128.231.64.1, 128.231.128.251, 165.112.4.230, 2607:f220:402:1801::a570:4e6, 2607:f220:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D_KN)
  • diabetescommittee.gov/NSEC3PARAM: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (128.231.64.1, 128.231.128.251, 165.112.4.230, 2607:f220:402:1801::a570:4e6, 2607:f220:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D_KN)
  • diabetescommittee.gov/SOA: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (128.231.64.1, 128.231.128.251, 165.112.4.230, 2607:f220:402:1801::a570:4e6, 2607:f220:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • diabetescommittee.gov/TXT: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (128.231.64.1, 128.231.128.251, 165.112.4.230, 2607:f220:402:1801::a570:4e6, 2607:f220:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D_KN)
  • diabetescommittee.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • 1pjexu8so9.diabetescommittee.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • diabetescommittee.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (52)
  • RRSIG diabetescommittee.gov/A alg 7, id 29390: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/A alg 7, id 37550: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/AAAA alg 7, id 29390: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/AAAA alg 7, id 37550: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 27120: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 27120: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 27120: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 27120: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 27120: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 27120: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 29390: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 29390: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 29390: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 29390: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 29390: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 29390: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 37550: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 37550: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 37550: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 37550: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 37550: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 37550: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 44673: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 44673: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 44673: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 44673: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 44673: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 44673: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 48903: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 48903: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 48903: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 48903: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 48903: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/DNSKEY alg 7, id 48903: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/NS alg 7, id 29390: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/NS alg 7, id 37550: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/NSEC3PARAM alg 7, id 29390: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/SOA alg 7, id 29390: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/SOA alg 7, id 37550: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/TXT alg 7, id 29390: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG diabetescommittee.gov/TXT alg 7, id 37550: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • diabetescommittee.gov/DS (alg 7, id 48903): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • diabetescommittee.gov/DS (alg 7, id 48903): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • diabetescommittee.gov/DS (alg 7, id 48903): 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.
  • diabetescommittee.gov/DS (alg 7, id 48903): 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 to diabetescommittee.gov: Authoritative AAAA records exist for ns.nih.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • gov to diabetescommittee.gov: Authoritative AAAA records exist for ns2.nih.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • gov to diabetescommittee.gov: Authoritative AAAA records exist for ns3.nih.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • diabetescommittee.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 1pjexu8so9.diabetescommittee.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • diabetescommittee.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • diabetescommittee.gov/DNSKEY 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