thinkingnull.com

Updated: 2021-08-09 14:41:13 UTC (1200 days ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 26838)
com/DNSKEY (alg 8, id 30909)
com/DNSKEY (alg 8, id 39343)
com/DS (alg 8, id 30909)
thinkingnull.com/DNSKEY (alg 13, id 60891)
thinkingnull.com/DS (alg 13, id 60891)
thinkingnull.com/DS (alg 13, id 60891)

com to thinkingnull.com: The following NS name(s) were found in the delegation NS RRset (i.e., in the com zone), but not in the authoritative NS RRset: ns0.thinkingnull.com See RFC 1034, Sec. 4.2.2.
thinkingnull.com/DS (alg 13, id 60891): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
thinkingnull.com/DS (alg 13, id 60891): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
thinkingnull.com/DS (alg 13, id 60891): 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.
thinkingnull.com/DS (alg 13, id 60891): 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.
thinkingnull.com/DS (alg 13, id 60891): In the spirit of RFC 4509, DS records with digest type 1 (SHA-1) might be ignored when DS records with digest type 4 (SHA-384) exist in the same RRset. See RFC 4509, Sec. 3.
thinkingnull.com/DS (alg 13, id 60891): In the spirit of RFC 4509, DS records with digest type 1 (SHA-1) might be ignored when DS records with digest type 4 (SHA-384) exist in the same RRset. See RFC 4509, Sec. 3.