firstfreedom.gov
Updated:
2020-05-21 11:36:11 UTC (1645 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (6)
- firstfreedom.gov/A
- firstfreedom.gov/AAAA
- firstfreedom.gov/MX
- firstfreedom.gov/NS
- firstfreedom.gov/SOA
- firstfreedom.gov/TXT
DNSKEY/DS/NSEC status
Bogus (2)
- firstfreedom.gov/DNSKEY (alg 8, id 11056)
- firstfreedom.gov/DNSKEY (alg 8, id 9924)
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 48903)
- firstfreedom.gov/DS (alg 8, id 62530)
- gov/DNSKEY (alg 8, id 40176)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Non_existent (1)
- firstfreedom.gov/DNSKEY (alg 8, id 62530)
Delegation status
Bogus (1)
- gov to firstfreedom.gov
Secure (1)
- . to gov
Notices
Errors (4)
- gov to firstfreedom.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. (149.101.80.157, 149.101.180.157, 153.31.192.139, 2607:f330:2003:403::201, 2607:f330:5000:107f::86, 2607:f330:6000:107f::86, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- gov to firstfreedom.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. (149.101.80.157, 149.101.180.157, 153.31.192.139, 2607:f330:2003:403::201, 2607:f330:5000:107f::86, 2607:f330:6000:107f::86, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- 6gblch3vze.firstfreedom.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- firstfreedom.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
- firstfreedom.gov/DS (alg 8, id 62530): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- firstfreedom.gov/DS (alg 8, id 62530): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- firstfreedom.gov/DS (alg 8, id 62530): 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.
- firstfreedom.gov/DS (alg 8, id 62530): 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 to firstfreedom.gov: The following NS name(s) were found in the delegation NS RRset (i.e., in the gov zone), but not in the authoritative NS RRset: ns2.cjis.gov See RFC 1034, Sec. 4.2.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): 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.
- 6gblch3vze.firstfreedom.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- firstfreedom.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
