wisc.edu
Updated:
2020-03-21 11:33:23 UTC (1710 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (1)
- wisc.edu/SOA
Secure (5)
- wisc.edu/A
- wisc.edu/MX
- wisc.edu/NS
- wisc.edu/SOA
- wisc.edu/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 33853)
- edu/DNSKEY (alg 8, id 28065)
- edu/DNSKEY (alg 8, id 50054)
- edu/DS (alg 8, id 28065)
- wisc.edu/DNSKEY (alg 8, id 28440)
- wisc.edu/DNSKEY (alg 8, id 31998)
- wisc.edu/DNSKEY (alg 8, id 50371)
- wisc.edu/DS (alg 8, id 50371)
- wisc.edu/DS (alg 8, id 50371)
Delegation status
Secure (2)
- . to edu
- edu to wisc.edu
Notices
Errors (13)
- edu to wisc.edu: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (192.12.80.222, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- edu to wisc.edu: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (192.12.80.222, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- wisc.edu/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (192.12.80.222, UDP_-_EDNS0_4096_D_K)
- wisc.edu/DNSKEY (alg 8, id 31998): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (192.12.80.222, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- wisc.edu/DNSKEY (alg 8, id 50371): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (192.12.80.222, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- wisc.edu/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (192.12.80.222, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- wisc.edu/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (192.12.80.222, UDP_-_EDNS0_4096_D_K)
- wisc.edu/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (192.12.80.222, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
- wisc.edu/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (192.12.80.222, UDP_-_EDNS0_4096_D_K)
- wisc.edu/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- wisc.edu/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- nbq8dl6zc1.wisc.edu/A has errors; select the "Denial of existence" DNSSEC option to see them.
- wisc.edu/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
- edu to wisc.edu: The glue address(es) for adns1.doit.wisc.edu (2607:f388::a53:1) differed from its authoritative address(es) (2607:f388::a53:1, 2607:f388:2:2001::100a). See RFC 1034, Sec. 4.2.2.
- edu to wisc.edu: The glue address(es) for adns2.doit.wisc.edu (2607:f388::a53:2) differed from its authoritative address(es) (2607:f388::a53:2, 2607:f388:d:2::1006). See RFC 1034, Sec. 4.2.2.
- edu to wisc.edu: The glue address(es) for adns3.doit.wisc.edu (2607:f388::a53:3) differed from its authoritative address(es) (2607:f388::a53:3, 2607:f388:2:2001::100b). See RFC 1034, Sec. 4.2.2.
- wisc.edu/DNSKEY (alg 8, id 28440): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (192.12.80.222, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- wisc.edu/DS (alg 8, id 50371): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- wisc.edu/DS (alg 8, id 50371): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- wisc.edu/DS (alg 8, id 50371): 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.
- wisc.edu/DS (alg 8, id 50371): 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.
