jccbi.gov
Updated:
2022-03-21 14:16:15 UTC (981 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (3)
- jccbi.gov/NS
- jccbi.gov/SOA
- jccbi.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- gov/DNSKEY (alg 8, id 7030)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- jccbi.gov/DNSKEY (alg 8, id 37396)
- jccbi.gov/DNSKEY (alg 8, id 48109)
- jccbi.gov/DNSKEY (alg 8, id 62196)
- jccbi.gov/DS (alg 8, id 48109)
- jccbi.gov/DS (alg 8, id 48109)
Delegation status
Secure (2)
- . to gov
- gov to jccbi.gov
Notices
Warnings (6)
- 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. (192.112.36.4, 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
- jccbi.gov/DS (alg 8, id 48109): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- jccbi.gov/DS (alg 8, id 48109): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- jccbi.gov/DS (alg 8, id 48109): 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.
- jccbi.gov/DS (alg 8, id 48109): 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.
JavaScript is required to make the graph below interactive.
