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