usdoj.gov
Updated:
2022-12-15 06:46:11 UTC (709 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (7)
- usdoj.gov/A
- usdoj.gov/AAAA
- usdoj.gov/MX
- usdoj.gov/NS
- usdoj.gov/NSEC3PARAM
- usdoj.gov/SOA
- usdoj.gov/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- gov/DNSKEY (alg 8, id 56278)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- usdoj.gov/DNSKEY (alg 8, id 16215)
- usdoj.gov/DNSKEY (alg 8, id 58159)
- usdoj.gov/DNSKEY (alg 8, id 61969)
- usdoj.gov/DS (alg 8, id 58159)
- usdoj.gov/DS (alg 8, id 58159)
- usdoj.gov/DS (alg 8, id 61969)
- usdoj.gov/DS (alg 8, id 61969)
Delegation status
Secure (2)
- . to gov
- gov to usdoj.gov
Notices
Errors (11)
- usdoj.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (149.101.180.157)
- usdoj.gov/A: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 11 times) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (149.101.180.157, UDP_-_NOEDNS_)
- usdoj.gov/A: No response was received from the server over UDP (tried 11 times) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (149.101.180.157, UDP_-_EDNS0_4096_D_KN)
- usdoj.gov/A: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (149.101.180.157, UDP_-_EDNS0_4096_D_KN)
- usdoj.gov/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.180.157, UDP_-_NOEDNS_)
- usdoj.gov/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (149.101.180.157, UDP_-_EDNS0_512_D_KN)
- usdoj.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.180.157, UDP_-_NOEDNS_)
- usdoj.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (149.101.180.157, TCP_-_EDNS0_4096_D_N)
- usdoj.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- usdoj.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- i98p3u5ab2.usdoj.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
- usdoj.gov/DS (alg 8, id 58159): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- usdoj.gov/DS (alg 8, id 58159): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- usdoj.gov/DS (alg 8, id 58159): 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.
- usdoj.gov/DS (alg 8, id 58159): 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.
- usdoj.gov/DS (alg 8, id 61969): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- usdoj.gov/DS (alg 8, id 61969): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- usdoj.gov/DS (alg 8, id 61969): 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.
- usdoj.gov/DS (alg 8, id 61969): 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.
- i98p3u5ab2.usdoj.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- usdoj.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
