View on GitHub

DNSViz: A DNS visualization tool

treasury.fed.us

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

RRset statusRRset status

Insecure (5)
  • fed.us/SOA
  • treasury.fed.us/A
  • treasury.fed.us/NS
  • treasury.fed.us/SOA
  • treasury.fed.us/TXT
Secure (1)
  • us/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 48903)
  • NSEC3 proving non-existence of fed.us/DS
  • us/DNSKEY (alg 8, id 21364)
  • us/DNSKEY (alg 8, id 39361)
  • us/DNSKEY (alg 8, id 53985)
  • us/DNSKEY (alg 8, id 8985)
  • us/DS (alg 8, id 21364)
  • us/DS (alg 8, id 21364)
  • us/DS (alg 8, id 39361)
  • us/DS (alg 8, id 39361)

Delegation statusDelegation status

Insecure (2)
  • fed.us to treasury.fed.us
  • us to fed.us
Secure (1)
  • . to us

NoticesNotices

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