uni-bielefeld.de
Updated:
2024-10-18 13:05:37 UTC (73 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- uni-bielefeld.de/A
- uni-bielefeld.de/MX
- uni-bielefeld.de/NS
- uni-bielefeld.de/NSEC3PARAM
- uni-bielefeld.de/SOA
- uni-bielefeld.de/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- de/DNSKEY (alg 8, id 26755)
- de/DNSKEY (alg 8, id 28278)
- de/DNSKEY (alg 8, id 39783)
- de/DS (alg 8, id 26755)
- uni-bielefeld.de/DNSKEY (alg 10, id 61267)
- uni-bielefeld.de/DNSKEY (alg 10, id 64763)
- uni-bielefeld.de/DNSKEY (alg 10, id 7884)
- uni-bielefeld.de/DS (alg 10, id 20092)
- uni-bielefeld.de/DS (alg 10, id 7884)
Non_existent (1)
- uni-bielefeld.de/DNSKEY (alg 10, id 20092)
Delegation status
Secure (2)
- . to de
- de to uni-bielefeld.de
Notices
Warnings (18)
- RRSIG uni-bielefeld.de/A alg 10, id 64763: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG uni-bielefeld.de/DNSKEY alg 10, id 61267: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG uni-bielefeld.de/DNSKEY alg 10, id 61267: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG uni-bielefeld.de/DNSKEY alg 10, id 61267: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG uni-bielefeld.de/DNSKEY alg 10, id 7884: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG uni-bielefeld.de/DNSKEY alg 10, id 7884: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG uni-bielefeld.de/DNSKEY alg 10, id 7884: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG uni-bielefeld.de/MX alg 10, id 64763: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG uni-bielefeld.de/NS alg 10, id 64763: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG uni-bielefeld.de/NSEC3PARAM alg 10, id 64763: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG uni-bielefeld.de/SOA alg 10, id 64763: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG uni-bielefeld.de/TXT alg 10, id 64763: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- uni-bielefeld.de/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
- uni-bielefeld.de/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- uni-bielefeld.de/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- uni-bielefeld.de/CDNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- uni-bielefeld.de/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- 3kr7l.vuolx.uni-bielefeld.de/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
