nuclear.gov
Updated:
2023-08-01 13:52:55 UTC (477 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- nuclear.gov/A
- nuclear.gov/AAAA
- nuclear.gov/NS
- nuclear.gov/NSEC3PARAM
- nuclear.gov/SOA
- nuclear.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 11019)
- ./DNSKEY (alg 8, id 20326)
- gov/DNSKEY (alg 8, id 40921)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- nuclear.gov/DNSKEY (alg 8, id 12262)
- nuclear.gov/DNSKEY (alg 8, id 38448)
- nuclear.gov/DNSKEY (alg 8, id 40134)
- nuclear.gov/DS (alg 8, id 12262)
- nuclear.gov/DS (alg 8, id 12262)
Delegation status
Secure (2)
- . to gov
- gov to nuclear.gov
Notices
Errors (10)
- nuclear.gov/DNSKEY: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (205.254.143.110, TCP_-_EDNS0_4096_D_KN)
- nuclear.gov/DNSKEY: No response was received from the server over TCP (tried 8 times). See RFC 1035, Sec. 4.2. (2607:f368:1000:1000::53, TCP_-_EDNS0_4096_D)
- nuclear.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2607:f368:1000:1000::53, 2607:f368:1000:1100::53, UDP_-_EDNS0_512_D_KN)
- nuclear.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (2607:f368:1000:1000::53, 2607:f368:1000:1100::53, TCP_-_EDNS0_4096_D_N)
- nuclear.gov/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (205.254.143.110, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
- nuclear.gov/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (205.254.143.110, UDP_-_NOEDNS_)
- nuclear.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- uv07c1gy2s.nuclear.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- nuclear.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- nuclear.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (15)
- gov to nuclear.gov: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gov zone): adns2.es.net See RFC 1034, Sec. 4.2.2.
- nuclear.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.254.144.110, 2607:f368:1000:1000::53, UDP_-_EDNS0_4096_D_KN)
- nuclear.gov/AAAA: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (2607:f368:1000:1000::53, UDP_-_EDNS0_4096_D_KN)
- nuclear.gov/AAAA: 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.254.143.110, UDP_-_EDNS0_4096_D_KN)
- nuclear.gov/DS (alg 8, id 12262): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- nuclear.gov/DS (alg 8, id 12262): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- nuclear.gov/DS (alg 8, id 12262): 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.
- nuclear.gov/DS (alg 8, id 12262): 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.
- nuclear.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.254.144.110, UDP_-_EDNS0_4096_D_KN)
- nuclear.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. (2607:f368:1000:1100::53, UDP_-_EDNS0_4096_D_KN_0x20)
- nuclear.gov/TXT: 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.254.144.110, UDP_-_EDNS0_4096_D_KN)
- nuclear.gov/TXT: 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. (2607:f368:1000:1000::53, UDP_-_EDNS0_4096_D_KN)
- nuclear.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- uv07c1gy2s.nuclear.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- nuclear.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
