sf-lug.net
Updated:
2024-09-24 02:17:08 UTC (28 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- sf-lug.net/A
- sf-lug.net/AAAA
- sf-lug.net/NS
- sf-lug.net/NSEC3PARAM
- sf-lug.net/SOA
- sf-lug.net/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20038)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- net/DNSKEY (alg 13, id 37331)
- net/DNSKEY (alg 13, id 42924)
- net/DS (alg 13, id 37331)
- sf-lug.net/DNSKEY (alg 13, id 13083)
- sf-lug.net/DNSKEY (alg 13, id 17437)
- sf-lug.net/DNSKEY (alg 8, id 32389)
- sf-lug.net/DNSKEY (alg 8, id 43378)
- sf-lug.net/DS (alg 8, id 32389)
- sf-lug.net/DS (alg 8, id 32389)
Delegation status
Secure (2)
- . to net
- net to sf-lug.net
Notices
Warnings (4)
- sf-lug.net/DS (alg 8, id 32389): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- sf-lug.net/DS (alg 8, id 32389): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- sf-lug.net/DS (alg 8, id 32389): 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.net/DS (alg 8, id 32389): 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.
