sf-lug.com
Updated:
2024-10-01 05:42:26 UTC (52 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (8)
- sf-lug.com/A
- sf-lug.com/AAAA
- sf-lug.com/CDNSKEY
- sf-lug.com/CDS
- sf-lug.com/NS
- sf-lug.com/NSEC3PARAM
- sf-lug.com/SOA
- sf-lug.com/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20038)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- com/DNSKEY (alg 13, id 19718)
- com/DNSKEY (alg 13, id 59354)
- com/DS (alg 13, id 19718)
- sf-lug.com/DNSKEY (alg 13, id 44197)
- sf-lug.com/DNSKEY (alg 13, id 55302)
- sf-lug.com/DNSKEY (alg 8, id 3078)
- sf-lug.com/DNSKEY (alg 8, id 33646)
- sf-lug.com/DS (alg 8, id 33646)
- sf-lug.com/DS (alg 8, id 33646)
Delegation status
Secure (2)
- . to com
- com to sf-lug.com
Notices
Warnings (6)
- sf-lug.com/CDNSKEY: The contents of the DS RRset are inconsistent with those of the CDNSKEY RRset. See RFC 7344, Sec. 3, RFC 7344, Sec. 5.
- sf-lug.com/CDS: The contents of the DS RRset are inconsistent with those of the CDS RRset. See RFC 7344, Sec. 3, RFC 7344, Sec. 5.
- sf-lug.com/DS (alg 8, id 33646): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- sf-lug.com/DS (alg 8, id 33646): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- sf-lug.com/DS (alg 8, id 33646): 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.
- sf-lug.com/DS (alg 8, id 33646): 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.
