integrity.gov
Updated:
2023-08-15 21:10:06 UTC (465 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (5)
- integrity.gov/A
- integrity.gov/MX
- integrity.gov/NS
- integrity.gov/SOA
- integrity.gov/TXT
DNSKEY/DS/NSEC status
Secure (7)
- ./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)
- integrity.gov/DS (alg 10, id 11913)
- integrity.gov/DS (alg 10, id 7014)
Non_existent (2)
- integrity.gov/DNSKEY (alg 10, id 11913)
- integrity.gov/DNSKEY (alg 10, id 7014)
Delegation status
Bogus (1)
- gov to integrity.gov
Secure (1)
- . to gov
Notices
Errors (15)
- gov to integrity.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. (199.134.227.132, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- gov to integrity.gov: The DS RRset for the zone included algorithm 10 (RSASHA512), but no DS RR matched a DNSKEY with algorithm 10 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.134.227.132, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- integrity.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (199.134.208.70, 199.134.208.90)
- integrity.gov/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.134.227.132, UDP_-_EDNS0_4096_D_KN)
- integrity.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.134.208.70, 199.134.208.90, UDP_-_NOEDNS_)
- integrity.gov/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.134.227.132, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- integrity.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.134.227.132, UDP_-_EDNS0_4096_D_KN)
- integrity.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.134.208.70, 199.134.208.90, UDP_-_NOEDNS_)
- integrity.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.134.227.132, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- integrity.gov/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.134.227.132, UDP_-_EDNS0_4096_D_KN)
- integrity.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- bdnerp2uks.integrity.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- integrity.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- integrity.gov/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
- integrity.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- integrity.gov/DS (alg 10, id 7014): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- integrity.gov/DS (alg 10, id 7014): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- integrity.gov/DS (alg 10, id 7014): 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.
- integrity.gov/DS (alg 10, id 7014): 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.
