View on GitHub

DNSViz: A DNS visualization tool

diabetescommittee.gov

Updated: 2025-05-21 11:34:14 UTC (203 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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 38696)
  • ./DNSKEY (alg 8, id 53148)
  • diabetescommittee.gov/DS (alg 8, id 27844)
  • diabetescommittee.gov/DS (alg 8, id 47659)
  • gov/DNSKEY (alg 13, id 2536)
  • gov/DNSKEY (alg 13, id 35496)
  • gov/DS (alg 13, id 2536)
Non_existent (2)
  • diabetescommittee.gov/DNSKEY (alg 8, id 27844)
  • diabetescommittee.gov/DNSKEY (alg 8, id 47659)

Delegation statusDelegation status

Bogus (1)
  • gov to diabetescommittee.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (22)
  • diabetescommittee.gov zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (128.231.64.1, 128.231.128.251, 165.112.4.230)
  • diabetescommittee.gov zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (128.231.64.1, 128.231.128.251, 165.112.4.230)
  • diabetescommittee.gov/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (128.231.64.1, 128.231.128.251, 165.112.4.230, UDP_-_EDNS0_4096_D_KN)
  • diabetescommittee.gov/AAAA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (128.231.128.251, UDP_-_NOEDNS_)
  • diabetescommittee.gov/AAAA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (128.231.64.1, 165.112.4.230, UDP_-_EDNS0_4096_D_KN)
  • diabetescommittee.gov/CDNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (128.231.64.1, 128.231.128.251, 165.112.4.230, UDP_-_NOEDNS_)
  • diabetescommittee.gov/CDS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (128.231.64.1, 128.231.128.251, 165.112.4.230, UDP_-_NOEDNS_)
  • diabetescommittee.gov/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (128.231.64.1, 128.231.128.251, 165.112.4.230, UDP_-_NOEDNS_)
  • diabetescommittee.gov/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (128.231.64.1, 128.231.128.251, 165.112.4.230, UDP_-_EDNS0_512_D_KN)
  • diabetescommittee.gov/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (128.231.128.251, 165.112.4.230, UDP_-_NOEDNS_)
  • diabetescommittee.gov/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (128.231.64.1, 128.231.128.251, 165.112.4.230, UDP_-_EDNS0_512_D_KN)
  • diabetescommittee.gov/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (128.231.64.1, UDP_-_EDNS0_4096_D_KN)
  • diabetescommittee.gov/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (128.231.64.1, 128.231.128.251, 165.112.4.230, UDP_-_EDNS0_4096_D_KN)
  • diabetescommittee.gov/NSEC3PARAM: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (128.231.64.1, 128.231.128.251, 165.112.4.230, UDP_-_EDNS0_4096_D_KN)
  • diabetescommittee.gov/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (128.231.64.1, 128.231.128.251, 165.112.4.230, UDP_-_NOEDNS_)
  • diabetescommittee.gov/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (128.231.64.1, 128.231.128.251, 165.112.4.230, TCP_-_EDNS0_4096_D_N)
  • diabetescommittee.gov/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (128.231.64.1, 128.231.128.251, 165.112.4.230, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • diabetescommittee.gov/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (128.231.64.1, 128.231.128.251, 165.112.4.230, UDP_-_NOEDNS_)
  • gov to diabetescommittee.gov: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11.
  • diabetescommittee.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • gy493.umxv3.diabetescommittee.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • diabetescommittee.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
  • diabetescommittee.gov/DS (alg 8, id 27844): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • diabetescommittee.gov/DS (alg 8, id 27844): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • diabetescommittee.gov/DS (alg 8, id 27844): 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 8, id 27844): 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 8, id 47659): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • diabetescommittee.gov/DS (alg 8, id 47659): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • diabetescommittee.gov/DS (alg 8, id 47659): 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 8, id 47659): 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.

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