fdsys.gov/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (162.140.15.100, 162.140.254.200, UDP_-_EDNS0_4096_D_KN)
fdsys.gov/DNSKEY (alg 8, id 27885): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (162.140.15.100, 162.140.254.200, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
fdsys.gov/DNSKEY (alg 8, id 41200): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (162.140.15.100, 162.140.254.200, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
fdsys.gov/DNSKEY: The response (451 bytes) was malformed. (162.140.64.100, 162.140.252.180, UDP_-_EDNS0_512_D_KN)
fdsys.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (162.140.15.100, 162.140.254.200, UDP_-_EDNS0_4096_D_KN)
fdsys.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (162.140.15.100, 162.140.254.200, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
fdsys.gov/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (162.140.15.100, 162.140.254.200, UDP_-_EDNS0_4096_D_KN)
gov to fdsys.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. (162.140.15.100, 162.140.254.200, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
gov to fdsys.gov: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.15.100, 162.140.254.200, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
fdsys.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
fdsys.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
fdsys.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
fdsys.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
up6jdm1gqf.fdsys.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (9)
fdsys.gov/DS (alg 8, id 41200): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
fdsys.gov/DS (alg 8, id 41200): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
fdsys.gov/DS (alg 8, id 41200): 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.
fdsys.gov/DS (alg 8, id 41200): 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.
gov to fdsys.gov: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gov zone): ns3.fdsys.gov, ns4.fdsys.gov See RFC 1034, Sec. 4.2.2.
fdsys.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
fdsys.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
fdsys.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
up6jdm1gqf.fdsys.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.