View on GitHub

DNSViz: A DNS visualization tool

ipac.gov

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

RRset statusRRset status

Secure (1)
  • gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 20826)
  • NSEC3 proving non-existence of ipac.gov/DS
  • gov/DNSKEY (alg 8, id 261)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

Lame (1)
  • gov to ipac.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (28)
  • NSEC3 proving non-existence of ipac.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 ipac.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • ipac.gov zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (199.169.192.28, 199.169.194.28, 2605:3100:fffc:100::7, 2605:3100:fffd:100::7)
  • ipac.gov zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (199.169.192.28, 199.169.194.28, 2605:3100:fffc:100::7, 2605:3100:fffd:100::7)
  • ipac.gov/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (199.169.194.28, 2605:3100:fffc:100::7, UDP_-_EDNS0_4096_D_KN)
  • ipac.gov/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.169.192.28, 2605:3100:fffd:100::7, UDP_-_NOEDNS_)
  • ipac.gov/AAAA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (199.169.194.28, 2605:3100:fffc:100::7, UDP_-_EDNS0_4096_D_KN)
  • ipac.gov/AAAA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.169.192.28, 2605:3100:fffd:100::7, UDP_-_NOEDNS_)
  • ipac.gov/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (199.169.194.28, 2605:3100:fffc:100::7, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • ipac.gov/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.169.192.28, 2605:3100:fffd:100::7, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • ipac.gov/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (199.169.194.28, 2605:3100:fffc:100::7, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • ipac.gov/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.169.192.28, 2605:3100:fffd:100::7, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • ipac.gov/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (199.169.194.28, 2605:3100:fffc:100::7, UDP_-_EDNS0_4096_D_KN)
  • ipac.gov/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.169.192.28, 2605:3100:fffd:100::7, UDP_-_NOEDNS_)
  • ipac.gov/NSEC3PARAM: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (199.169.194.28, 2605:3100:fffc:100::7, UDP_-_EDNS0_4096_D_KN)
  • ipac.gov/NSEC3PARAM: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.169.192.28, 2605:3100:fffd:100::7, UDP_-_NOEDNS_)
  • ipac.gov/SOA: No response was received from the server over TCP (tried 4 times). See RFC 1035, Sec. 4.2. (2605:3100:fffd:100::7, TCP_-_NOEDNS_)
  • ipac.gov/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (199.169.194.28, 2605:3100:fffc:100::7, TCP_-_EDNS0_4096_D_N)
  • ipac.gov/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (199.169.194.28, 2605:3100:fffc:100::7, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • ipac.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.169.192.28, 2605:3100:fffd:100::7, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • ipac.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.169.192.28, TCP_-_NOEDNS_)
  • ipac.gov/TXT: No response was received from the server over UDP (tried 13 times). See RFC 1035, Sec. 4.2. (2605:3100:fffd:100::7, UDP_-_NOEDNS_)
  • ipac.gov/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (199.169.194.28, 2605:3100:fffc:100::7, UDP_-_EDNS0_4096_D_KN)
  • ipac.gov/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.169.192.28, UDP_-_NOEDNS_)
  • ipac.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • ojh0acwitl.ipac.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • ipac.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • ipac.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
  • NSEC3 proving non-existence of ipac.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of ipac.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • gov to ipac.gov: Authoritative AAAA records exist for ns1.twai.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • ipac.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