View on GitHub

DNSViz: A DNS visualization tool

treasury.gov

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

RRset statusRRset status

Bogus (1)
  • treasury.gov/AAAA (NODATA)
Secure (6)
  • treasury.gov/A
  • treasury.gov/AAAA
  • treasury.gov/MX
  • treasury.gov/NS
  • treasury.gov/SOA
  • treasury.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (4)
  • NSEC3 proving non-existence of treasury.gov/AAAA
  • NSEC3 proving non-existence of treasury.gov/AAAA
  • treasury.gov/DNSKEY (alg 7, id 1664)
  • treasury.gov/DNSKEY (alg 7, id 44076)
Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • gov/DNSKEY (alg 8, id 26665)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • treasury.gov/DNSKEY (alg 7, id 22148)
  • treasury.gov/DNSKEY (alg 7, id 37335)
  • treasury.gov/DS (alg 7, id 37335)
  • treasury.gov/DS (alg 7, id 37335)

Delegation statusDelegation status

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

NoticesNotices

Errors (17)
  • NSEC3 proving non-existence of treasury.gov/AAAA: 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/AAAA: 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/AAAA: 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/AAAA: 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/AAAA: The following queries resulted in an answer response, even though the bitmap in the NSEC3 RR indicates that the queried records don't exist: treasury.gov/TXT, treasury.gov/AAAA, treasury.gov/A, treasury.gov/MX See RFC 5155, Sec. 8.5.
  • NSEC3 proving non-existence of treasury.gov/AAAA: The following queries resulted in an answer response, even though the bitmap in the NSEC3 RR indicates that the queried records don't exist: treasury.gov/TXT, treasury.gov/AAAA, treasury.gov/A, treasury.gov/MX See RFC 5155, Sec. 8.5.
  • NSEC3 proving non-existence of treasury.gov/AAAA: The following queries resulted in an answer response, even though the bitmap in the NSEC3 RR indicates that the queried records don't exist: treasury.gov/TXT, treasury.gov/AAAA, treasury.gov/A, treasury.gov/MX See RFC 5155, Sec. 8.5.
  • NSEC3 proving non-existence of treasury.gov/AAAA: The following queries resulted in an answer response, even though the bitmap in the NSEC3 RR indicates that the queried records don't exist: treasury.gov/TXT, treasury.gov/AAAA, treasury.gov/A, treasury.gov/MX See RFC 5155, Sec. 8.5.
  • RRSIG treasury.gov/A alg 7, id 22148: The TTL of the RRset (120) exceeds the value of the Original TTL field of the RRSIG RR covering it (2). See RFC 4035, Sec. 2.2.
  • RRSIG treasury.gov/A alg 7, id 22148: The TTL of the RRset (120) exceeds the value of the Original TTL field of the RRSIG RR covering it (2). See RFC 4035, Sec. 2.2.
  • gov to treasury.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. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
  • gov to treasury.gov: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no DS RR matched a DNSKEY with algorithm 7 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
  • treasury.gov/DNSKEY (alg 7, id 1664): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (164.95.95.155, 2610:108:3000:100a::155, UDP_-_EDNS0_4096_D_K)
  • treasury.gov/DNSKEY (alg 7, id 22148): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
  • treasury.gov/DNSKEY (alg 7, id 37335): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
  • fnhkudey1i.treasury.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • treasury.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (54)
  • NSEC3 proving non-existence of treasury.gov/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of treasury.gov/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of treasury.gov/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of treasury.gov/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of treasury.gov/AAAA alg 7, id 1664: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of treasury.gov/AAAA alg 7, id 1664: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/A alg 7, id 1664: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/A alg 7, id 1664: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/A alg 7, id 22148: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/A alg 7, id 22148: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/AAAA alg 7, id 22148: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/AAAA alg 7, id 22148: 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 1664: 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 1664: 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 22148: 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 22148: 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 22148: 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 22148: 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 37335: 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 37335: 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 37335: 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 37335: 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 44076: 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 44076: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/MX alg 7, id 1664: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/MX alg 7, id 1664: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/MX alg 7, id 22148: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/MX alg 7, id 22148: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/NS alg 7, id 1664: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/NS alg 7, id 22148: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/NS alg 7, id 22148: 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 1664: 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 1664: 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 22148: 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 22148: 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 22148: 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 22148: 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 22148: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/TXT alg 7, id 1664: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/TXT alg 7, id 1664: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/TXT alg 7, id 22148: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasury.gov/TXT alg 7, id 22148: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • 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.
  • treasury.gov/DNSKEY (alg 7, id 44076): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (164.95.95.155, 2610:108:3000:100a::155, UDP_-_EDNS0_4096_D_K)
  • treasury.gov/DS (alg 7, id 37335): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • treasury.gov/DS (alg 7, id 37335): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • treasury.gov/DS (alg 7, id 37335): 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.
  • treasury.gov/DS (alg 7, id 37335): 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.
  • treasury.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • fnhkudey1i.treasury.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • treasury.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