usfj.mil
Updated:
2023-01-15 12:24:19 UTC (706 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- usfj.mil/NS
- usfj.mil/NSEC3PARAM
- usfj.mil/SOA
- usfj.mil/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 951)
- mil/DNSKEY (alg 8, id 55084)
- mil/DNSKEY (alg 8, id 57763)
- mil/DNSKEY (alg 8, id 62470)
- mil/DS (alg 8, id 62470)
- usfj.mil/DNSKEY (alg 8, id 10545)
- usfj.mil/DNSKEY (alg 8, id 23571)
- usfj.mil/DNSKEY (alg 8, id 58520)
- usfj.mil/DNSKEY (alg 8, id 61411)
- usfj.mil/DS (alg 8, id 58520)
- usfj.mil/DS (alg 8, id 58520)
Delegation status
Secure (2)
- . to mil
- mil to usfj.mil
Notices
Errors (15)
- mil zone: The server(s) did not respond authoritatively for the namespace. See RFC 1035, Sec. 4.1.1. (199.252.157.234, 199.252.162.234, 199.252.180.234)
- mil/DNSKEY (alg 8, id 55084): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
- mil/DNSKEY (alg 8, id 57763): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
- mil/DNSKEY (alg 8, id 62470): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
- usfj.mil/DS (alg 8, id 58520): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
- usfj.mil/DS (alg 8, id 58520): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
- usfj.mil/DS (alg 8, id 58520): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
- usfj.mil/DS (alg 8, id 58520): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
- usfj.mil/NS: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
- usfj.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- usfj.mil/DS has errors; select the "Denial of existence" DNSSEC option to see them.
- usfj.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- usfj.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- usfj.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- bos8kdl1gv.usfj.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
- mil to usfj.mil: The following NS name(s) were found in the delegation NS RRset (i.e., in the mil zone), but not in the authoritative NS RRset: pnocxns1.pr.navy.mil, pnocxns2.pr.navy.mil See RFC 1034, Sec. 4.2.2.
- mil/DNSKEY: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_512_D_KN)
- usfj.mil/DS (alg 8, id 58520): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- usfj.mil/DS (alg 8, id 58520): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- usfj.mil/DS (alg 8, id 58520): 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.
- usfj.mil/DS (alg 8, id 58520): 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.
- usfj.mil/SOA: 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. (199.211.150.67, UDP_-_EDNS0_4096_D_KN)
- usfj.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- usfj.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- usfj.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- usfj.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- bos8kdl1gv.usfj.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
