ic3.gov
Updated:
2023-05-23 12:05:12 UTC (551 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (7)
- ic3.gov/A
- ic3.gov/AAAA
- ic3.gov/MX
- ic3.gov/NS
- ic3.gov/NSEC3PARAM
- ic3.gov/SOA
- ic3.gov/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- gov/DNSKEY (alg 8, id 50011)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- ic3.gov/DNSKEY (alg 8, id 28698)
- ic3.gov/DNSKEY (alg 8, id 38374)
- ic3.gov/DNSKEY (alg 8, id 49462)
- ic3.gov/DNSKEY (alg 8, id 58732)
- ic3.gov/DS (alg 8, id 49462)
- ic3.gov/DS (alg 8, id 49462)
Delegation status
Secure (2)
- . to gov
- gov to ic3.gov
Notices
Errors (3)
- ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (199.9.14.201, UDP_-_EDNS0_512_D_KN)
- f7n2sd6y19.ic3.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- ic3.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (19)
- ./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. (192.228.79.201, 199.9.14.201, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 60955): 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.228.79.201, 199.9.14.201, UDP_-_EDNS0_4096_D_KN)
- gov/DS (alg 8, id 7698): 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. (192.228.79.201, UDP_-_EDNS0_4096_D_KN)
- gov/DS (alg 8, id 7698): 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. (192.228.79.201, UDP_-_EDNS0_4096_D_KN)
- 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. (199.9.14.201, UDP_-_EDNS0_4096_D_KN)
- 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. (199.9.14.201, UDP_-_EDNS0_4096_D_KN)
- ic3.gov/DNSKEY (alg 8, id 28698): 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:489a:3102:6::62, 2001:489a:3600::13, UDP_-_EDNS0_4096_D_KN)
- ic3.gov/DNSKEY (alg 8, id 38374): 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:489a:3102:6::62, 2001:489a:3600::13, UDP_-_EDNS0_4096_D_KN)
- ic3.gov/DNSKEY (alg 8, id 49462): 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:489a:3102:6::62, 2001:489a:3600::13, UDP_-_EDNS0_4096_D_KN)
- ic3.gov/DNSKEY (alg 8, id 58732): 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:489a:3102:6::62, 2001:489a:3600::13, UDP_-_EDNS0_4096_D_KN)
- ic3.gov/DS (alg 8, id 49462): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ic3.gov/DS (alg 8, id 49462): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ic3.gov/DS (alg 8, id 49462): 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.
- ic3.gov/DS (alg 8, id 49462): 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.
- ic3.gov/MX: 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:489a:3102:6::62, 2001:489a:3600::13, UDP_-_EDNS0_4096_D_KN)
- ic3.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. (2001:489a:3102:6::62, 2001:489a:3600::13, UDP_-_EDNS0_4096_D_KN)
- ic3.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- f7n2sd6y19.ic3.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- ic3.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
