urbanwaters.gov
Updated:
2021-11-01 15:53:38 UTC (1116 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (12)
- urbanwaters.gov/A
- urbanwaters.gov/AAAA
- urbanwaters.gov/NS
- urbanwaters.gov/NSEC3PARAM
- urbanwaters.gov/NSEC3PARAM
- urbanwaters.gov/NSEC3PARAM
- urbanwaters.gov/NSEC3PARAM
- urbanwaters.gov/SOA
- urbanwaters.gov/SOA
- urbanwaters.gov/SOA
- urbanwaters.gov/SOA
- urbanwaters.gov/TXT
DNSKEY/DS/NSEC status
Secure (13)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- gov/DNSKEY (alg 8, id 6229)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- urbanwaters.gov/DNSKEY (alg 8, id 21501)
- urbanwaters.gov/DNSKEY (alg 8, id 27255)
- urbanwaters.gov/DNSKEY (alg 8, id 3003)
- urbanwaters.gov/DNSKEY (alg 8, id 41070)
- urbanwaters.gov/DNSKEY (alg 8, id 54369)
- urbanwaters.gov/DNSKEY (alg 8, id 8422)
- urbanwaters.gov/DS (alg 8, id 8422)
- urbanwaters.gov/DS (alg 8, id 8422)
Delegation status
Secure (2)
- . to gov
- gov to urbanwaters.gov
Notices
Errors (20)
- 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.
- urbanwaters.gov/A: 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/AAAA: 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/NS: 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/TXT: 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/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.
- urbanwaters.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- qyw16lj70g.urbanwaters.gov/A 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)
- 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)
- 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)
- 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.
- urbanwaters.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- qyw16lj70g.urbanwaters.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
