doj.gov
Updated:
2022-10-13 14:34:34 UTC (809 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- doj.gov/MX
- doj.gov/NS
- doj.gov/NSEC3PARAM
- doj.gov/SOA
- doj.gov/TXT
DNSKEY/DS/NSEC status
Secure (14)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- doj.gov/DNSKEY (alg 8, id 20511)
- doj.gov/DNSKEY (alg 8, id 39165)
- doj.gov/DNSKEY (alg 8, id 55012)
- doj.gov/DNSKEY (alg 8, id 9379)
- doj.gov/DS (alg 8, id 55012)
- doj.gov/DS (alg 8, id 55012)
- doj.gov/DS (alg 8, id 9379)
- doj.gov/DS (alg 8, id 9379)
- gov/DNSKEY (alg 8, id 261)
- gov/DNSKEY (alg 8, id 56278)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Secure (2)
- . to gov
- gov to doj.gov
Notices
Errors (10)
- doj.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (149.101.180.157)
- doj.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_)
- doj.gov/DNSKEY: 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)
- doj.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)
- doj.gov/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.180.157, UDP_-_NOEDNS__0x20)
- doj.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- mw9u8i7aln.doj.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- doj.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- doj.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- doj.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
- doj.gov/DS (alg 8, id 55012): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- doj.gov/DS (alg 8, id 55012): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- doj.gov/DS (alg 8, id 55012): 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.
- doj.gov/DS (alg 8, id 55012): 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.
- doj.gov/DS (alg 8, id 9379): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- doj.gov/DS (alg 8, id 9379): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- doj.gov/DS (alg 8, id 9379): 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.
- doj.gov/DS (alg 8, id 9379): 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.
- doj.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- mw9u8i7aln.doj.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- doj.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- doj.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
