View on GitHub

DNSViz: A DNS visualization tool

ginniemae.gov

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

RRset statusRRset status

Insecure (1)
  • ginniemae.gov/A
Secure (1)
  • gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 18733)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC3 proving non-existence of ginniemae.gov/DS
  • gov/DNSKEY (alg 8, id 56278)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

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

NoticesNotices

Errors (19)
  • NSEC3 proving non-existence of ginniemae.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 ginniemae.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • ginniemae.gov zone: The server(s) did not respond authoritatively for the namespace. See RFC 1035, Sec. 4.1.1. (3.30.14.84, 18.252.150.96, 18.252.212.83, 160.1.176.36)
  • ginniemae.gov zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (3.30.14.84, 18.252.150.96, 18.252.212.83, 160.1.176.36)
  • ginniemae.gov/A: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (3.30.14.84, 18.252.150.96, 18.252.212.83, 160.1.176.36, UDP_-_EDNS0_4096_D_KN)
  • ginniemae.gov/AAAA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (3.30.14.84, 18.252.150.96, 18.252.212.83, 160.1.176.36, UDP_-_NOEDNS_)
  • ginniemae.gov/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (3.30.14.84, 18.252.150.96, 18.252.212.83, 160.1.176.36, UDP_-_NOEDNS_)
  • ginniemae.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (3.30.14.84, 18.252.150.96, 18.252.212.83, 160.1.176.36, UDP_-_EDNS0_512_D_KN)
  • ginniemae.gov/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (3.30.14.84, 18.252.150.96, 18.252.212.83, 160.1.176.36, UDP_-_NOEDNS_)
  • ginniemae.gov/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (3.30.14.84, 18.252.150.96, 18.252.212.83, 160.1.176.36, UDP_-_EDNS0_512_D_KN)
  • ginniemae.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (3.30.14.84, 18.252.150.96, 18.252.212.83, 160.1.176.36, UDP_-_NOEDNS_)
  • ginniemae.gov/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (3.30.14.84, 18.252.150.96, 18.252.212.83, 160.1.176.36, UDP_-_NOEDNS_)
  • ginniemae.gov/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (3.30.14.84, 18.252.150.96, 18.252.212.83, 160.1.176.36, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • ginniemae.gov/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (3.30.14.84, 18.252.150.96, 18.252.212.83, 160.1.176.36, TCP_-_EDNS0_4096_D_N)
  • ginniemae.gov/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (3.30.14.84, 18.252.150.96, 18.252.212.83, 160.1.176.36, UDP_-_NOEDNS_)
  • ginniemae.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • ginniemae.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • ginniemae.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • smx58av6i4.ginniemae.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
  • NSEC3 proving non-existence of ginniemae.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of ginniemae.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • ginniemae.gov/A: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (3.30.14.84, UDP_-_EDNS0_4096_D_KN)
  • ginniemae.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