apps.mil
Updated:
2021-02-08 15:23:15 UTC (1415 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (3)
- apps.mil/NS
- apps.mil/SOA
- apps.mil/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 42351)
- apps.mil/DNSKEY (alg 8, id 19869)
- apps.mil/DNSKEY (alg 8, id 64321)
- apps.mil/DNSKEY (alg 8, id 6796)
- apps.mil/DS (alg 8, id 64321)
- apps.mil/DS (alg 8, id 64321)
- mil/DNSKEY (alg 8, id 19128)
- mil/DNSKEY (alg 8, id 24363)
- mil/DNSKEY (alg 8, id 51349)
- mil/DS (alg 8, id 51349)
- mil/DS (alg 8, id 51349)
Delegation status
Secure (2)
- . to mil
- mil to apps.mil
Notices
Errors (8)
- apps.mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (152.229.110.235)
- apps.mil/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (152.229.110.235, UDP_-_NOEDNS_)
- mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (199.252.154.234, UDP_-_EDNS0_512_D_KN)
- 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.
- 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.
- u3vmarl052.apps.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (14)
- apps.mil/DS (alg 8, id 64321): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- apps.mil/DS (alg 8, id 64321): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- apps.mil/DS (alg 8, id 64321): 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.
- apps.mil/DS (alg 8, id 64321): 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.
- apps.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. (131.77.60.235, UDP_-_EDNS0_4096_D_KN)
- mil/DS (alg 8, id 51349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- mil/DS (alg 8, id 51349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- mil/DS (alg 8, id 51349): 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.
- mil/DS (alg 8, id 51349): 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.
- 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.
- 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.
- u3vmarl052.apps.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
