iastate.edu
Updated:
2023-07-22 19:58:10 UTC (348 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (6)
- iastate.edu/A
- iastate.edu/MX
- iastate.edu/NS
- iastate.edu/NSEC3PARAM
- iastate.edu/SOA
- iastate.edu/TXT
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 11019)
- ./DNSKEY (alg 8, id 20326)
- edu/DNSKEY (alg 8, id 24314)
- edu/DNSKEY (alg 8, id 28065)
- edu/DS (alg 8, id 28065)
- iastate.edu/DS (alg 10, id 38658)
- iastate.edu/DS (alg 10, id 6936)
- iastate.edu/DS (alg 13, id 2618)
Non_existent (5)
- iastate.edu/DNSKEY (alg 10, id 10382)
- iastate.edu/DNSKEY (alg 10, id 38658)
- iastate.edu/DNSKEY (alg 10, id 6936)
- iastate.edu/DNSKEY (alg 13, id 2618)
- iastate.edu/DNSKEY (alg 13, id 44937)
Delegation status
Bogus (1)
- edu to iastate.edu
Secure (1)
- . to edu
Notices
Errors (13)
- edu to iastate.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.
- iastate.edu zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (129.186.67.129, 129.186.67.145, 2610:130:101:112::2, 2610:130:102:112::2, 2620:0:e50:6010::11)
- iastate.edu/DNSKEY: No response was received from the server over TCP (tried 10 times). See RFC 1035, Sec. 4.2. (128.255.13.69, TCP_-_EDNS0_4096_D_N)
- iastate.edu/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (129.186.67.129, 129.186.67.145, 2610:130:101:112::2, 2610:130:102:112::2, 2620:0:e50:6010::11, UDP_-_EDNS0_4096_D_KN, UDP_-_NOEDNS_)
- iastate.edu/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (129.186.67.129, UDP_-_EDNS0_512_D_KN)
- iastate.edu/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2610:130:101:112::2, UDP_-_EDNS0_512_D_KN)
- iastate.edu/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (128.255.13.69, 129.186.67.145, UDP_-_NOEDNS_)
- iastate.edu/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (128.255.13.69, 129.186.67.129, 129.186.67.145, 2610:130:101:112::2, 2610:130:102:112::2, 2620:0:e50:6010::11, TCP_-_EDNS0_4096_D_N)
- iastate.edu/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (128.255.13.69, 129.186.67.129, 129.186.67.145, UDP_-_NOEDNS_)
- iastate.edu/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- iastate.edu/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- myidzswvxk.iastate.edu/A has errors; select the "Denial of existence" DNSSEC option to see them.
- iastate.edu/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (9)
- RRSIG iastate.edu/A alg 10, id 10382: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG iastate.edu/MX alg 10, id 10382: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG iastate.edu/NS alg 10, id 10382: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG iastate.edu/NSEC3PARAM alg 10, id 10382: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG iastate.edu/SOA alg 10, id 10382: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG iastate.edu/TXT alg 10, id 10382: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- iastate.edu/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- myidzswvxk.iastate.edu/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- iastate.edu/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
