View on GitHub

DNSViz: A DNS visualization tool

hhsops.gov

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

RRset statusRRset status

Secure (8)
  • hhsops.gov/A
  • hhsops.gov/AAAA
  • hhsops.gov/NS
  • hhsops.gov/NSEC3PARAM
  • hhsops.gov/NSEC3PARAM
  • hhsops.gov/NSEC3PARAM
  • hhsops.gov/SOA
  • hhsops.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (21)
  • ./DNSKEY (alg 8, id 14748)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • gov/DNSKEY (alg 8, id 57735)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • hhsops.gov/DNSKEY (alg 8, id 12895)
  • hhsops.gov/DNSKEY (alg 8, id 14104)
  • hhsops.gov/DNSKEY (alg 8, id 17274)
  • hhsops.gov/DNSKEY (alg 8, id 38146)
  • hhsops.gov/DNSKEY (alg 8, id 3909)
  • hhsops.gov/DNSKEY (alg 8, id 4024)
  • hhsops.gov/DNSKEY (alg 8, id 56955)
  • hhsops.gov/DS (alg 8, id 12895)
  • hhsops.gov/DS (alg 8, id 12895)
  • hhsops.gov/DS (alg 8, id 14104)
  • hhsops.gov/DS (alg 8, id 14104)
  • hhsops.gov/DS (alg 8, id 38146)
  • hhsops.gov/DS (alg 8, id 38146)
  • hhsops.gov/DS (alg 8, id 4024)
  • hhsops.gov/DS (alg 8, id 4024)

Delegation statusDelegation status

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

NoticesNotices

Errors (14)
  • RRSIG hhsops.gov/NSEC3PARAM alg 8, id 3909: With a TTL of 3600 the RRSIG RR can be in the cache of a non-validating resolver until 54 minutes after it expires at 2021-09-27 17:36:54+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG hhsops.gov/NSEC3PARAM alg 8, id 3909: With a TTL of 3600 the RRSIG RR can be in the cache of a non-validating resolver until 54 minutes after it expires at 2021-09-27 17:36:54+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG hhsops.gov/NSEC3PARAM alg 8, id 3909: With a TTL of 3600 the RRSIG RR can be in the cache of a non-validating resolver until 54 minutes after it expires at 2021-09-27 17:36:54+00:00. See RFC 4035, Sec. 5.3.3.
  • hhsops.gov/DS (alg 8, id 12895): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • hhsops.gov/DS (alg 8, id 12895): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • hhsops.gov/DS (alg 8, id 14104): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • hhsops.gov/DS (alg 8, id 14104): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • hhsops.gov/DS (alg 8, id 38146): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • hhsops.gov/DS (alg 8, id 38146): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • hhsops.gov/DS (alg 8, id 4024): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • hhsops.gov/DS (alg 8, id 4024): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • x53ot0rykq.hhsops.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • hhsops.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • hhsops.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
  • hhsops.gov/DS (alg 8, id 12895): 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.
  • hhsops.gov/DS (alg 8, id 12895): 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.
  • hhsops.gov/DS (alg 8, id 14104): 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.
  • hhsops.gov/DS (alg 8, id 14104): 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.
  • hhsops.gov/DS (alg 8, id 38146): 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.
  • hhsops.gov/DS (alg 8, id 38146): 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.
  • hhsops.gov/DS (alg 8, id 4024): 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.
  • hhsops.gov/DS (alg 8, id 4024): 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.
  • x53ot0rykq.hhsops.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • hhsops.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • hhsops.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