patriotbonds.gov
Updated:
2023-05-02 17:37:14 UTC (571 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 patriotbonds.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 patriotbonds.gov
Secure (1)
- . to gov
Notices
Errors (7)
- NSEC3 proving non-existence of patriotbonds.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 patriotbonds.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- patriotbonds.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (166.123.208.16, 166.123.208.17)
- patriotbonds.gov zone: There was an error resolving the following NS name(s) to address(es): ns1.patriotbonds.gov, ns2.patriotbonds.gov
- patriotbonds.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (166.123.208.16, 166.123.208.17, UDP_-_NOEDNS_)
- patriotbonds.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (166.123.208.16, 166.123.208.17, UDP_-_NOEDNS_)
- patriotbonds.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
- NSEC3 proving non-existence of patriotbonds.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of patriotbonds.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- patriotbonds.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
