amanite.site
Updated:
2020-12-14 09:14:26 UTC (4 years ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (3)
- amanite.site/MX
- amanite.site/NS
- amanite.site/SOA
Secure (1)
- site/SOA
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26116)
- NSEC3 proving non-existence of amanite.site/DS
- site/DNSKEY (alg 8, id 18264)
- site/DNSKEY (alg 8, id 51144)
- site/DNSKEY (alg 8, id 51676)
- site/DS (alg 8, id 51676)
- site/DS (alg 8, id 51676)
Delegation status
Insecure (1)
- site to amanite.site
Secure (1)
- . to site
Notices
Errors (3)
- NSEC3 proving non-existence of amanite.site/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of amanite.site/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- amanite.site/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- site/DS (alg 8, id 51676): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- site/DS (alg 8, id 51676): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- site/DS (alg 8, id 51676): 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.
- site/DS (alg 8, id 51676): 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.
JavaScript is required to make the graph below interactive.
