www.ietf.org

Updated: 2020-05-10 21:52:18 UTC (1609 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 (17)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 48903)
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 35886)
net/DNSKEY (alg 8, id 36059)
net/DS (alg 8, id 35886)
org/DNSKEY (alg 7, id 17883)
org/DNSKEY (alg 7, id 27074)
org/DNSKEY (alg 7, id 62165)
org/DS (alg 7, id 17883)
org/DS (alg 7, id 17883)

Delegation status

Secure (4)

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

Notices

Errors (2)

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 (25)

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 ietf.org/DS alg 7, id 27074: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG ietf.org/DS alg 7, id 27074: 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 27074: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG org/DNSKEY alg 7, id 27074: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG org/DNSKEY alg 7, id 27074: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). 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/DNSKEY (alg 5, id 40452): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2001:1900:3001:11::28, UDP_-_EDNS0_4096_D_K)
ietf.org/DNSKEY (alg 5, id 45586): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2001:1900:3001:11::28, UDP_-_EDNS0_4096_D_K)
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.
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.
ietf.org/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.