medco.com

Updated: 2024-10-12 20:24:21 UTC (42 days ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 61050)
com/DNSKEY (alg 13, id 19718)
com/DNSKEY (alg 13, id 29942)
com/DNSKEY (alg 13, id 59354)
com/DS (alg 13, id 19718)
medco.com/DS (alg 8, id 22684)
medco.com/DS (alg 8, id 24607)
medco.com/DS (alg 8, id 29890)

com to medco.com: 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. (167.18.104.150, 167.211.104.150, TCP_-_EDNS0_4096_D_KN)
com to medco.com: 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. (167.18.104.150, 167.211.104.150, TCP_-_EDNS0_4096_D_KN)

medco.com/DS (alg 8, id 22684): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
medco.com/DS (alg 8, id 22684): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
medco.com/DS (alg 8, id 22684): 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.
medco.com/DS (alg 8, id 22684): 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.