navy.mil
Updated:
2024-09-04 19:00:23 UTC (134 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- navy.mil/MX
- navy.mil/NS
- navy.mil/NSEC3PARAM
- navy.mil/SOA
- navy.mil/TXT
Secure (1)
- mil/SOA
DNSKEY/DS/NSEC status
Insecure (3)
- navy.mil/DNSKEY (alg 8, id 10320)
- navy.mil/DNSKEY (alg 8, id 11910)
- navy.mil/DNSKEY (alg 8, id 52315)
Secure (7)
- ./DNSKEY (alg 8, id 20038)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of navy.mil/DS
- mil/DNSKEY (alg 8, id 16801)
- mil/DNSKEY (alg 8, id 21018)
- mil/DNSKEY (alg 8, id 51405)
- mil/DS (alg 8, id 16801)
Delegation status
Insecure (1)
- mil to navy.mil
Secure (1)
- . to mil
Notices
Errors (18)
- NSEC3 proving non-existence of navy.mil/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of navy.mil/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- navy.mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (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/DNSKEY (alg 8, id 11910): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (131.77.60.232, 152.229.110.232, 214.23.245.6, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- navy.mil/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2608:c144:1:155::234, UDP_-_NOEDNS_)
- navy.mil/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (131.77.60.232, 152.229.110.232, 214.3.125.232, 214.23.245.6, 215.65.126.185, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- navy.mil/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (131.77.60.232, 152.229.110.232, 214.3.125.232, 214.23.245.6, 215.65.126.185, UDP_-_EDNS0_4096_D_KN)
- navy.mil/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (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:c144:1:155::234, 2608:c182::1001:9012:1600:20, 2608:c182:0:1012:1001:9012:1400:20, UDP_-_NOEDNS_)
- navy.mil/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (131.77.60.232, 152.229.110.232, 214.3.125.232, 214.23.245.6, 215.65.126.185, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- navy.mil/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (131.77.60.232, 152.229.110.232, 214.3.125.232, 214.23.245.6, 215.65.126.185, UDP_-_EDNS0_4096_D_KN)
- navy.mil/AAAA 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/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
- navy.mil/DNSKEY 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.
- b8xis.w8roa.navy.mil/A 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.
- navy.mil/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (16)
- NSEC3 proving non-existence of navy.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of navy.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- 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.
- navy.mil/DNSKEY (alg 8, id 10320): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (131.77.60.232, 152.229.110.232, 214.23.245.6, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- navy.mil/DNSKEY (alg 8, id 52315): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (131.77.60.232, 152.229.110.232, 214.23.245.6, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- navy.mil/AAAA 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/CDNSKEY 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.
- b8xis.w8roa.navy.mil/A 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.
- navy.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
