ns.cs.uni-magdeburg.de
Updated:
2020-11-11 08:07:37 UTC (1519 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (2)
- ns.cs.uni-magdeburg.de/A
- uni-magdeburg.de/SOA
Secure (1)
- de/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26116)
- NSEC3 proving non-existence of uni-magdeburg.de/DS
- de/DNSKEY (alg 8, id 45580)
- de/DNSKEY (alg 8, id 7095)
- de/DS (alg 8, id 45580)
Delegation status
Insecure (2)
- de to uni-magdeburg.de
- uni-magdeburg.de to cs.uni-magdeburg.de
Secure (1)
- . to de
Notices
Errors (2)
- NSEC3 proving non-existence of uni-magdeburg.de/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of uni-magdeburg.de/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
Warnings (3)
- NSEC3 proving non-existence of uni-magdeburg.de/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of uni-magdeburg.de/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- uni-magdeburg.de to cs.uni-magdeburg.de: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the uni-magdeburg.de zone): max.cs.uni-magdeburg.de, luxator.cs.uni-magdeburg.de See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
