uni-stuttgart.de
Updated:
2021-09-21 13:01:33 UTC (1163 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (1)
- uni-stuttgart.de/NSEC3PARAM (NODATA)
Secure (7)
- uni-stuttgart.de/A
- uni-stuttgart.de/AAAA
- uni-stuttgart.de/MX
- uni-stuttgart.de/NS
- uni-stuttgart.de/NSEC3PARAM
- uni-stuttgart.de/SOA
- uni-stuttgart.de/TXT
DNSKEY/DS/NSEC status
Bogus (1)
- NSEC proving non-existence of uni-stuttgart.de/NSEC3PARAM
Secure (9)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- de/DNSKEY (alg 8, id 26755)
- de/DNSKEY (alg 8, id 54729)
- de/DS (alg 8, id 26755)
- uni-stuttgart.de/DNSKEY (alg 10, id 26499)
- uni-stuttgart.de/DNSKEY (alg 10, id 28968)
- uni-stuttgart.de/DS (alg 10, id 26499)
Delegation status
Secure (2)
- . to de
- de to uni-stuttgart.de
Notices
Errors (9)
- NSEC proving non-existence of uni-stuttgart.de/NSEC3PARAM: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (129.143.253.133, 2001:7c0::53:10, 2001:7c0:0:253::133, UDP_-_EDNS0_4096_D_KN)
- NSEC proving non-existence of uni-stuttgart.de/NSEC3PARAM: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (129.143.253.133, 2001:7c0::53:10, 2001:7c0:0:253::133, UDP_-_EDNS0_4096_D_KN)
- NSEC proving non-existence of uni-stuttgart.de/NSEC3PARAM: The following queries resulted in an answer response, even though the bitmap in the NSEC RR indicates that the queried records don't exist: uni-stuttgart.de/NSEC3PARAM See RFC 4035, Sec. 3.1.3.1.
- NSEC proving non-existence of uni-stuttgart.de/NSEC3PARAM: The following queries resulted in an answer response, even though the bitmap in the NSEC RR indicates that the queried records don't exist: uni-stuttgart.de/NSEC3PARAM See RFC 4035, Sec. 3.1.3.1.
- uni-stuttgart.de/DNSKEY: No response was received from the server over UDP (tried 15 times). See RFC 1035, Sec. 4.2. (129.143.2.10, UDP_-_EDNS0_4096_D)
- uni-stuttgart.de/NSEC3PARAM: No response was received from the server over TCP (tried 5 times). See RFC 1035, Sec. 4.2. (129.143.2.10, TCP_-_EDNS0_4096_D_KN)
- uni-stuttgart.de/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- 3fg8xpiz1j.uni-stuttgart.de/A has errors; select the "Denial of existence" DNSSEC option to see them.
- uni-stuttgart.de/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (16)
- RRSIG uni-stuttgart.de/A alg 10, id 28968: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG uni-stuttgart.de/AAAA alg 10, id 28968: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG uni-stuttgart.de/DNSKEY alg 10, id 26499: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG uni-stuttgart.de/DNSKEY alg 10, id 26499: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG uni-stuttgart.de/DNSKEY alg 10, id 28968: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG uni-stuttgart.de/DNSKEY alg 10, id 28968: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG uni-stuttgart.de/MX alg 10, id 28968: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG uni-stuttgart.de/NS alg 10, id 28968: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG uni-stuttgart.de/NSEC3PARAM alg 10, id 28968: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG uni-stuttgart.de/SOA alg 10, id 28968: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG uni-stuttgart.de/SOA alg 10, id 28968: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG uni-stuttgart.de/TXT alg 10, id 28968: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- uni-stuttgart.de/TXT: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (129.143.2.10, UDP_-_EDNS0_4096_D_KN)
- uni-stuttgart.de/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- 3fg8xpiz1j.uni-stuttgart.de/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- uni-stuttgart.de/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
