peacecorps.gov
Updated:
2021-08-12 02:27:07 UTC (1202 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (7)
- peacecorps.gov/A
- peacecorps.gov/AAAA
- peacecorps.gov/MX
- peacecorps.gov/NS
- peacecorps.gov/NSEC3PARAM
- peacecorps.gov/SOA
- peacecorps.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- gov/DNSKEY (alg 8, id 57735)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- peacecorps.gov/DNSKEY (alg 7, id 20661)
- peacecorps.gov/DNSKEY (alg 7, id 20870)
- peacecorps.gov/DNSKEY (alg 7, id 44838)
- peacecorps.gov/DS (alg 7, id 44838)
- peacecorps.gov/DS (alg 7, id 44838)
Delegation status
Secure (2)
- . to gov
- gov to peacecorps.gov
Notices
Errors (15)
- gov to peacecorps.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. (65.205.231.223, TCP_-_NOEDNS_)
- gov to peacecorps.gov: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no DS RR matched a DNSKEY with algorithm 7 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (65.205.231.223, TCP_-_NOEDNS_)
- peacecorps.gov/DNSKEY (alg 7, id 20661): DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 11 times) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (65.205.231.223, TCP_-_NOEDNS_)
- peacecorps.gov/DNSKEY (alg 7, id 20661): No response was received from the server over UDP (tried 11 times) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (65.205.231.223, UDP_-_EDNS0_4096_D_KN)
- peacecorps.gov/DNSKEY (alg 7, id 20661): The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (65.205.231.223, UDP_-_EDNS0_4096_D_KN)
- peacecorps.gov/DNSKEY (alg 7, id 20870): DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 11 times) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (65.205.231.223, TCP_-_NOEDNS_)
- peacecorps.gov/DNSKEY (alg 7, id 20870): No response was received from the server over UDP (tried 11 times) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (65.205.231.223, UDP_-_EDNS0_4096_D_KN)
- peacecorps.gov/DNSKEY (alg 7, id 20870): The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (65.205.231.223, UDP_-_EDNS0_4096_D_KN)
- peacecorps.gov/DNSKEY (alg 7, id 44838): DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 11 times) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (65.205.231.223, TCP_-_NOEDNS_)
- peacecorps.gov/DNSKEY (alg 7, id 44838): No response was received from the server over UDP (tried 11 times) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (65.205.231.223, UDP_-_EDNS0_4096_D_KN)
- peacecorps.gov/DNSKEY (alg 7, id 44838): The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (65.205.231.223, UDP_-_EDNS0_4096_D_KN)
- peacecorps.gov/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (65.205.231.223, UDP_-_EDNS0_512_D_KN)
- peacecorps.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- peacecorps.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- 1zone8fb65.peacecorps.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (23)
- RRSIG peacecorps.gov/A alg 7, id 20870: 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 20870: 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 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 20870: 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 20870: 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 20870: 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 44838: 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 44838: 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 44838: 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 20870: 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 20870: 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 20870: 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 20870: 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 20870: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- peacecorps.gov/DS (alg 7, id 44838): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- peacecorps.gov/DS (alg 7, id 44838): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- peacecorps.gov/DS (alg 7, id 44838): 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.
- peacecorps.gov/DS (alg 7, id 44838): 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.
- 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.
- 1zone8fb65.peacecorps.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
