View on GitHub

DNSViz: A DNS visualization tool

fiscal.treasury.gov

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

RRset statusRRset status

Insecure (7)
  • fiscal.treasury.gov/A
  • fiscal.treasury.gov/AAAA
  • fiscal.treasury.gov/MX
  • fiscal.treasury.gov/NS
  • fiscal.treasury.gov/SOA
  • fiscal.treasury.gov/TXT
  • treasury.gov/SOA
Secure (1)
  • gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (6)
  • NSEC3 proving non-existence of fiscal.treasury.gov/DS
  • NSEC3 proving non-existence of fiscal.treasury.gov/DS
  • NSEC3 proving non-existence of fiscal.treasury.gov/DS
  • NSEC3 proving non-existence of fiscal.treasury.gov/DS
  • treasury.gov/DNSKEY (alg 7, id 27992)
  • treasury.gov/DNSKEY (alg 7, id 4458)
Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • NSEC3 proving non-existence of treasury.gov/DS
  • gov/DNSKEY (alg 8, id 50011)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

Insecure (2)
  • gov to treasury.gov
  • treasury.gov to fiscal.treasury.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (26)
  • NSEC3 proving non-existence of fiscal.treasury.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 fiscal.treasury.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 fiscal.treasury.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 fiscal.treasury.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 fiscal.treasury.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 fiscal.treasury.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 fiscal.treasury.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 fiscal.treasury.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 treasury.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 treasury.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • RRSIG fiscal.treasury.gov/A alg 7, id 27992: The Signer's Name field of the RRSIG RR (treasury.gov) does not match the name of the zone containing the RRset (fiscal.treasury.gov). See RFC 4035, Sec. 5.3.1.
  • RRSIG fiscal.treasury.gov/A alg 7, id 27992: The Signer's Name field of the RRSIG RR (treasury.gov) does not match the name of the zone containing the RRset (fiscal.treasury.gov). See RFC 4035, Sec. 5.3.1.
  • RRSIG fiscal.treasury.gov/AAAA alg 7, id 27992: The Signer's Name field of the RRSIG RR (treasury.gov) does not match the name of the zone containing the RRset (fiscal.treasury.gov). See RFC 4035, Sec. 5.3.1.
  • RRSIG fiscal.treasury.gov/AAAA alg 7, id 27992: The Signer's Name field of the RRSIG RR (treasury.gov) does not match the name of the zone containing the RRset (fiscal.treasury.gov). See RFC 4035, Sec. 5.3.1.
  • RRSIG fiscal.treasury.gov/MX alg 7, id 27992: The Signer's Name field of the RRSIG RR (treasury.gov) does not match the name of the zone containing the RRset (fiscal.treasury.gov). See RFC 4035, Sec. 5.3.1.
  • RRSIG fiscal.treasury.gov/MX alg 7, id 27992: The Signer's Name field of the RRSIG RR (treasury.gov) does not match the name of the zone containing the RRset (fiscal.treasury.gov). See RFC 4035, Sec. 5.3.1.
  • RRSIG fiscal.treasury.gov/SOA alg 7, id 27992: The Signer's Name field of the RRSIG RR (treasury.gov) does not match the name of the zone containing the RRset (fiscal.treasury.gov). See RFC 4035, Sec. 5.3.1.
  • RRSIG fiscal.treasury.gov/SOA alg 7, id 27992: The Signer's Name field of the RRSIG RR (treasury.gov) does not match the name of the zone containing the RRset (fiscal.treasury.gov). See RFC 4035, Sec. 5.3.1.
  • RRSIG fiscal.treasury.gov/SOA alg 7, id 27992: The Signer's Name field of the RRSIG RR (treasury.gov) does not match the name of the zone containing the RRset (fiscal.treasury.gov). See RFC 4035, Sec. 5.3.1.
  • RRSIG fiscal.treasury.gov/SOA alg 7, id 27992: The Signer's Name field of the RRSIG RR (treasury.gov) does not match the name of the zone containing the RRset (fiscal.treasury.gov). See RFC 4035, Sec. 5.3.1.
  • RRSIG fiscal.treasury.gov/TXT alg 7, id 27992: The Signer's Name field of the RRSIG RR (treasury.gov) does not match the name of the zone containing the RRset (fiscal.treasury.gov). See RFC 4035, Sec. 5.3.1.
  • RRSIG fiscal.treasury.gov/TXT alg 7, id 27992: The Signer's Name field of the RRSIG RR (treasury.gov) does not match the name of the zone containing the RRset (fiscal.treasury.gov). See RFC 4035, Sec. 5.3.1.
  • fiscal.treasury.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • fiscal.treasury.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • fiscal.treasury.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • fiscal.treasury.gov/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (43)
  • NSEC3 proving non-existence of fiscal.treasury.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of fiscal.treasury.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of fiscal.treasury.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of fiscal.treasury.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of fiscal.treasury.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of fiscal.treasury.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of fiscal.treasury.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of fiscal.treasury.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of treasury.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of treasury.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of fiscal.treasury.gov/DS alg 7, id 27992: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of fiscal.treasury.gov/DS alg 7, id 27992: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of fiscal.treasury.gov/DS alg 7, id 27992: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of fiscal.treasury.gov/DS alg 7, id 27992: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fiscal.treasury.gov/A alg 7, id 27992: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fiscal.treasury.gov/A alg 7, id 27992: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fiscal.treasury.gov/AAAA alg 7, id 27992: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fiscal.treasury.gov/AAAA alg 7, id 27992: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fiscal.treasury.gov/MX alg 7, id 27992: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fiscal.treasury.gov/MX alg 7, id 27992: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fiscal.treasury.gov/SOA alg 7, id 27992: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fiscal.treasury.gov/SOA alg 7, id 27992: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fiscal.treasury.gov/SOA alg 7, id 27992: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fiscal.treasury.gov/SOA alg 7, id 27992: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fiscal.treasury.gov/TXT alg 7, id 27992: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fiscal.treasury.gov/TXT alg 7, id 27992: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/DNSKEY alg 7, id 27992: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/DNSKEY alg 7, id 27992: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/DNSKEY alg 7, id 27992: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/DNSKEY alg 7, id 27992: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/DNSKEY alg 7, id 4458: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/DNSKEY alg 7, id 4458: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/DNSKEY alg 7, id 4458: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/DNSKEY alg 7, id 4458: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/SOA alg 7, id 27992: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/SOA alg 7, id 27992: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/SOA alg 7, id 27992: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • fiscal.treasury.gov/DNSKEY: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (172.64.52.110, 172.64.53.149, 2606:4700:52::ac40:346e, 2606:4700:5a::ac40:3595, UDP_-_EDNS0_512_D_KN)
  • treasury.gov/DNSKEY: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (172.64.52.110, 172.64.53.149, 2606:4700:52::ac40:346e, 2606:4700:5a::ac40:3595, UDP_-_EDNS0_512_D_KN)
  • fiscal.treasury.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • fiscal.treasury.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • fiscal.treasury.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • fiscal.treasury.gov/NSEC3PARAM 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