ha.psc.gov/DNSKEY (alg 7, id 180): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (165.112.13.50, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
ha.psc.gov/DNSKEY (alg 7, id 32534): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (165.112.13.50, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
pms.ha.psc.gov/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (165.112.13.50, UDP_-_EDNS0_4096_D_KN)
psc.gov to ha.psc.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. (156.40.55.100, 165.112.13.50, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
psc.gov to ha.psc.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. (165.112.13.50, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
Warnings (18)
RRSIG ha.psc.gov/DNSKEY alg 7, id 180: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG ha.psc.gov/DNSKEY alg 7, id 180: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG ha.psc.gov/DNSKEY alg 7, id 32534: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG ha.psc.gov/DNSKEY alg 7, id 32534: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG pms.ha.psc.gov/A alg 7, id 32534: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
ha.psc.gov/DS (alg 7, id 180): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
ha.psc.gov/DS (alg 7, id 180): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
ha.psc.gov/DS (alg 7, id 180): 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.
ha.psc.gov/DS (alg 7, id 180): 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.
psc.gov/DS (alg 8, id 14656): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
psc.gov/DS (alg 8, id 14656): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
psc.gov/DS (alg 8, id 14656): 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.
psc.gov/DS (alg 8, id 14656): 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.
psc.gov/DS (alg 8, id 62567): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
psc.gov/DS (alg 8, id 62567): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
psc.gov/DS (alg 8, id 62567): 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.
psc.gov/DS (alg 8, id 62567): 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.
pms.psc.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.