af.mil
Updated:
2024-03-27 08:35:09 UTC (289 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- af.mil/NS
- af.mil/NSEC3PARAM
- af.mil/SOA
- af.mil/SOA
- af.mil/SOA
- af.mil/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 30903)
- ./DNSKEY (alg 8, id 5613)
- af.mil/DNSKEY (alg 8, id 15258)
- af.mil/DNSKEY (alg 8, id 2725)
- af.mil/DNSKEY (alg 8, id 495)
- af.mil/DS (alg 8, id 2725)
- af.mil/DS (alg 8, id 2725)
- mil/DNSKEY (alg 8, id 16801)
- mil/DNSKEY (alg 8, id 25501)
- mil/DNSKEY (alg 8, id 29059)
- mil/DS (alg 8, id 16801)
Delegation status
Secure (2)
- . to mil
- mil to af.mil
Notices
Errors (13)
- RRSIG af.mil/DNSKEY alg 8, id 2725: With a TTL of 147304 the RRSIG RR can be in the cache of a non-validating resolver until 8 hours, 43 minutes after it expires at 2024-03-28 16:46:47+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG af.mil/DNSKEY alg 8, id 2725: With a TTL of 147304 the RRSIG RR can be in the cache of a non-validating resolver until 8 hours, 43 minutes after it expires at 2024-03-28 16:46:47+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG af.mil/DNSKEY alg 8, id 2725: With a TTL of 147304 the RRSIG RR can be in the cache of a non-validating resolver until 8 hours, 43 minutes after it expires at 2024-03-28 16:46:47+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG af.mil/DNSKEY alg 8, id 495: With a TTL of 147304 the RRSIG RR can be in the cache of a non-validating resolver until 8 hours, 43 minutes after it expires at 2024-03-28 16:46:47+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG af.mil/DNSKEY alg 8, id 495: With a TTL of 147304 the RRSIG RR can be in the cache of a non-validating resolver until 8 hours, 43 minutes after it expires at 2024-03-28 16:46:47+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG af.mil/DNSKEY alg 8, id 495: With a TTL of 147304 the RRSIG RR can be in the cache of a non-validating resolver until 8 hours, 43 minutes after it expires at 2024-03-28 16:46:47+00:00. See RFC 4035, Sec. 5.3.3.
- mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2608:4163:1:143::234)
- 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/A has errors; select the "Denial of existence" DNSSEC option to see them.
- 79l8jhg2z6.af.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- af.mil/DNSKEY 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 (9)
- af.mil/DS (alg 8, id 2725): 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 2725): 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 2725): 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 2725): 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.
- 79l8jhg2z6.af.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- af.mil/CNAME 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.
- af.mil/AAAA 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.
