NSEC3 proving non-existence of aftac.gov/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 aftac.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
aftac.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (198.47.84.12)
aftac.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (198.47.84.11)
aftac.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (198.47.84.11, UDP_-_NOEDNS_)
aftac.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (198.47.84.12, TCP_-_EDNS0_4096_D_N)
aftac.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
aftac.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
NSEC3 proving non-existence of aftac.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of aftac.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
aftac.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.