tsp.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.186)
tsp.gov/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.186, UDP_-_NOEDNS_)
tsp.gov/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.186, 149.101.182.186, UDP_-_NOEDNS_)
tsp.gov/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.186, UDP_-_NOEDNS_)
tsp.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.186, TCP_-_EDNS0_4096_D_N)
tsp.gov/SOA: No response was received from the server over TCP (tried 5 times). See RFC 1035, Sec. 4.2. (149.101.182.185, TCP_-_EDNS0_4096_D_N)
tsp.gov/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.186, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
tsp.gov/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.186, UDP_-_NOEDNS_)
tsp.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
oike1sf24b.tsp.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
tsp.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
tsp.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (21)
tsp.gov/DNSKEY (alg 8, id 14596): 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. (149.101.182.185, UDP_-_EDNS0_4096_D_KN)
tsp.gov/DNSKEY (alg 8, id 32520): 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. (149.101.182.185, UDP_-_EDNS0_4096_D_KN)
tsp.gov/DNSKEY (alg 8, id 46143): 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. (149.101.182.185, UDP_-_EDNS0_4096_D_KN)
tsp.gov/DNSKEY (alg 8, id 51316): 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. (149.101.182.185, UDP_-_EDNS0_4096_D_KN)
tsp.gov/DS (alg 8, id 14596): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
tsp.gov/DS (alg 8, id 14596): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
tsp.gov/DS (alg 8, id 14596): 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.
tsp.gov/DS (alg 8, id 14596): 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.
tsp.gov/DS (alg 8, id 47764): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
tsp.gov/DS (alg 8, id 47764): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
tsp.gov/DS (alg 8, id 47764): 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.
tsp.gov/DS (alg 8, id 47764): 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.
tsp.gov/DS (alg 8, id 51316): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
tsp.gov/DS (alg 8, id 51316): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
tsp.gov/DS (alg 8, id 51316): 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.
tsp.gov/DS (alg 8, id 51316): 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.
tsp.gov/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. (149.101.182.185, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
tsp.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
oike1sf24b.tsp.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
tsp.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
tsp.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.