dot.gov
Updated:
2020-05-10 13:26:28 UTC (1662 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (5)
- dot.gov/A
- dot.gov/MX
- dot.gov/NS
- dot.gov/SOA
- dot.gov/TXT
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 48903)
- dot.gov/DS (alg 8, id 28156)
- gov/DNSKEY (alg 8, id 40176)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Non_existent (1)
- dot.gov/DNSKEY (alg 8, id 28156)
Delegation status
Bogus (1)
- gov to dot.gov
Secure (1)
- . to gov
Notices
Errors (11)
- dot.gov/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (204.68.194.100, 204.68.194.200, 204.152.44.100, 2001:19e8:d::100, 2001:19e8:d::200, 2001:19e8:d4::100, UDP_-_EDNS0_4096_D_K)
- dot.gov/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (204.68.194.100, 204.68.194.200, 204.152.44.100, 2001:19e8:d::100, 2001:19e8:d::200, 2001:19e8:d4::100, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- dot.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (204.68.194.100, 204.68.194.200, 204.152.44.100, 2001:19e8:d::100, 2001:19e8:d::200, 2001:19e8:d4::100, UDP_-_EDNS0_4096_D_K)
- dot.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (204.68.194.100, 204.68.194.200, 204.152.44.100, 2001:19e8:d::100, 2001:19e8:d::200, 2001:19e8:d4::100, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
- dot.gov/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (204.68.194.100, 204.68.194.200, 204.152.44.100, 2001:19e8:d::100, 2001:19e8:d::200, 2001:19e8:d4::100, UDP_-_EDNS0_4096_D_K)
- gov to dot.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. (204.68.194.100, 204.68.194.200, 204.152.44.100, 2001:19e8:d::100, 2001:19e8:d::200, 2001:19e8:d4::100, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- gov to dot.gov: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (204.68.194.100, 204.68.194.200, 204.152.44.100, 2001:19e8:d::100, 2001:19e8:d::200, 2001:19e8:d4::100, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- dot.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- c12dtxlq0o.dot.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- dot.gov/AAAA 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 (11)
- dot.gov/DS (alg 8, id 28156): 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 28156): 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 28156): 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 28156): 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 to dot.gov: Authoritative AAAA records exist for edns1.dot.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- gov to dot.gov: Authoritative AAAA records exist for edns2.dot.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- gov to dot.gov: Authoritative AAAA records exist for edns3.dot.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.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): 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.
