NSEC3 proving non-existence of fdms.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 fdms.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
fdms.gov zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (134.67.12.12, 161.80.212.12, 2620:117:506f:c::f00c, 2620:117:5071:d4::f00c)
fdms.gov zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (134.67.12.12, 161.80.212.12, 2620:117:506f:c::f00c, 2620:117:5071:d4::f00c)
fdms.gov/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (134.67.12.12, 161.80.212.12, 2620:117:506f:c::f00c, 2620:117:5071:d4::f00c, UDP_-_NOEDNS_)
fdms.gov/AAAA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (134.67.12.12, 161.80.212.12, 2620:117:506f:c::f00c, 2620:117:5071:d4::f00c, UDP_-_NOEDNS_)
fdms.gov/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (134.67.12.12, 161.80.212.12, 2620:117:506f:c::f00c, 2620:117:5071:d4::f00c, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
fdms.gov/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (134.67.12.12, 161.80.212.12, 2620:117:506f:c::f00c, 2620:117:5071:d4::f00c, UDP_-_NOEDNS_)
fdms.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (134.67.12.12, 161.80.212.12, 2620:117:506f:c::f00c, 2620:117:5071:d4::f00c, TCP_-_NOEDNS_)
fdms.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (134.67.12.12, 161.80.212.12, 2620:117:506f:c::f00c, 2620:117:5071:d4::f00c, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
fdms.gov/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (134.67.12.12, 161.80.212.12, 2620:117:506f:c::f00c, 2620:117:5071:d4::f00c, UDP_-_NOEDNS_)
fdms.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
fdms.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
2wiel4mgzn.fdms.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
fdms.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
fdms.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
NSEC3 proving non-existence of fdms.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of fdms.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
gov/DS (alg 8, id 7698): 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/DS (alg 8, id 7698): 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.
fdms.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
fdms.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
2wiel4mgzn.fdms.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
fdms.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.