View on GitHub

DNSViz: A DNS visualization tool

sss.gov

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

RRset statusRRset status

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • gov/DNSKEY (alg 8, id 50011)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • sss.gov/DS (alg 7, id 49254)
  • sss.gov/DS (alg 7, id 55410)
Non_existent (2)
  • sss.gov/DNSKEY (alg 7, id 49254)
  • sss.gov/DNSKEY (alg 7, id 55410)

Delegation statusDelegation status

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

NoticesNotices

Errors (15)
  • gov to sss.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.
  • sss.gov zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (63.150.72.5, 208.44.130.121, 2001:428::7, 2001:428::8)
  • sss.gov zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (63.150.72.5, 208.44.130.121, 2001:428::7, 2001:428::8)
  • sss.gov/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (63.150.72.5, 208.44.130.121, 2001:428::7, 2001:428::8, UDP_-_EDNS0_4096_D_KN)
  • sss.gov/AAAA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (63.150.72.5, 208.44.130.121, 2001:428::7, 2001:428::8, UDP_-_EDNS0_4096_D_KN)
  • sss.gov/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (63.150.72.5, 208.44.130.121, 2001:428::7, 2001:428::8, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • sss.gov/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (63.150.72.5, 208.44.130.121, 2001:428::7, 2001:428::8, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • sss.gov/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (63.150.72.5, 208.44.130.121, 2001:428::7, 2001:428::8, UDP_-_EDNS0_4096_D_KN)
  • sss.gov/NSEC3PARAM: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (63.150.72.5, 208.44.130.121, 2001:428::7, 2001:428::8, UDP_-_EDNS0_4096_D_KN)
  • sss.gov/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (63.150.72.5, 208.44.130.121, 2001:428::7, 2001:428::8, TCP_-_EDNS0_4096_D_N)
  • sss.gov/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (63.150.72.5, 208.44.130.121, 2001:428::7, 2001:428::8, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • sss.gov/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (63.150.72.5, 208.44.130.121, 2001:428::7, 2001:428::8, UDP_-_EDNS0_4096_D_KN)
  • sss.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • sss.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • 8vrxu125qd.sss.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
  • sss.gov/DS (alg 7, id 49254): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • sss.gov/DS (alg 7, id 49254): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • sss.gov/DS (alg 7, id 49254): 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.
  • sss.gov/DS (alg 7, id 49254): 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.

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