redpilllinpro01.ring.nlnog.net

Updated: 2020-07-18 20:36:21 UTC (1617 days ago) Update now

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

Notices

DNSSEC Authentication Chain

RRset status

Secure (2)

redpilllinpro01.ring.nlnog.net/A
redpilllinpro01.ring.nlnog.net/AAAA

DNSKEY/DS/NSEC status

Secure (16)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 46594)
net/DNSKEY (alg 8, id 35886)
net/DNSKEY (alg 8, id 36059)
net/DNSKEY (alg 8, id 56519)
net/DS (alg 8, id 35886)
nlnog.net/DNSKEY (alg 13, id 14572)
nlnog.net/DS (alg 13, id 14572)
nlnog.net/DS (alg 13, id 14572)
nlnog.net/DS (alg 13, id 14572)
ring.nlnog.net/DNSKEY (alg 8, id 41746)
ring.nlnog.net/DNSKEY (alg 8, id 45046)
ring.nlnog.net/DNSKEY (alg 8, id 65139)
ring.nlnog.net/DS (alg 8, id 41746)
ring.nlnog.net/DS (alg 8, id 41746)
ring.nlnog.net/DS (alg 8, id 41746)

Delegation status

Secure (3)

. to net
net to nlnog.net
nlnog.net to ring.nlnog.net

Notices

Warnings (16)

nlnog.net/DS (alg 13, id 14572): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
nlnog.net/DS (alg 13, id 14572): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
nlnog.net/DS (alg 13, id 14572): DNSSEC implementers are prohibited from implementing signing with DS algorithm 3 (GOST 34.11-94). See RFC 8624, Sec. 3.2.
nlnog.net/DS (alg 13, id 14572): DNSSEC implementers are prohibited from implementing signing with DS algorithm 3 (GOST 34.11-94). See RFC 8624, Sec. 3.2.
nlnog.net/DS (alg 13, id 14572): 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.
nlnog.net/DS (alg 13, id 14572): 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.
nlnog.net/DS (alg 13, id 14572): Generating cryptographic hashes using algorithm 3 (GOST 34.11-94) is not supported by this code, so the cryptographic status of the DS RR is unknown. See RFC 4035, Sec. 5.2.
nlnog.net/DS (alg 13, id 14572): Generating cryptographic hashes using algorithm 3 (GOST 34.11-94) is not supported by this code, so the cryptographic status of the DS RR is unknown. See RFC 4035, Sec. 5.2.
ring.nlnog.net/DS (alg 8, id 41746): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
ring.nlnog.net/DS (alg 8, id 41746): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
ring.nlnog.net/DS (alg 8, id 41746): DNSSEC implementers are prohibited from implementing signing with DS algorithm 3 (GOST 34.11-94). See RFC 8624, Sec. 3.2.
ring.nlnog.net/DS (alg 8, id 41746): DNSSEC implementers are prohibited from implementing signing with DS algorithm 3 (GOST 34.11-94). See RFC 8624, Sec. 3.2.
ring.nlnog.net/DS (alg 8, id 41746): 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.
ring.nlnog.net/DS (alg 8, id 41746): 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.
ring.nlnog.net/DS (alg 8, id 41746): Generating cryptographic hashes using algorithm 3 (GOST 34.11-94) is not supported by this code, so the cryptographic status of the DS RR is unknown. See RFC 4035, Sec. 5.2.
ring.nlnog.net/DS (alg 8, id 41746): Generating cryptographic hashes using algorithm 3 (GOST 34.11-94) is not supported by this code, so the cryptographic status of the DS RR is unknown. See RFC 4035, Sec. 5.2.