globalchange.gov
Updated:
2021-12-16 15:27:00 UTC (1070 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- globalchange.gov/A
- globalchange.gov/MX
- globalchange.gov/NS
- globalchange.gov/SOA
- globalchange.gov/TXT
Secure (1)
- gov/SOA
DNSKEY/DS/NSEC status
Insecure (2)
- globalchange.gov/DNSKEY (alg 5, id 46873)
- globalchange.gov/DNSKEY (alg 5, id 55605)
Secure (6)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of globalchange.gov/DS
- gov/DNSKEY (alg 8, id 6229)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Insecure (1)
- gov to globalchange.gov
Secure (1)
- . to gov
Notices
Errors (3)
- NSEC3 proving non-existence of globalchange.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 globalchange.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- globalchange.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (17)
- NSEC3 proving non-existence of globalchange.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of globalchange.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- RRSIG globalchange.gov/A alg 5, id 55605: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG globalchange.gov/DNSKEY alg 5, id 46873: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG globalchange.gov/DNSKEY alg 5, id 46873: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG globalchange.gov/DNSKEY alg 5, id 55605: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG globalchange.gov/DNSKEY alg 5, id 55605: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG globalchange.gov/MX alg 5, id 55605: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG globalchange.gov/NS alg 5, id 55605: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG globalchange.gov/SOA alg 5, id 55605: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG globalchange.gov/TXT alg 5, id 55605: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- globalchange.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- globalchange.gov/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
- globalchange.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- globalchange.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- h51sq4to28.globalchange.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- globalchange.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
