mymoney.gov
Updated:
2023-06-08 05:23:51 UTC (533 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (1)
- gov/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- NSEC3 proving non-existence of mymoney.gov/DS
- gov/DNSKEY (alg 8, id 50011)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Lame (1)
- gov to mymoney.gov
Secure (1)
- . to gov
Notices
Errors (18)
- 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.236, 162.159.1.240, 2400:cb00:2049:1::a29f:ec, 2400:cb00:2049:1::a29f:1f0)
- 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.236, 162.159.1.240, 2400:cb00:2049:1::a29f:ec, 2400:cb00:2049:1::a29f:1f0)
- mymoney.gov zone: There was an error resolving the following NS name(s) to address(es): ns1.mymoney.gov, ns2.mymoney.gov
- mymoney.gov/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (162.159.0.236, 162.159.1.240, 2400:cb00:2049:1::a29f:ec, 2400:cb00:2049:1::a29f:1f0, 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.236, 162.159.1.240, 2400:cb00:2049:1::a29f:ec, 2400:cb00:2049:1::a29f:1f0, 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.236, 162.159.1.240, 2400:cb00:2049:1::a29f:ec, 2400:cb00:2049:1::a29f:1f0, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- mymoney.gov/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (162.159.0.236, 162.159.1.240, 2400:cb00:2049:1::a29f:ec, 2400:cb00:2049:1::a29f:1f0, 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.236, 162.159.1.240, 2400:cb00:2049:1::a29f:ec, 2400:cb00:2049:1::a29f:1f0, UDP_-_EDNS0_4096_D_KN)
- mymoney.gov/NSEC3PARAM: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (162.159.0.236, 162.159.1.240, 2400:cb00:2049:1::a29f:ec, 2400:cb00:2049:1::a29f:1f0, 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.236, 162.159.1.240, 2400:cb00:2049:1::a29f:ec, 2400:cb00:2049:1::a29f:1f0, 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.236, 162.159.1.240, 2400:cb00:2049:1::a29f:ec, 2400:cb00:2049:1::a29f:1f0, 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.236, 162.159.1.240, 2400:cb00:2049:1::a29f:ec, 2400:cb00:2049:1::a29f:1f0, UDP_-_EDNS0_4096_D_KN)
- 5zk2oj4t8u.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.
Warnings (3)
- 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.
- mymoney.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
