View on GitHub

DNSViz: A DNS visualization tool

nasa.gov

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

RRset statusRRset status

Bogus (6)
  • nasa.gov/A
  • nasa.gov/AAAA
  • nasa.gov/MX
  • nasa.gov/NS
  • nasa.gov/SOA
  • nasa.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 951)
  • gov/DNSKEY (alg 8, id 24250)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • nasa.gov/DS (alg 8, id 22855)
Non_existent (1)
  • nasa.gov/DNSKEY (alg 8, id 22855)

Delegation statusDelegation status

Bogus (1)
  • gov to nasa.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (17)
  • gov to nasa.gov: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (2.16.40.66, 95.100.168.66, 184.26.160.64, 184.26.161.67, 184.85.248.64, 193.108.91.32, 2600:1401:2::20, 2600:1403:a::42, 2600:1480:1800::43, 2600:1480:b000::42, 2600:1480:f000::40, 2a02:26f0:117::40, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gov to nasa.gov: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (2.16.40.66, 95.100.168.66, 184.26.160.64, 184.26.161.67, 184.85.248.64, 193.108.91.32, 2600:1401:2::20, 2600:1403:a::42, 2600:1480:1800::43, 2600:1480:b000::42, 2600:1480:f000::40, 2a02:26f0:117::40, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • nasa.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (2600:1401:2::20)
  • nasa.gov/A: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 10 times) with the DO bit set. See RFC 4035, Sec. 3.2.1. (2600:1401:2::20, UDP_-_EDNS0_4096_)
  • nasa.gov/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (2.16.40.66, 95.100.168.66, 184.26.160.64, 184.26.161.67, 184.85.248.64, 193.108.91.32, 2600:1403:a::42, 2600:1480:1800::43, 2600:1480:b000::42, 2600:1480:f000::40, 2a02:26f0:117::40, UDP_-_EDNS0_4096_D_KN)
  • nasa.gov/A: No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). See RFC 6891, Sec. 6.1.4. (2600:1401:2::20, UDP_-_EDNS0_4096_D_KN)
  • nasa.gov/A: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (2600:1401:2::20, UDP_-_EDNS0_4096_D_KN)
  • nasa.gov/AAAA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (2.16.40.66, 95.100.168.66, 184.26.160.64, 184.26.161.67, 184.85.248.64, 193.108.91.32, 2600:1401:2::20, 2600:1403:a::42, 2600:1480:1800::43, 2600:1480:b000::42, 2600:1480:f000::40, 2a02:26f0:117::40, UDP_-_EDNS0_4096_D_KN)
  • nasa.gov/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (2.16.40.66, 95.100.168.66, 184.26.160.64, 184.26.161.67, 184.85.248.64, 193.108.91.32, 2600:1401:2::20, 2600:1403:a::42, 2600:1480:1800::43, 2600:1480:b000::42, 2600:1480:f000::40, 2a02:26f0:117::40, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • nasa.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (2.16.40.66, 95.100.168.66, 184.26.160.64, 184.26.161.67, 184.85.248.64, 193.108.91.32, 2600:1401:2::20, 2600:1403:a::42, 2600:1480:1800::43, 2600:1480:b000::42, 2600:1480:f000::40, 2a02:26f0:117::40, UDP_-_EDNS0_4096_D_KN)
  • nasa.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (2.16.40.66, 95.100.168.66, 184.26.160.64, 184.26.161.67, 184.85.248.64, 193.108.91.32, 2600:1401:2::20, 2600:1403:a::42, 2600:1480:1800::43, 2600:1480:b000::42, 2600:1480:f000::40, 2a02:26f0:117::40, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • nasa.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (2600:1401:2::20, TCP_-_EDNS0_4096_D_N)
  • nasa.gov/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (2.16.40.66, 95.100.168.66, 184.26.160.64, 184.26.161.67, 184.85.248.64, 193.108.91.32, 2600:1401:2::20, 2600:1403:a::42, 2600:1480:1800::43, 2600:1480:b000::42, 2600:1480:f000::40, 2a02:26f0:117::40, UDP_-_EDNS0_4096_D_KN)
  • nasa.gov/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • nasa.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • nasa.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • e6gq274sjc.nasa.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (1)
  • nasa.gov/SOA: 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. (2600:1401:2::20, UDP_-_EDNS0_4096_D_KN)

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