peacecorps.gov
Updated:
2022-12-09 21:24:56 UTC (715 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (7)
- peacecorps.gov/A
- peacecorps.gov/AAAA
- peacecorps.gov/MX
- peacecorps.gov/NS
- peacecorps.gov/NSEC3PARAM
- peacecorps.gov/SOA
- peacecorps.gov/TXT
Secure (1)
- gov/SOA
DNSKEY/DS/NSEC status
Insecure (2)
- peacecorps.gov/DNSKEY (alg 7, id 20661)
- peacecorps.gov/DNSKEY (alg 7, id 30914)
Secure (6)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of peacecorps.gov/DS
- gov/DNSKEY (alg 8, id 56278)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Insecure (1)
- gov to peacecorps.gov
Secure (1)
- . to gov
Notices
Errors (5)
- NSEC3 proving non-existence of peacecorps.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of peacecorps.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- peacecorps.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- peacecorps.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
- 2knf8g7vzy.peacecorps.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (17)
- NSEC3 proving non-existence of peacecorps.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of peacecorps.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- RRSIG peacecorps.gov/A alg 7, id 30914: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG peacecorps.gov/AAAA alg 7, id 30914: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG peacecorps.gov/DNSKEY alg 7, id 20661: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG peacecorps.gov/DNSKEY alg 7, id 20661: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG peacecorps.gov/DNSKEY alg 7, id 30914: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG peacecorps.gov/DNSKEY alg 7, id 30914: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG peacecorps.gov/MX alg 7, id 30914: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG peacecorps.gov/NS alg 7, id 30914: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG peacecorps.gov/NSEC3PARAM alg 7, id 30914: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG peacecorps.gov/SOA alg 7, id 30914: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG peacecorps.gov/TXT alg 7, id 30914: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- peacecorps.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- peacecorps.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- peacecorps.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
- 2knf8g7vzy.peacecorps.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
