jccbi.gov
Updated:
2023-01-30 19:10:40 UTC (663 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- jccbi.gov/NS
- jccbi.gov/NSEC3PARAM
- jccbi.gov/SOA
- jccbi.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 951)
- gov/DNSKEY (alg 8, id 24250)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- jccbi.gov/DNSKEY (alg 10, id 22580)
- jccbi.gov/DNSKEY (alg 10, id 26108)
- jccbi.gov/DNSKEY (alg 10, id 54533)
- jccbi.gov/DNSKEY (alg 10, id 61632)
- jccbi.gov/DS (alg 10, id 61632)
Delegation status
Secure (2)
- . to gov
- gov to jccbi.gov
Notices
Errors (5)
- jccbi.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- jccbi.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- ot3ruvh6c1.jccbi.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- jccbi.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- jccbi.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (18)
- RRSIG jccbi.gov/DNSKEY alg 10, id 26108: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG jccbi.gov/DNSKEY alg 10, id 26108: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG jccbi.gov/DNSKEY alg 10, id 26108: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG jccbi.gov/DNSKEY alg 10, id 26108: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG jccbi.gov/DNSKEY alg 10, id 61632: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG jccbi.gov/DNSKEY alg 10, id 61632: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG jccbi.gov/DNSKEY alg 10, id 61632: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG jccbi.gov/DNSKEY alg 10, id 61632: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG jccbi.gov/NS alg 10, id 26108: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG jccbi.gov/NSEC3PARAM alg 10, id 26108: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG jccbi.gov/SOA alg 10, id 26108: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG jccbi.gov/TXT alg 10, id 26108: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- jccbi.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- jccbi.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- jccbi.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- jccbi.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- ot3ruvh6c1.jccbi.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- jccbi.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
