View on GitHub

DNSViz: A DNS visualization tool

pms.psc.gov

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

RRset statusRRset status

Insecure (2)
  • pms.ha.psc.gov/A
  • pms.psc.gov/CNAME
Secure (1)
  • gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (10)
  • ha.psc.gov/DNSKEY (alg 8, id 24922)
  • ha.psc.gov/DNSKEY (alg 8, id 25716)
  • ha.psc.gov/DNSKEY (alg 8, id 47521)
  • ha.psc.gov/DNSKEY (alg 8, id 51873)
  • ha.psc.gov/DS (alg 8, id 24922)
  • ha.psc.gov/DS (alg 8, id 51034)
  • psc.gov/DNSKEY (alg 8, id 30544)
  • psc.gov/DNSKEY (alg 8, id 42917)
  • psc.gov/DNSKEY (alg 8, id 45940)
  • psc.gov/DNSKEY (alg 8, id 5664)
Secure (8)
  • ./DNSKEY (alg 8, id 11019)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC3 proving non-existence of psc.gov/DS
  • gov/DNSKEY (alg 8, id 10104)
  • gov/DNSKEY (alg 8, id 40921)
  • gov/DNSKEY (alg 8, id 64280)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
Non_existent (1)
  • ha.psc.gov/DNSKEY (alg 8, id 51034)

Delegation statusDelegation status

Insecure (1)
  • gov to psc.gov
Secure (2)
  • . to gov
  • psc.gov to ha.psc.gov

NoticesNotices

Errors (2)
  • NSEC3 proving non-existence of psc.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of psc.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
Warnings (7)
  • NSEC3 proving non-existence of psc.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of psc.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • ha.psc.gov/DS (alg 8, id 51034): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ha.psc.gov/DS (alg 8, id 51034): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ha.psc.gov/DS (alg 8, id 51034): 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.
  • ha.psc.gov/DS (alg 8, id 51034): 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.
  • psc.gov to ha.psc.gov: The following NS name(s) were found in the delegation NS RRset (i.e., in the psc.gov zone), but not in the authoritative NS RRset: ns2.ha.nih.gov See RFC 1034, Sec. 4.2.2.

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