View on GitHub

DNSViz: A DNS visualization tool

usandc.gov

Updated: 2021-05-15 12:31:45 UTC (1287 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (5)
  • usandc.gov/MX
  • usandc.gov/NS
  • usandc.gov/NS
  • usandc.gov/SOA
  • usandc.gov/SOA
Secure (1)
  • gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC3 proving non-existence of usandc.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 usandc.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (17)
  • NSEC3 proving non-existence of usandc.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 usandc.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • usandc.gov zone: The following NS name(s) did not resolve to address(es): altdsos.altusandc.gov, altdstork.altusandc.gov
  • usandc.gov zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (198.47.84.11)
  • usandc.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (198.47.84.11, 198.47.84.12)
  • usandc.gov/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (198.47.84.11, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • usandc.gov/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (198.47.84.11, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • usandc.gov/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (198.47.84.11, UDP_-_NOEDNS_)
  • usandc.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (198.47.84.11, 198.47.84.12, TCP_-_EDNS0_4096_D_N)
  • usandc.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (198.47.84.11, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • usandc.gov/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
  • f719m3dxv8.usandc.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • usandc.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • usandc.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • usandc.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • usandc.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • usandc.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
  • NSEC3 proving non-existence of usandc.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of usandc.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • gov to usandc.gov: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gov zone): mnsa-dns-002zu.altusandc.gov, mnsa-dns-001zu.altusandc.gov See RFC 1034, Sec. 4.2.2.
  • usandc.gov/DS 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