example.org
Updated:
2022-09-13 06:51:32 UTC (802 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- example.org/A
- example.org/AAAA
- example.org/MX
- example.org/NS
- example.org/SOA
- example.org/TXT
DNSKEY/DS/NSEC status
Secure (13)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 20826)
- example.org/DNSKEY (alg 8, id 28020)
- example.org/DNSKEY (alg 8, id 3397)
- example.org/DNSKEY (alg 8, id 7574)
- example.org/DS (alg 8, id 31589)
- example.org/DS (alg 8, id 3397)
- example.org/DS (alg 8, id 3397)
- example.org/DS (alg 8, id 37780)
- org/DNSKEY (alg 8, id 26974)
- org/DNSKEY (alg 8, id 29166)
- org/DNSKEY (alg 8, id 56124)
- org/DS (alg 8, id 26974)
Non_existent (2)
- example.org/DNSKEY (alg 8, id 31589)
- example.org/DNSKEY (alg 8, id 37780)
Delegation status
Secure (2)
- . to org
- org to example.org
Notices
Warnings (4)
- example.org/DS (alg 8, id 3397): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- example.org/DS (alg 8, id 3397): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- example.org/DS (alg 8, id 3397): 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.org/DS (alg 8, id 3397): 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.
