NSEC3 proving non-existence of gov.tr/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 gov.tr/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
gov.tr/MX has errors; select the "Denial of existence" DNSSEC option to see them.
gov.tr/A has errors; select the "Denial of existence" DNSSEC option to see them.
gov.tr/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
gov.tr/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
gov.tr/DS has errors; select the "Denial of existence" DNSSEC option to see them.
i0cam1sg7j.gov.tr/A has errors; select the "Denial of existence" DNSSEC option to see them.
gov.tr/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
NSEC3 proving non-existence of gov.tr/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of gov.tr/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
gov.tr/SOA: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (185.7.0.2, UDP_-_EDNS0_4096_D_KN_0x20)
gov.tr/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
gov.tr/A has warnings; select the "Denial of existence" DNSSEC option to see them.
gov.tr/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
gov.tr/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
gov.tr/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
i0cam1sg7j.gov.tr/A has warnings; select the "Denial of existence" DNSSEC option to see them.
gov.tr/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.