thinkingnull.com
Updated:
2021-08-11 04:23:35 UTC (1201 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- thinkingnull.com/MX
- thinkingnull.com/NS
- thinkingnull.com/SOA
- thinkingnull.com/TXT
DNSKEY/DS/NSEC status
Secure (8)
- ./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)
Delegation status
Secure (2)
- . to com
- com to thinkingnull.com
Notices
Warnings (6)
- 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.
JavaScript is required to make the graph below interactive.
