sflug.org
Updated:
2024-09-30 03:47:22 UTC (22 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (8)
- sflug.org/A
- sflug.org/AAAA
- sflug.org/CDNSKEY
- sflug.org/CDS
- sflug.org/NS
- sflug.org/NSEC3PARAM
- sflug.org/SOA
- sflug.org/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20038)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- org/DNSKEY (alg 8, id 15678)
- org/DNSKEY (alg 8, id 23064)
- org/DNSKEY (alg 8, id 26974)
- org/DS (alg 8, id 26974)
- sflug.org/DNSKEY (alg 8, id 45182)
- sflug.org/DNSKEY (alg 8, id 47230)
- sflug.org/DNSKEY (alg 8, id 55585)
- sflug.org/DS (alg 8, id 55585)
- sflug.org/DS (alg 8, id 55585)
Delegation status
Secure (2)
- . to org
- org to sflug.org
Notices
Warnings (5)
- sflug.org/CDS: The contents of the DS RRset are inconsistent with those of the CDS RRset. See RFC 7344, Sec. 3, RFC 7344, Sec. 5.
- sflug.org/DS (alg 8, id 55585): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- sflug.org/DS (alg 8, id 55585): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- sflug.org/DS (alg 8, id 55585): 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.
- sflug.org/DS (alg 8, id 55585): 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.
