fincen.gov
Updated:
2020-09-04 08:14:49 UTC (1542 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- fincen.gov/A
- fincen.gov/MX
- fincen.gov/NS
- fincen.gov/SOA
- fincen.gov/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46594)
- fincen.gov/DNSKEY (alg 8, id 13690)
- fincen.gov/DNSKEY (alg 8, id 22834)
- fincen.gov/DNSKEY (alg 8, id 62100)
- fincen.gov/DNSKEY (alg 8, id 63231)
- fincen.gov/DS (alg 8, id 13690)
- fincen.gov/DS (alg 8, id 13690)
- gov/DNSKEY (alg 8, id 26665)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Secure (2)
- . to gov
- gov to fincen.gov
Notices
Errors (6)
- fincen.gov/DNSKEY (alg 8, id 13690): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
- gov to fincen.gov: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
- gov to fincen.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. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
- fincen.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- fincen.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- 5s9mxgjz0n.fincen.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
- fincen.gov/DNSKEY (alg 8, id 22834): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (164.95.95.155, 2610:108:3000:100a::155, UDP_-_EDNS0_4096_D_K)
- fincen.gov/DS (alg 8, id 13690): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- fincen.gov/DS (alg 8, id 13690): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- fincen.gov/DS (alg 8, id 13690): 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.
- fincen.gov/DS (alg 8, id 13690): 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.
- fincen.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- fincen.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- 5s9mxgjz0n.fincen.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
