View on GitHub

DNSViz: A DNS visualization tool

dhhs.gov

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 (9)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • dhhs.gov/DS (alg 8, id 10645)
  • dhhs.gov/DS (alg 8, id 33209)
  • gov/DNSKEY (alg 8, id 15489)
  • gov/DNSKEY (alg 8, id 26665)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
Non_existent (2)
  • dhhs.gov/DNSKEY (alg 8, id 10645)
  • dhhs.gov/DNSKEY (alg 8, id 33209)

Delegation statusDelegation status

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

NoticesNotices

Errors (5)
  • dhhs.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (158.74.30.98, 158.74.30.99, 158.74.30.102, 158.74.30.103, 2607:f220:0:1::2a, 2607:f220:0:1::2b, 2607:f220:0:1::2c, 2607:f220:0:1::2d)
  • dhhs.gov zone: There was an error resolving the following NS name(s) to address(es): rh202ns1.355.dhhs.gov, rh202ns2.355.dhhs.gov, rh120ns1.368.dhhs.gov, rh120ns2.368.dhhs.gov
  • dhhs.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (158.74.30.98, 158.74.30.99, 158.74.30.102, 158.74.30.103, 2607:f220:0:1::2a, 2607:f220:0:1::2b, 2607:f220:0:1::2c, 2607:f220:0:1::2d, UDP_-_NOEDNS_)
  • dhhs.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (158.74.30.98, 158.74.30.99, 158.74.30.102, 158.74.30.103, 2607:f220:0:1::2a, 2607:f220:0:1::2b, 2607:f220:0:1::2c, 2607:f220:0:1::2d, UDP_-_NOEDNS_)
  • gov to dhhs.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.
Warnings (8)
  • dhhs.gov/DS (alg 8, id 33209): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • dhhs.gov/DS (alg 8, id 33209): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • dhhs.gov/DS (alg 8, id 33209): 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.
  • dhhs.gov/DS (alg 8, id 33209): 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.

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