ots.gov
Updated:
2021-01-13 12:23:07 UTC (1408 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- ots.gov/A
- ots.gov/NS
- ots.gov/SOA
- ots.gov/SOA
- ots.gov/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 42351)
- gov/DNSKEY (alg 8, id 15489)
- gov/DNSKEY (alg 8, id 27306)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- ots.gov/DNSKEY (alg 8, id 39138)
- ots.gov/DNSKEY (alg 8, id 55627)
- ots.gov/DS (alg 8, id 55627)
- ots.gov/DS (alg 8, id 55627)
Delegation status
Secure (2)
- . to gov
- gov to ots.gov
Notices
Errors (4)
- ots.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- ots.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- bhx8updng1.ots.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- ots.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (16)
- 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.
- 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. (2001:7fe::53, 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. (2001:7fe::53, 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. (2001:7fe::53, 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. (2001:7fe::53, UDP_-_EDNS0_4096_D_KN)
- ots.gov/DS (alg 8, id 55627): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ots.gov/DS (alg 8, id 55627): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ots.gov/DS (alg 8, id 55627): 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.
- ots.gov/DS (alg 8, id 55627): 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.
- ots.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- ots.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- bhx8updng1.ots.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- ots.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
