NSEC3 proving non-existence of nist.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 nist.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
nist.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (129.6.13.3, 129.6.13.4)
nist.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (132.163.4.10, 132.163.4.11, 2610:20:6005:13::3, 2610:20:6005:13::4, 2610:20:6b01:4::10, 2610:20:6b01:4::11)
nist.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (132.163.4.10, 132.163.4.11, 2610:20:6005:13::3, 2610:20:6005:13::4, 2610:20:6b01:4::10, 2610:20:6b01:4::11, UDP_-_NOEDNS_)
nist.gov/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (129.6.13.4, UDP_-_NOEDNS_)
nist.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (132.163.4.10, 132.163.4.11, 2610:20:6005:13::3, 2610:20:6005:13::4, 2610:20:6b01:4::10, 2610:20:6b01:4::11, UDP_-_NOEDNS_)
nist.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (129.6.13.3, 129.6.13.4, TCP_-_EDNS0_4096_D_N)
nist.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
NSEC3 proving non-existence of nist.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of nist.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
gov to nist.gov: A glue records exist for bea2.nist.gov, but there are no corresponding authoritative A records. See RFC 1034, Sec. 4.2.2.
nist.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.