goes-r.gov
Updated:
2022-01-20 19:26:00 UTC (1066 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (4)
- goes-r.gov/A
- goes-r.gov/NS
- goes-r.gov/SOA
- goes-r.gov/TXT
Secure (1)
- gov/SOA
DNSKEY/DS/NSEC status
Insecure (3)
- goes-r.gov/DNSKEY (alg 5, id 43594)
- goes-r.gov/DNSKEY (alg 5, id 57747)
- goes-r.gov/DNSKEY (alg 5, id 64470)
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- NSEC3 proving non-existence of goes-r.gov/DS
- gov/DNSKEY (alg 8, id 6229)
- gov/DNSKEY (alg 8, id 7030)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Insecure (1)
- gov to goes-r.gov
Secure (1)
- . to gov
Notices
Errors (3)
- NSEC3 proving non-existence of goes-r.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 goes-r.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- goes-r.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (19)
- NSEC3 proving non-existence of goes-r.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of goes-r.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- RRSIG goes-r.gov/A alg 5, id 64470: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG goes-r.gov/DNSKEY alg 5, id 43594: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG goes-r.gov/DNSKEY alg 5, id 43594: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG goes-r.gov/DNSKEY alg 5, id 43594: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG goes-r.gov/DNSKEY alg 5, id 64470: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG goes-r.gov/DNSKEY alg 5, id 64470: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG goes-r.gov/DNSKEY alg 5, id 64470: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG goes-r.gov/NS alg 5, id 64470: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG goes-r.gov/SOA alg 5, id 64470: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG goes-r.gov/TXT alg 5, id 64470: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- goes-r.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- goes-r.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- goes-r.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- goes-r.gov/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
- goes-r.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- goes-r.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
- hgfk9impyr.goes-r.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
