cnss.gov
Updated:
2021-06-15 18:16:35 UTC (1256 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (2)
- cnss.gov/NS
- cnss.gov/SOA
DNSKEY/DS/NSEC status
Secure (13)
- ./DNSKEY (alg 8, id 14631)
- ./DNSKEY (alg 8, id 20326)
- cnss.gov/DNSKEY (alg 8, id 26101)
- cnss.gov/DNSKEY (alg 8, id 31669)
- cnss.gov/DNSKEY (alg 8, id 4231)
- cnss.gov/DNSKEY (alg 8, id 59763)
- cnss.gov/DS (alg 8, id 31669)
- cnss.gov/DS (alg 8, id 31669)
- cnss.gov/DS (alg 8, id 4231)
- cnss.gov/DS (alg 8, id 4231)
- gov/DNSKEY (alg 8, id 48498)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Secure (2)
- . to gov
- gov to cnss.gov
Notices
Errors (6)
- cnss.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- cnss.gov/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
- pm8hdsiacj.cnss.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- cnss.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- cnss.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- cnss.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (16)
- ./DNSKEY (alg 8, id 14631): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 20326): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
- cnss.gov/DS (alg 8, id 31669): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- cnss.gov/DS (alg 8, id 31669): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- cnss.gov/DS (alg 8, id 31669): 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.
- cnss.gov/DS (alg 8, id 31669): 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.
- cnss.gov/DS (alg 8, id 4231): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- cnss.gov/DS (alg 8, id 4231): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- cnss.gov/DS (alg 8, id 4231): 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.
- cnss.gov/DS (alg 8, id 4231): 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.
- cnss.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- cnss.gov/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.
- pm8hdsiacj.cnss.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- cnss.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- cnss.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- cnss.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
