jusfc.gov
Updated:
2020-09-11 19:52:11 UTC (1531 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- jusfc.gov/A
- jusfc.gov/MX
- jusfc.gov/NS
- jusfc.gov/SOA
- jusfc.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46594)
- gov/DNSKEY (alg 8, id 26665)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- jusfc.gov/DNSKEY (alg 5, id 25935)
- jusfc.gov/DNSKEY (alg 5, id 30679)
- jusfc.gov/DS (alg 5, id 30679)
- jusfc.gov/DS (alg 5, id 30679)
Delegation status
Secure (2)
- . to gov
- gov to jusfc.gov
Notices
Warnings (21)
- RRSIG jusfc.gov/A alg 5, id 25935: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG jusfc.gov/DNSKEY alg 5, id 25935: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG jusfc.gov/DNSKEY alg 5, id 25935: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG jusfc.gov/DNSKEY alg 5, id 30679: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG jusfc.gov/DNSKEY alg 5, id 30679: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG jusfc.gov/MX alg 5, id 25935: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG jusfc.gov/NS alg 5, id 25935: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG jusfc.gov/SOA alg 5, id 25935: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG jusfc.gov/TXT alg 5, id 25935: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- 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.
- jusfc.gov/DS (alg 5, id 30679): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- jusfc.gov/DS (alg 5, id 30679): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- jusfc.gov/DS (alg 5, id 30679): 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.
- jusfc.gov/DS (alg 5, id 30679): 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.
- jusfc.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- y9dlfsh74w.jusfc.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- jusfc.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- jusfc.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
