apps.mil
Updated:
2023-10-02 12:20:08 UTC (446 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (4)
- apps.mil/NS
- apps.mil/NSEC3PARAM
- apps.mil/SOA
- apps.mil/TXT
Secure (2)
- mil/SOA
- mil/SOA
DNSKEY/DS/NSEC status
Insecure (3)
- apps.mil/DNSKEY (alg 8, id 32206)
- apps.mil/DNSKEY (alg 8, id 33978)
- apps.mil/DNSKEY (alg 8, id 36970)
Secure (10)
- ./DNSKEY (alg 8, id 11019)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46780)
- NSEC3 proving non-existence of apps.mil/DS
- NSEC3 proving non-existence of apps.mil/DS
- mil/DNSKEY (alg 8, id 14098)
- mil/DNSKEY (alg 8, id 16801)
- mil/DNSKEY (alg 8, id 44065)
- mil/DNSKEY (alg 8, id 62470)
- mil/DS (alg 8, id 16801)
Delegation status
Insecure (1)
- mil to apps.mil
Secure (1)
- . to mil
Notices
Errors (12)
- NSEC3 proving non-existence of apps.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 apps.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 apps.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 apps.mil/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- apps.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:21, 2608:125:0:1811:1001:9012:f00:21, 2608:145:0:180b:1001:9012:d00:21)
- apps.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:21, 2608:125:0:1811:1001:9012:f00:21, 2608:145:0:180b:1001:9012:d00:21, UDP_-_NOEDNS_)
- apps.mil/DS has errors; select the "Denial of existence" DNSSEC option to see them.
- apps.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- apps.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- yp5xz49bwh.apps.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- apps.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- apps.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (14)
- NSEC3 proving non-existence of apps.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of apps.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of apps.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of apps.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- mil to apps.mil: AAAA glue records exist for ns.cybercom.mil, but there are no corresponding authoritative AAAA records. See RFC 1034, Sec. 4.2.2.
- mil to apps.mil: AAAA glue records exist for ns.jtfgno.mil, but there are no corresponding authoritative AAAA records. See RFC 1034, Sec. 4.2.2.
- mil to apps.mil: AAAA glue records exist for ns1.csd.disa.mil, but there are no corresponding authoritative AAAA records. See RFC 1034, Sec. 4.2.2.
- mil to apps.mil: 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. (2608:4163:1:143::234, UDP_-_EDNS0_4096_D_KN)
- apps.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
- apps.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- apps.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- yp5xz49bwh.apps.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- apps.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- apps.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
