View on GitHub

DNSViz: A DNS visualization tool

tsptest.gov

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

RRset statusRRset status

Bogus (1)
  • tsptest.gov/NS

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • gov/DNSKEY (alg 8, id 57735)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • tsptest.gov/DS (alg 7, id 38208)
  • tsptest.gov/DS (alg 8, id 7834)
Non_existent (6)
  • tsptest.gov/DNSKEY (alg 7, id 26642)
  • tsptest.gov/DNSKEY (alg 7, id 38208)
  • tsptest.gov/DNSKEY (alg 7, id 39857)
  • tsptest.gov/DNSKEY (alg 8, id 10311)
  • tsptest.gov/DNSKEY (alg 8, id 14625)
  • tsptest.gov/DNSKEY (alg 8, id 7834)

Delegation statusDelegation status

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

NoticesNotices

Errors (16)
  • gov to tsptest.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.
  • tsptest.gov zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (149.101.182.186)
  • tsptest.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.185)
  • tsptest.gov/AAAA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.185, 149.101.182.186, UDP_-_NOEDNS_)
  • tsptest.gov/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.185, 149.101.182.186, UDP_-_NOEDNS_)
  • tsptest.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.185, 149.101.182.186, UDP_-_EDNS0_512_D_KN)
  • tsptest.gov/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.185, 149.101.182.186, UDP_-_NOEDNS_)
  • tsptest.gov/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.185, 149.101.182.186, UDP_-_EDNS0_512_D_KN)
  • tsptest.gov/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.185, 149.101.182.186, UDP_-_NOEDNS_)
  • tsptest.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.185, 149.101.182.186, TCP_-_EDNS0_4096_D_N)
  • tsptest.gov/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.185, 149.101.182.186, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • tsptest.gov/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.185, 149.101.182.186, UDP_-_NOEDNS_)
  • tsptest.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • tsptest.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • 1kjge4qm20.tsptest.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • tsptest.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
  • RRSIG tsptest.gov/NS alg 7, id 26642: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tsptest.gov/NS alg 7, id 26642: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tsptest.gov/NS alg 7, id 26642: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tsptest.gov/NS alg 7, id 39857: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tsptest.gov/NS alg 7, id 39857: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tsptest.gov/NS alg 7, id 39857: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • tsptest.gov/DS (alg 7, id 38208): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • tsptest.gov/DS (alg 7, id 38208): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • tsptest.gov/DS (alg 7, id 38208): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • tsptest.gov/DS (alg 7, id 38208): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • tsptest.gov/NS: 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. (149.101.182.186, UDP_-_EDNS0_4096_D_KN)
  • tsptest.gov/A 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