View on GitHub

DNSViz: A DNS visualization tool

treasuryauctions.gov

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

RRset statusRRset status

Secure (6)
  • treasuryauctions.gov/A
  • treasuryauctions.gov/AAAA
  • treasuryauctions.gov/MX
  • treasuryauctions.gov/NS
  • treasuryauctions.gov/SOA
  • treasuryauctions.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • gov/DNSKEY (alg 8, id 15489)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • treasuryauctions.gov/DNSKEY (alg 7, id 54122)
  • treasuryauctions.gov/DNSKEY (alg 8, id 46786)
  • treasuryauctions.gov/DS (alg 8, id 46786)
  • treasuryauctions.gov/DS (alg 8, id 46786)

Delegation statusDelegation status

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

NoticesNotices

Errors (14)
  • treasuryauctions.gov/A: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (164.95.95.155, 166.123.208.249, 2610:108:3000:100a::155, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
  • treasuryauctions.gov/A: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (164.95.95.155, 166.123.208.249, 2610:108:3000:100a::155, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
  • treasuryauctions.gov/AAAA: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (164.95.95.155, 166.123.208.249, 2610:108:3000:100a::155, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
  • treasuryauctions.gov/AAAA: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (164.95.95.155, 166.123.208.249, 2610:108:3000:100a::155, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
  • treasuryauctions.gov/MX: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (164.95.95.155, 166.123.208.249, 2610:108:3000:100a::155, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
  • treasuryauctions.gov/MX: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (164.95.95.155, 166.123.208.249, 2610:108:3000:100a::155, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
  • treasuryauctions.gov/NS: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (164.95.95.155, 166.123.208.249, 2610:108:3000:100a::155, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
  • treasuryauctions.gov/NS: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (164.95.95.155, 166.123.208.249, 2610:108:3000:100a::155, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
  • treasuryauctions.gov/SOA: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (164.95.95.155, 166.123.208.249, 2610:108:3000:100a::155, 2610:108:4000:100a::249, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • treasuryauctions.gov/SOA: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (164.95.95.155, 166.123.208.249, 2610:108:3000:100a::155, 2610:108:4000:100a::249, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • treasuryauctions.gov/TXT: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (164.95.95.155, 166.123.208.249, 2610:108:3000:100a::155, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
  • treasuryauctions.gov/TXT: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (164.95.95.155, 166.123.208.249, 2610:108:3000:100a::155, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
  • 6ca95izqey.treasuryauctions.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • treasuryauctions.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (46)
  • RRSIG treasuryauctions.gov/A alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/A alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/A alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/A alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/AAAA alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/AAAA alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/AAAA alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/AAAA alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/DNSKEY alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/DNSKEY alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/DNSKEY alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/DNSKEY alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/DNSKEY alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/DNSKEY alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/MX alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/MX alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/MX alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/MX alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/NS alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/NS alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/NS alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/NS alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/NS alg 7, id 54122: The value of the Signature Inception field of the RRSIG RR (2020-11-16 12:45:58+00:00) is within possible clock skew range (0 seconds) of the current time (2020-11-16 12:45:58+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG treasuryauctions.gov/SOA alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/SOA alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/SOA alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/SOA alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/SOA alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/SOA alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/SOA alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/SOA alg 7, id 54122: The value of the Signature Inception field of the RRSIG RR (2020-11-16 12:45:58+00:00) is within possible clock skew range (0 seconds) of the current time (2020-11-16 12:45:58+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG treasuryauctions.gov/TXT alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/TXT alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/TXT alg 7, id 54122: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treasuryauctions.gov/TXT alg 7, id 54122: The value of the Signature Inception field of the RRSIG RR (2020-11-16 12:45:58+00:00) is within possible clock skew range (0 seconds) of the current time (2020-11-16 12:45:58+00:00). See RFC 4035, Sec. 5.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.
  • treasuryauctions.gov/DS (alg 8, id 46786): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • treasuryauctions.gov/DS (alg 8, id 46786): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • treasuryauctions.gov/DS (alg 8, id 46786): 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.
  • treasuryauctions.gov/DS (alg 8, id 46786): 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.
  • treasuryauctions.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 6ca95izqey.treasuryauctions.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • treasuryauctions.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