dot.gov
Updated:
2022-04-11 18:54:51 UTC (957 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- dot.gov/A
- dot.gov/MX
- dot.gov/NS
- dot.gov/NSEC3PARAM
- dot.gov/SOA
- dot.gov/TXT
DNSKEY/DS/NSEC status
Secure (14)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 47671)
- dot.gov/DNSKEY (alg 8, id 40413)
- dot.gov/DNSKEY (alg 8, id 49516)
- dot.gov/DNSKEY (alg 8, id 56035)
- dot.gov/DNSKEY (alg 8, id 9528)
- dot.gov/DS (alg 8, id 49516)
- dot.gov/DS (alg 8, id 49516)
- dot.gov/DS (alg 8, id 56035)
- dot.gov/DS (alg 8, id 56035)
- gov/DNSKEY (alg 8, id 2706)
- gov/DNSKEY (alg 8, id 7030)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Secure (2)
- . to gov
- gov to dot.gov
Notices
Errors (4)
- gov/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:7fe::53, UDP_-_NOEDNS_)
- dot.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- t457iub2rv.dot.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- dot.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (16)
- dot.gov/DNSKEY (alg 8, id 40413): 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:19e8:d::100, 2001:19e8:d::200, UDP_-_EDNS0_4096_D_KN)
- dot.gov/DNSKEY (alg 8, id 49516): 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:19e8:d::100, 2001:19e8:d::200, UDP_-_EDNS0_4096_D_KN)
- dot.gov/DNSKEY (alg 8, id 56035): 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:19e8:d::100, 2001:19e8:d::200, UDP_-_EDNS0_4096_D_KN)
- dot.gov/DNSKEY (alg 8, id 9528): 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:19e8:d::100, 2001:19e8:d::200, UDP_-_EDNS0_4096_D_KN)
- dot.gov/DS (alg 8, id 49516): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- dot.gov/DS (alg 8, id 49516): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- dot.gov/DS (alg 8, id 49516): 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.
- dot.gov/DS (alg 8, id 49516): 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.
- dot.gov/DS (alg 8, id 56035): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- dot.gov/DS (alg 8, id 56035): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- dot.gov/DS (alg 8, id 56035): 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.
- dot.gov/DS (alg 8, id 56035): 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.
- dot.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- dot.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- t457iub2rv.dot.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- dot.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
