wildfire.gov
Updated:
2020-05-27 19:43:57 UTC (1642 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 48903)
- gov/DNSKEY (alg 8, id 40176)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- wildfire.gov/DS (alg 8, id 51244)
- wildfire.gov/DS (alg 8, id 60739)
Non_existent (2)
- wildfire.gov/DNSKEY (alg 8, id 51244)
- wildfire.gov/DNSKEY (alg 8, id 60739)
Delegation status
Bogus (1)
- gov to wildfire.gov
Secure (1)
- . to gov
Notices
Errors (15)
- ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2001:500:12::d0d, UDP_-_EDNS0_512_D_K)
- gov to wildfire.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.
- wildfire.gov zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (165.221.108.59, 199.141.137.15, 199.141.140.11)
- wildfire.gov zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (165.221.108.59, 199.141.137.15, 199.141.140.11)
- wildfire.gov/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (165.221.108.59, 199.141.137.15, 199.141.140.11, UDP_-_EDNS0_4096_D_K)
- wildfire.gov/AAAA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (165.221.108.59, 199.141.137.15, 199.141.140.11, UDP_-_EDNS0_4096_D_K)
- wildfire.gov/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (165.221.108.59, 199.141.137.15, 199.141.140.11, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- wildfire.gov/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (165.221.108.59, 199.141.137.15, 199.141.140.11, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- wildfire.gov/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (165.221.108.59, 199.141.137.15, 199.141.140.11, UDP_-_EDNS0_4096_D_K)
- wildfire.gov/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (165.221.108.59, 199.141.137.15, 199.141.140.11, TCP_-_EDNS0_4096_D)
- wildfire.gov/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (165.221.108.59, 199.141.137.15, 199.141.140.11, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
- wildfire.gov/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (165.221.108.59, 199.141.137.15, 199.141.140.11, UDP_-_EDNS0_4096_D_K)
- wildfire.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- wildfire.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- yx5fc9o41n.wildfire.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
- ./DNSKEY (alg 8, id 20326): 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. (2001:500:12::d0d, UDP_-_EDNS0_4096_D_K)
- ./DNSKEY (alg 8, id 48903): 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. (2001:500:12::d0d, 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.
JavaScript is required to make the graph below interactive.
