www.example.com
Updated:
2023-04-20 07:11:07 UTC (616 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (2)
- www.example.com/A
- www.example.com/AAAA
DNSKEY/DS/NSEC status
Secure (14)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 36739)
- com/DNSKEY (alg 8, id 46551)
- com/DS (alg 8, id 30909)
- example.com/DNSKEY (alg 8, id 17695)
- example.com/DNSKEY (alg 8, id 31406)
- example.com/DNSKEY (alg 8, id 45620)
- example.com/DNSKEY (alg 8, id 8050)
- example.com/DS (alg 8, id 31406)
- example.com/DS (alg 8, id 31406)
- example.com/DS (alg 8, id 31589)
- example.com/DS (alg 8, id 43547)
Non_existent (2)
- example.com/DNSKEY (alg 8, id 31589)
- example.com/DNSKEY (alg 8, id 43547)
Delegation status
Secure (2)
- . to com
- com to example.com
Notices
Warnings (4)
- example.com/DS (alg 8, id 31406): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- example.com/DS (alg 8, id 31406): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- example.com/DS (alg 8, id 31406): 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.
- example.com/DS (alg 8, id 31406): 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.
JavaScript is required to make the graph below interactive.
