af.mil
Updated:
2024-11-06 12:28:02 UTC (50 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- af.mil/NS
- af.mil/NSEC3PARAM
- af.mil/SOA
- af.mil/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- af.mil/DNSKEY (alg 8, id 15258)
- af.mil/DNSKEY (alg 8, id 15529)
- af.mil/DNSKEY (alg 8, id 495)
- af.mil/DS (alg 8, id 15529)
- af.mil/DS (alg 8, id 15529)
- mil/DNSKEY (alg 8, id 20335)
- mil/DNSKEY (alg 8, id 26770)
- mil/DNSKEY (alg 8, id 63500)
- mil/DS (alg 8, id 63500)
Delegation status
Secure (2)
- . to mil
- mil to af.mil
Notices
Errors (7)
- af.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- af.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- af.mil/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- af.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- 2qmtk.tgrfm.af.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- af.mil/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
- af.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (14)
- af.mil/DS (alg 8, id 15529): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- af.mil/DS (alg 8, id 15529): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- af.mil/DS (alg 8, id 15529): 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.
- af.mil/DS (alg 8, id 15529): 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/DNSKEY (alg 8, id 20335): No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (199.252.143.234, UDP_-_EDNS0_4096_D_KN)
- mil/DNSKEY (alg 8, id 26770): No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (199.252.143.234, UDP_-_EDNS0_4096_D_KN)
- mil/DNSKEY (alg 8, id 63500): No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (199.252.143.234, UDP_-_EDNS0_4096_D_KN)
- af.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- af.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- af.mil/CDNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- af.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- 2qmtk.tgrfm.af.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- af.mil/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
- af.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
