_pgpkey-http._tcp.keys.openpgp.org
Updated:
2020-07-13 18:56:45 UTC (1622 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- _pgpkey-http._tcp.keys.openpgp.org/SRV (NXDOMAIN)
- _tcp.keys.openpgp.org/NS (NXDOMAIN)
- keys.openpgp.org/A
- keys.openpgp.org/AAAA
- keys.openpgp.org/SOA
DNSKEY/DS/NSEC status
Secure (15)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46594)
- NSEC3 proving non-existence of _pgpkey-http._tcp.keys.openpgp.org/SRV
- NSEC3 proving non-existence of _tcp.keys.openpgp.org/NS
- keys.openpgp.org/DNSKEY (alg 8, id 14555)
- keys.openpgp.org/DNSKEY (alg 8, id 30465)
- keys.openpgp.org/DS (alg 8, id 14555)
- openpgp.org/DNSKEY (alg 8, id 26041)
- openpgp.org/DNSKEY (alg 8, id 63435)
- openpgp.org/DS (alg 8, id 26041)
- org/DNSKEY (alg 7, id 17883)
- org/DNSKEY (alg 7, id 21869)
- org/DNSKEY (alg 7, id 27353)
- org/DS (alg 7, id 17883)
- org/DS (alg 7, id 17883)
Delegation status
Secure (3)
- . to org
- openpgp.org to keys.openpgp.org
- org to openpgp.org
Notices
Errors (5)
- NSEC3 proving non-existence of _pgpkey-http._tcp.keys.openpgp.org/SRV: 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 _pgpkey-http._tcp.keys.openpgp.org/SRV: 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 _tcp.keys.openpgp.org/NS: 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 _tcp.keys.openpgp.org/NS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- keys.openpgp.org/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (16)
- NSEC3 proving non-existence of _pgpkey-http._tcp.keys.openpgp.org/SRV: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of _pgpkey-http._tcp.keys.openpgp.org/SRV: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of _tcp.keys.openpgp.org/NS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of _tcp.keys.openpgp.org/NS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- RRSIG openpgp.org/DS alg 7, id 27353: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG org/DNSKEY alg 7, id 17883: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG org/DNSKEY alg 7, id 17883: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG org/DNSKEY alg 7, id 17883: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG org/DNSKEY alg 7, id 27353: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG org/DNSKEY alg 7, id 27353: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG org/DNSKEY alg 7, id 27353: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- org/DS (alg 7, id 17883): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- org/DS (alg 7, id 17883): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- org/DS (alg 7, id 17883): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- org/DS (alg 7, id 17883): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- keys.openpgp.org/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
