NSEC3 proving non-existence of cloud.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of cloud.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
cloud.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (205.251.192.137)
cloud.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (205.251.192.137, 205.251.194.219, UDP_-_EDNS0_512_D_K)
cloud.gov/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (205.251.194.219, UDP_-_EDNS0_512_D_K)
cloud.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (205.251.192.137, TCP_-_EDNS0_4096_D)
cloud.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
cloud.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (21)
NSEC3 proving non-existence of cloud.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of cloud.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
cloud.gov/A: 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. (205.251.192.137, UDP_-_EDNS0_4096_D_K)
cloud.gov/A: 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. (205.251.194.219, UDP_-_EDNS0_4096_D_K)
cloud.gov/AAAA: No response was received from the server over UDP (tried 11 times) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (205.251.194.219, UDP_-_EDNS0_4096_D_K)
cloud.gov/AAAA: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (205.251.192.137, UDP_-_EDNS0_4096_D_K)
cloud.gov/NS: 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. (205.251.194.219, UDP_-_EDNS0_4096_D_K)
cloud.gov/SOA: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (205.251.192.137, UDP_-_EDNS0_4096_D_K)
cloud.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. (205.251.192.137, 205.251.194.219, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
cloud.gov/TXT: No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). See RFC 6891, Sec. 6.1.4. (205.251.194.219, UDP_-_EDNS0_4096_D_K)
gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
gov/DS (alg 8, id 7698): 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.
gov/DS (alg 8, id 7698): 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.
gov/DS (alg 8, id 7698): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_K)
gov/DS (alg 8, id 7698): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_K)
gov/DS (alg 8, id 7698): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_K)
gov/DS (alg 8, id 7698): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_K)
hcqa845dsx.cloud.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
cloud.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
cloud.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.