View on GitHub

DNSViz: A DNS visualization tool

dc3on.gov

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

RRset statusRRset status

Secure (4)
  • dc3on.gov/MX
  • dc3on.gov/NS
  • dc3on.gov/SOA
  • dc3on.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (13)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 42351)
  • dc3on.gov/DNSKEY (alg 13, id 26992)
  • dc3on.gov/DNSKEY (alg 13, id 32540)
  • dc3on.gov/DNSKEY (alg 13, id 56663)
  • dc3on.gov/DS (alg 13, id 56663)
  • dc3on.gov/DS (alg 13, id 56663)
  • dc3on.gov/DS (alg 8, id 54001)
  • gov/DNSKEY (alg 8, id 15489)
  • gov/DNSKEY (alg 8, id 27306)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
Non_existent (1)
  • dc3on.gov/DNSKEY (alg 8, id 54001)

Delegation statusDelegation status

Secure (2)
  • . to gov
  • gov to dc3on.gov

NoticesNotices

Errors (13)
  • dc3on.gov/DNSKEY (alg 13, id 26992): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, UDP_-_EDNS0_4096_D_KN)
  • dc3on.gov/DNSKEY (alg 13, id 32540): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, UDP_-_EDNS0_4096_D_KN)
  • dc3on.gov/DNSKEY (alg 13, id 56663): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, UDP_-_EDNS0_4096_D_KN)
  • dc3on.gov/MX: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • dc3on.gov/NS: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, UDP_-_EDNS0_4096_D_KN)
  • dc3on.gov/SOA: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • dc3on.gov/TXT: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, UDP_-_EDNS0_4096_D_KN)
  • gov to dc3on.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. (66.102.236.215, 66.102.236.216, UDP_-_EDNS0_4096_D_KN)
  • dc3on.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • wk4nemlt3i.dc3on.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • dc3on.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • dc3on.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • dc3on.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (20)
  • dc3on.gov/DS (alg 13, id 56663): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • dc3on.gov/DS (alg 13, id 56663): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • dc3on.gov/DS (alg 13, id 56663): 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.
  • dc3on.gov/DS (alg 13, id 56663): 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.
  • dc3on.gov/DS (alg 8, id 54001): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • dc3on.gov/DS (alg 8, id 54001): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • dc3on.gov/DS (alg 8, id 54001): 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.
  • dc3on.gov/DS (alg 8, id 54001): 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.
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): 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.
  • gov/DS (alg 8, id 7698): 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.
  • gov/DS (alg 8, id 7698): 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. (2001:7fe::53, UDP_-_EDNS0_4096_D_KN)
  • gov/DS (alg 8, id 7698): 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. (2001:7fe::53, UDP_-_EDNS0_4096_D_KN)
  • gov/DS (alg 8, id 7698): 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. (2001:7fe::53, UDP_-_EDNS0_4096_D_KN)
  • gov/DS (alg 8, id 7698): 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. (2001:7fe::53, UDP_-_EDNS0_4096_D_KN)
  • wk4nemlt3i.dc3on.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • dc3on.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • dc3on.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • dc3on.gov/CNAME 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