_25._tcp.mail.nic.cl
Updated:
2023-10-19 17:19:14 UTC (399 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- _25._tcp.mail.nic.cl/TLSA (NXDOMAIN)
- _tcp.mail.nic.cl/NS (NXDOMAIN)
- mail.nic.cl/A
- mail.nic.cl/AAAA
- nic.cl/SOA
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46780)
- NSEC3 proving non-existence of _25._tcp.mail.nic.cl/TLSA
- NSEC3 proving non-existence of _tcp.mail.nic.cl/NS
- cl/DNSKEY (alg 8, id 21199)
- cl/DNSKEY (alg 8, id 43710)
- cl/DNSKEY (alg 8, id 51141)
- cl/DS (alg 8, id 21199)
- nic.cl/DNSKEY (alg 13, id 27364)
- nic.cl/DNSKEY (alg 13, id 33134)
- nic.cl/DNSKEY (alg 13, id 41391)
- nic.cl/DS (alg 13, id 27364)
Delegation status
Secure (2)
- . to cl
- cl to nic.cl
Notices
Errors (5)
- NSEC3 proving non-existence of _25._tcp.mail.nic.cl/TLSA: 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 _25._tcp.mail.nic.cl/TLSA: 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 _tcp.mail.nic.cl/NS: 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 _tcp.mail.nic.cl/NS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- nic.cl/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
- NSEC3 proving non-existence of _25._tcp.mail.nic.cl/TLSA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of _25._tcp.mail.nic.cl/TLSA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of _tcp.mail.nic.cl/NS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of _tcp.mail.nic.cl/NS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- nic.cl/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
