NSEC3 proving non-existence of mypay.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 mypay.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
mypay.gov zone: The following NS name(s) did not resolve to address(es): dns19.dfas.mil, dns2.dfas.mil, dns23.dfas.mil
mypay.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (206.39.12.245, 207.133.150.245, 207.133.248.245)
mypay.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (206.39.12.245, 207.133.150.245, 207.133.248.245, UDP_-_NOEDNS_)
mypay.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (206.39.12.245, 207.133.150.245, 207.133.248.245, UDP_-_NOEDNS_)
mypay.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
NSEC3 proving non-existence of mypay.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of mypay.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.
mypay.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.