NSEC3 proving non-existence of mymoney.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 mymoney.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
mymoney.gov zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9)
mymoney.gov zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9)
mymoney.gov/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, UDP_-_EDNS0_4096_D_KN)
mymoney.gov/AAAA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, UDP_-_EDNS0_4096_D_KN)
mymoney.gov/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
mymoney.gov/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, UDP_-_EDNS0_4096_D_KN)
mymoney.gov/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, TCP_-_EDNS0_4096_D_N)
mymoney.gov/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
mymoney.gov/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, UDP_-_EDNS0_4096_D_KN)
mymoney.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
btrh08meco.mymoney.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
mymoney.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
mymoney.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
mymoney.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
mymoney.gov/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
NSEC3 proving non-existence of mymoney.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of mymoney.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
gov to mymoney.gov: AAAA glue records exist for ns2.mymoney.gov, but there are no corresponding authoritative AAAA records. See RFC 1034, Sec. 4.2.2.
gov to mymoney.gov: The glue address(es) for ns1.mymoney.gov (162.159.0.236) differed from its authoritative address(es) (162.159.0.233). See RFC 1034, Sec. 4.2.2.
gov to mymoney.gov: The glue address(es) for ns1.mymoney.gov (2400:cb00:2049:1::a29f:ec) differed from its authoritative address(es) (2400:cb00:2049:1::a29f:e9). See RFC 1034, Sec. 4.2.2.
gov to mymoney.gov: The glue address(es) for ns2.mymoney.gov (162.159.1.240) differed from its authoritative address(es) (162.159.1.245). See RFC 1034, Sec. 4.2.2.
mymoney.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.