View on GitHub

DNSViz: A DNS visualization tool

qa.ws.igt.fiscal.treasury.gov

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

RRset statusRRset status

Bogus (4)
  • fiscal.treasury.gov/SOA
  • qa.ws.igt.fiscal.treasury.gov/A
  • qa.ws.igt.fiscal.treasury.gov/AAAA
  • treasury.gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (7)
  • 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
  • NSEC3 proving non-existence of igt.fiscal.treasury.gov/DS
  • NSEC3 proving non-existence of igt.fiscal.treasury.gov/DS
  • NSEC3 proving non-existence of igt.fiscal.treasury.gov/DS
Secure (10)
  • ./DNSKEY (alg 8, id 18733)
  • ./DNSKEY (alg 8, id 20326)
  • gov/DNSKEY (alg 8, id 261)
  • gov/DNSKEY (alg 8, id 56278)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • treasury.gov/DNSKEY (alg 7, id 3908)
  • treasury.gov/DNSKEY (alg 7, id 4458)
  • treasury.gov/DS (alg 7, id 4458)
  • treasury.gov/DS (alg 7, id 4458)
Non_existent (1)
  • treasury.gov/DNSKEY (alg 7, id 3908)

Delegation statusDelegation status

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

NoticesNotices

Errors (34)
  • 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 fiscal.treasury.gov/DS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (164.95.20.53, UDP_-_EDNS0_4096_D_KN)
  • NSEC3 proving non-existence of fiscal.treasury.gov/DS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (164.95.20.53, UDP_-_EDNS0_4096_D_KN)
  • NSEC3 proving non-existence of fiscal.treasury.gov/DS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (166.123.208.249, UDP_-_EDNS0_4096_D_KN)
  • NSEC3 proving non-existence of fiscal.treasury.gov/DS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (166.123.208.249, UDP_-_EDNS0_4096_D_KN)
  • NSEC3 proving non-existence of fiscal.treasury.gov/DS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (2610:108:3100:100a::20:53, UDP_-_EDNS0_4096_D_KN)
  • NSEC3 proving non-existence of fiscal.treasury.gov/DS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (2610:108:3100:100a::20:53, UDP_-_EDNS0_4096_D_KN)
  • NSEC3 proving non-existence of fiscal.treasury.gov/DS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_KN)
  • NSEC3 proving non-existence of fiscal.treasury.gov/DS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_KN)
  • NSEC3 proving non-existence of igt.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 igt.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 igt.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 igt.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 igt.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 igt.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 igt.fiscal.treasury.gov/DS: No NSEC3 RR matches the SNAME (igt.fiscal.treasury.gov). See RFC 5155, Sec. 8.6.
  • NSEC3 proving non-existence of igt.fiscal.treasury.gov/DS: No NSEC3 RR matches the SNAME (igt.fiscal.treasury.gov). See RFC 5155, Sec. 8.6.
  • NSEC3 proving non-existence of igt.fiscal.treasury.gov/DS: No NSEC3 RR matches the SNAME (igt.fiscal.treasury.gov). See RFC 5155, Sec. 8.6.
  • NSEC3 proving non-existence of igt.fiscal.treasury.gov/DS: No NSEC3 RR matches the SNAME (igt.fiscal.treasury.gov). See RFC 5155, Sec. 8.6.
  • NSEC3 proving non-existence of igt.fiscal.treasury.gov/DS: No NSEC3 RR matches the SNAME (igt.fiscal.treasury.gov). See RFC 5155, Sec. 8.6.
  • NSEC3 proving non-existence of igt.fiscal.treasury.gov/DS: No NSEC3 RR matches the SNAME (igt.fiscal.treasury.gov). See RFC 5155, Sec. 8.6.
  • RRSIG NSEC3 proving non-existence of igt.fiscal.treasury.gov/DS alg 7, id 3908: 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 NSEC3 proving non-existence of igt.fiscal.treasury.gov/DS alg 7, id 3908: 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 NSEC3 proving non-existence of igt.fiscal.treasury.gov/DS alg 7, id 3908: 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 3908: 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 3908: 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 3908: 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.
Warnings (40)
  • 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 igt.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 igt.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 igt.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 igt.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 igt.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 igt.fiscal.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 3908: 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 3908: 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 3908: 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 3908: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of igt.fiscal.treasury.gov/DS alg 7, id 3908: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of igt.fiscal.treasury.gov/DS alg 7, id 3908: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of igt.fiscal.treasury.gov/DS alg 7, id 3908: 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 3908: 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 3908: 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 3908: 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 3908: 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 3908: 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 3908: 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 3908: 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 3908: 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 3908: 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 3908: 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 3908: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • treasury.gov/DS (alg 7, id 4458): 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 4458): 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 4458): 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 4458): 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