gov to nist.gov: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11.
nist.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (129.6.14.193, 129.6.92.10, 132.163.4.10, 2610:20:6005:92::10, 2610:20:6005:2192::193, 2610:20:6b01:4::10, 2610:20:6b01:4::11)
nist.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (132.163.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, UDP_-_NOEDNS_)
nist.gov/AAAA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (132.163.4.10, UDP_-_NOEDNS_)
nist.gov/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (129.6.14.193, 129.6.92.10, 132.163.4.10, 2610:20:6005:92::10, 2610:20:6005:2192::193, 2610:20:6b01:4::10, 2610:20:6b01:4::11, UDP_-_EDNS0_4096_D_KN, UDP_-_NOEDNS_)
nist.gov/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (132.163.4.10, 2610:20:6b01:4::10, UDP_-_NOEDNS_)
nist.gov/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (132.163.4.10, UDP_-_EDNS0_512_D_KN)
nist.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (129.6.92.10, 132.163.4.11, 2610:20:6005:92::10, 2610:20:6b01:4::10, UDP_-_NOEDNS_)
nist.gov/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (129.6.92.10, 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.14.193, 129.6.92.10, 132.163.4.10, 2610:20:6005:92::10, 2610:20:6005:2192::193, 2610:20:6b01:4::10, 2610:20:6b01:4::11, TCP_-_EDNS0_4096_D_N)
nist.gov/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (129.6.92.10, 132.163.4.10, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
nist.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
nist.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
5uia98ndg4.nist.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (21)
RRSIG nist.gov/A alg 7, id 54557: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG nist.gov/A alg 7, id 8882: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG nist.gov/AAAA alg 7, id 54557: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG nist.gov/AAAA alg 7, id 8882: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG nist.gov/MX alg 7, id 54557: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG nist.gov/MX alg 7, id 8882: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG nist.gov/NS alg 7, id 54557: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG nist.gov/NS alg 7, id 8882: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG nist.gov/NSEC3PARAM alg 7, id 54557: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG nist.gov/NSEC3PARAM alg 7, id 8882: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG nist.gov/SOA alg 7, id 54557: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG nist.gov/SOA alg 7, id 54557: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG nist.gov/SOA alg 7, id 8882: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG nist.gov/SOA alg 7, id 8882: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG nist.gov/TXT alg 7, id 54557: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG nist.gov/TXT alg 7, id 8882: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
nist.gov/DS (alg 7, id 35565): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
nist.gov/DS (alg 7, id 35565): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
nist.gov/DS (alg 7, id 35565): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
nist.gov/DS (alg 7, id 35565): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
nist.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.