crypt-app.net
Updated:
2020-09-21 03:52:04 UTC (1525 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- crypt-app.net/A
- crypt-app.net/AAAA
- crypt-app.net/MX
- crypt-app.net/NS
- crypt-app.net/SOA
- crypt-app.net/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26116)
- ./DNSKEY (alg 8, id 46594)
- crypt-app.net/DNSKEY (alg 13, id 40082)
- crypt-app.net/DNSKEY (alg 13, id 60363)
- crypt-app.net/DS (alg 13, id 60363)
- crypt-app.net/DS (alg 13, id 60363)
- net/DNSKEY (alg 8, id 35886)
- net/DNSKEY (alg 8, id 56519)
- net/DS (alg 8, id 35886)
Delegation status
Secure (2)
- . to net
- net to crypt-app.net
Notices
Errors (2)
- crypt-app.net/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- lkhcy1im4p.crypt-app.net/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
- crypt-app.net/DS (alg 13, id 60363): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- crypt-app.net/DS (alg 13, id 60363): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- crypt-app.net/DS (alg 13, id 60363): 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.
- crypt-app.net/DS (alg 13, id 60363): 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.
- crypt-app.net/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- lkhcy1im4p.crypt-app.net/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
