kth.se
Updated:
2023-04-05 17:24:04 UTC (598 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- kth.se/A
- kth.se/AAAA
- kth.se/MX
- kth.se/NS
- kth.se/SOA
- kth.se/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- ./DNSKEY (alg 8, id 951)
- kth.se/DNSKEY (alg 8, id 35811)
- kth.se/DNSKEY (alg 8, id 52831)
- kth.se/DS (alg 8, id 52831)
- kth.se/DS (alg 8, id 52831)
- se/DNSKEY (alg 8, id 24984)
- se/DNSKEY (alg 8, id 59407)
- se/DS (alg 8, id 59407)
Delegation status
Secure (2)
- . to se
- se to kth.se
Notices
Errors (1)
- se zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:678:e:112::53)
Warnings (4)
- kth.se/DS (alg 8, id 52831): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- kth.se/DS (alg 8, id 52831): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- kth.se/DS (alg 8, id 52831): 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.
- kth.se/DS (alg 8, id 52831): 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.
