af.mil
Updated:
2023-01-11 19:32:23 UTC (730 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (8)
- af.mil/NS
- af.mil/NSEC3PARAM
- af.mil/SOA
- af.mil/SOA
- af.mil/SOA
- af.mil/SOA
- af.mil/SOA
- af.mil/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 951)
- af.mil/DNSKEY (alg 8, id 15258)
- af.mil/DNSKEY (alg 8, id 495)
- af.mil/DNSKEY (alg 8, id 62926)
- af.mil/DS (alg 8, id 62926)
- af.mil/DS (alg 8, id 62926)
- mil/DNSKEY (alg 8, id 19660)
- mil/DNSKEY (alg 8, id 57763)
- mil/DNSKEY (alg 8, id 62470)
- mil/DS (alg 8, id 62470)
Delegation status
Secure (2)
- . to mil
- mil to af.mil
Notices
Errors (16)
- RRSIG af.mil/SOA alg 8, id 495: The TTL of the RRSIG (84062) exceeds the value of its Original TTL field (3600). See RFC 4035, Sec. 2.2.
- RRSIG af.mil/SOA alg 8, id 495: The TTL of the RRSIG (84108) exceeds the value of its Original TTL field (3600). See RFC 4035, Sec. 2.2.
- RRSIG af.mil/TXT alg 8, id 495: The TTL of the RRSIG (80720) exceeds the value of its Original TTL field (300). See RFC 4035, Sec. 2.2.
- af.mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (132.3.9.10, 132.3.13.10)
- af.mil/DNSKEY: No response was received from the server over TCP (tried 2 times). See RFC 1035, Sec. 4.2. (132.3.48.140, TCP_-_EDNS0_4096_D_KN)
- af.mil/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (132.3.48.132, UDP_-_NOEDNS_)
- af.mil/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (132.3.9.10, 132.3.13.10, UDP_-_NOEDNS_)
- af.mil/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (132.3.48.132, UDP_-_NOEDNS_)
- af.mil/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (132.3.48.132, 132.3.48.140, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
- af.mil/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (132.3.48.132, 132.3.48.140, UDP_-_NOEDNS_)
- 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.
- b1r9m5iceg.af.mil/A 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.
- 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 (10)
- af.mil/DS (alg 8, id 62926): 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 62926): 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 62926): 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 62926): 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/NS: 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. (132.3.48.140, UDP_-_EDNS0_4096_D_KN)
- af.mil/CNAME 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.
- b1r9m5iceg.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/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
