View on GitHub

DNSViz: A DNS visualization tool

housecommunications.gov

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

RRset statusRRset status

Insecure (4)
  • housecommunications.gov/A
  • housecommunications.gov/NS
  • housecommunications.gov/SOA
  • housecommunications.gov/TXT
Secure (1)
  • gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (3)
  • housecommunications.gov/DNSKEY (alg 8, id 19854)
  • housecommunications.gov/DNSKEY (alg 8, id 45430)
  • housecommunications.gov/DNSKEY (alg 8, id 63051)
Secure (7)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • NSEC3 proving non-existence of housecommunications.gov/DS
  • gov/DNSKEY (alg 8, id 48498)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

Insecure (1)
  • gov to housecommunications.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (10)
  • NSEC3 proving non-existence of housecommunications.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 housecommunications.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • housecommunications.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:502:4612::91)
  • housecommunications.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:502:4612::91, UDP_-_NOEDNS_)
  • housecommunications.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:502:4612::91, UDP_-_NOEDNS_)
  • housecommunications.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • 5qhcyorwt4.housecommunications.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • housecommunications.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • housecommunications.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • housecommunications.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
  • NSEC3 proving non-existence of housecommunications.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of housecommunications.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • housecommunications.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 5qhcyorwt4.housecommunications.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • housecommunications.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • housecommunications.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • housecommunications.gov/AAAA 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