www.ietf.org

Updated: 2020-11-03 12:51:39 UTC (1432 days ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

Notices

DNSSEC Authentication Chain

RRset status

Secure (3)

www.ietf.org.cdn.cloudflare.net/A
www.ietf.org.cdn.cloudflare.net/AAAA
www.ietf.org/CNAME

DNSKEY/DS/NSEC status

Secure (16)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 26116)
cloudflare.net/DNSKEY (alg 13, id 2371)
cloudflare.net/DNSKEY (alg 13, id 34505)
cloudflare.net/DS (alg 13, id 2371)
ietf.org/DNSKEY (alg 5, id 40452)
ietf.org/DNSKEY (alg 5, id 45586)
ietf.org/DS (alg 5, id 45586)
ietf.org/DS (alg 5, id 45586)
net/DNSKEY (alg 8, id 15314)
net/DNSKEY (alg 8, id 35886)
net/DS (alg 8, id 35886)
org/DNSKEY (alg 8, id 26974)
org/DNSKEY (alg 8, id 34266)
org/DNSKEY (alg 8, id 63858)
org/DS (alg 8, id 26974)

Delegation status

Secure (4)

. to net
. to org
net to cloudflare.net
org to ietf.org

Notices

Errors (4)

ietf.org zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2a01:8840:6::1)
ietf.org/DNSKEY: No response was received from the server over UDP (tried 14 times). See RFC 1035, Sec. 4.2. (4.31.198.40, 2001:1900:3001:11::28, UDP_-_EDNS0_4096_D_K)
ietf.org/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (4.31.198.40, 2001:1900:3001:11::28, UDP_-_EDNS0_512_D_K)
ietf.org/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (11)

RRSIG ietf.org/DNSKEY alg 5, id 40452: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG ietf.org/DNSKEY alg 5, id 40452: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG ietf.org/DNSKEY alg 5, id 45586: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG ietf.org/DNSKEY alg 5, id 45586: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG www.ietf.org/CNAME alg 5, id 40452: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG www.ietf.org/CNAME alg 5, id 40452: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
ietf.org/DS (alg 5, id 45586): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
ietf.org/DS (alg 5, id 45586): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
ietf.org/DS (alg 5, id 45586): 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.
ietf.org/DS (alg 5, id 45586): 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.
ietf.org/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.