RRSIG urbanwaters.gov/DNSKEY alg 8, id 41070: The Signature Expiration field of the RRSIG RR (2021-04-05 23:46:50+00:00) is 209 days in the past. See RFC 4035, Sec. 5.3.1.
RRSIG urbanwaters.gov/DNSKEY alg 8, id 41070: The Signature Expiration field of the RRSIG RR (2021-04-05 23:46:50+00:00) is 209 days in the past. See RFC 4035, Sec. 5.3.1.
RRSIG urbanwaters.gov/DNSKEY alg 8, id 41070: The Signature Expiration field of the RRSIG RR (2021-04-05 23:46:50+00:00) is 209 days in the past. See RFC 4035, Sec. 5.3.1.
RRSIG urbanwaters.gov/DNSKEY alg 8, id 41070: The Signature Expiration field of the RRSIG RR (2021-04-05 23:46:50+00:00) is 209 days in the past. See RFC 4035, Sec. 5.3.1.
RRSIG urbanwaters.gov/DNSKEY alg 8, id 41070: The Signature Expiration field of the RRSIG RR (2021-04-05 23:46:50+00:00) is 209 days in the past. See RFC 4035, Sec. 5.3.1.
RRSIG urbanwaters.gov/DNSKEY alg 8, id 41070: The Signature Expiration field of the RRSIG RR (2021-04-05 23:46:50+00:00) is 209 days in the past. See RFC 4035, Sec. 5.3.1.
RRSIG urbanwaters.gov/DNSKEY alg 8, id 41070: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG urbanwaters.gov/DNSKEY alg 8, id 41070: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG urbanwaters.gov/DNSKEY alg 8, id 41070: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG urbanwaters.gov/DNSKEY alg 8, id 41070: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG urbanwaters.gov/DNSKEY alg 8, id 41070: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG urbanwaters.gov/DNSKEY alg 8, id 41070: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
gov to urbanwaters.gov: 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. (134.67.12.10, 2620:117:506f:c::f00a, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
gov to urbanwaters.gov: 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. (134.67.12.10, 2620:117:506f:c::f00a, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
urbanwaters.gov/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (134.67.12.10, 161.80.212.10, 2620:117:506f:c::f00a, 2620:117:5071:d4::f00a, UDP_-_EDNS0_4096_D_KN)
urbanwaters.gov/AAAA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (134.67.12.10, 161.80.212.10, 2620:117:506f:c::f00a, 2620:117:5071:d4::f00a, UDP_-_EDNS0_4096_D_KN)
urbanwaters.gov/DNSKEY (alg 8, id 21501): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (134.67.12.10, 2620:117:506f:c::f00a, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
urbanwaters.gov/DNSKEY (alg 8, id 54369): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (134.67.12.10, 161.80.212.10, 2620:117:506f:c::f00a, 2620:117:5071:d4::f00a, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
urbanwaters.gov/DNSKEY (alg 8, id 8422): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (134.67.12.10, 2620:117:506f:c::f00a, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
urbanwaters.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (134.67.12.10, 161.80.212.10, 2620:117:506f:c::f00a, 2620:117:5071:d4::f00a, UDP_-_EDNS0_4096_D_KN)
urbanwaters.gov/NSEC3PARAM (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (134.67.12.10, 2620:117:506f:c::f00a, UDP_-_EDNS0_4096_D_KN)
urbanwaters.gov/NSEC3PARAM: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (161.80.212.10, 2620:117:5071:d4::f00a, UDP_-_EDNS0_4096_D_KN)
urbanwaters.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (134.67.12.10, 2620:117:506f:c::f00a, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
urbanwaters.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (161.80.212.10, 2620:117:5071:d4::f00a, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
urbanwaters.gov/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (134.67.12.10, 161.80.212.10, 2620:117:506f:c::f00a, 2620:117:5071:d4::f00a, UDP_-_EDNS0_4096_D_KN)
urbanwaters.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
urbanwaters.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
2f67ze8vyt.urbanwaters.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
urbanwaters.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
urbanwaters.gov/DNSKEY (alg 8, id 27255): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (134.67.12.10, 161.80.212.10, 161.80.212.12, 2620:117:506f:c::f00a, 2620:117:5071:d4::f00a, 2620:117:5071:d4::f00c, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
urbanwaters.gov/DNSKEY (alg 8, id 3003): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (134.67.12.10, 161.80.212.10, 161.80.212.12, 2620:117:506f:c::f00a, 2620:117:5071:d4::f00a, 2620:117:5071:d4::f00c, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
urbanwaters.gov/DNSKEY (alg 8, id 41070): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (134.67.12.10, 161.80.212.10, 161.80.212.12, 2620:117:506f:c::f00a, 2620:117:5071:d4::f00a, 2620:117:5071:d4::f00c, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
urbanwaters.gov/DS (alg 8, id 8422): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
urbanwaters.gov/DS (alg 8, id 8422): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
urbanwaters.gov/DS (alg 8, id 8422): 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.
urbanwaters.gov/DS (alg 8, id 8422): 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.
urbanwaters.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
2f67ze8vyt.urbanwaters.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
urbanwaters.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.