navy.mil
Updated:
2024-09-05 21:18:14 UTC (67 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- navy.mil/MX
- navy.mil/NS
- navy.mil/NSEC3PARAM
- navy.mil/SOA
- navy.mil/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20038)
- ./DNSKEY (alg 8, id 20326)
- mil/DNSKEY (alg 8, id 16801)
- mil/DNSKEY (alg 8, id 21018)
- mil/DNSKEY (alg 8, id 51405)
- mil/DS (alg 8, id 16801)
- navy.mil/DNSKEY (alg 8, id 10320)
- navy.mil/DNSKEY (alg 8, id 11910)
- navy.mil/DNSKEY (alg 8, id 52315)
- navy.mil/DS (alg 8, id 52315)
- navy.mil/DS (alg 8, id 52315)
Delegation status
Secure (2)
- . to mil
- mil to navy.mil
Notices
Errors (10)
- mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2608:4163:1:143::234)
- navy.mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (1.2.3.4, 2608:102:0:182d:1001:9012:c00:20, 2608:125:0:1811:1001:9012:f00:20, 2608:145:0:180b:1001:9012:d00:20, 2608:4122:0:1012:1001:9012:1400:20, 2608:c182::1001:9012:1600:20, 2608:c182:0:1012:1001:9012:1400:20)
- navy.mil/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (1.2.3.4, 2608:102:0:182d:1001:9012:c00:20, 2608:125:0:1811:1001:9012:f00:20, 2608:145:0:180b:1001:9012:d00:20, 2608:4122:0:1012:1001:9012:1400:20, 2608:c182::1001:9012:1600:20, 2608:c182:0:1012:1001:9012:1400:20, UDP_-_NOEDNS_)
- navy.mil/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (214.3.125.232, 215.65.126.185, UDP_-_NOEDNS_)
- navy.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- navy.mil/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
- navy.mil/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- navy.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- navy.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- vlk50.gfipl.navy.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (18)
- mil to navy.mil: Authoritative AAAA records exist for dns1.disa.mil, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- mil to navy.mil: Authoritative AAAA records exist for dns2.disa.mil, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- mil to navy.mil: Authoritative AAAA records exist for dns3.disa.mil, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- mil to navy.mil: Authoritative AAAA records exist for dns4.disa.mil, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- mil to navy.mil: Authoritative AAAA records exist for dns5.disa.mil, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- mil to navy.mil: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the mil zone): biden.navy.mil See RFC 1034, Sec. 4.2.2.
- navy.mil/DS (alg 8, id 52315): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- navy.mil/DS (alg 8, id 52315): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- navy.mil/DS (alg 8, id 52315): 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.
- navy.mil/DS (alg 8, id 52315): 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.
- navy.mil/NSEC3PARAM: 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. (131.77.60.232, 214.23.245.6, UDP_-_EDNS0_4096_D_KN)
- navy.mil/TXT: 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. (214.23.245.6, UDP_-_EDNS0_4096_D_KN)
- navy.mil/CDNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- navy.mil/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
- navy.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- navy.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- navy.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- vlk50.gfipl.navy.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
