temple.edu

Updated: 2021-06-16 12:08:22 UTC (1262 days ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 14631)
./DNSKEY (alg 8, id 20326)
edu/DNSKEY (alg 8, id 28065)
edu/DNSKEY (alg 8, id 63587)
edu/DS (alg 8, id 28065)
temple.edu/DS (alg 8, id 59455)

edu to temple.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.
temple.edu/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (155.247.19.2, 155.247.166.2, 2607:4a80::2, 2607:4a80:80::2, UDP_-_NOEDNS_)
temple.edu/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (155.247.19.2, 155.247.166.2, 2607:4a80::2, 2607:4a80:80::2, UDP_-_EDNS0_512_D_KN)
temple.edu/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (155.247.19.2, 155.247.166.2, 2607:4a80::2, 2607:4a80:80::2, UDP_-_NOEDNS_)
temple.edu/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
temple.edu/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.

temple.edu/AAAA: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2607:4a80:80::2, UDP_-_EDNS0_4096_D_KN)
temple.edu/SOA: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2607:4a80:80::2, UDP_-_EDNS0_4096_D_KN)