dfas.mil
Updated:
2021-03-15 19:15:52 UTC (1398 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- dfas.mil/MX
- dfas.mil/NS
- dfas.mil/SOA
- dfas.mil/TXT
DNSKEY/DS/NSEC status
Secure (14)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 42351)
- dfas.mil/DNSKEY (alg 8, id 13996)
- dfas.mil/DNSKEY (alg 8, id 17326)
- dfas.mil/DNSKEY (alg 8, id 38790)
- dfas.mil/DNSKEY (alg 8, id 46518)
- dfas.mil/DNSKEY (alg 8, id 56265)
- dfas.mil/DS (alg 8, id 17326)
- dfas.mil/DS (alg 8, id 17326)
- mil/DNSKEY (alg 8, id 11853)
- mil/DNSKEY (alg 8, id 19128)
- 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 dfas.mil
Notices
Errors (9)
- mil zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (199.252.162.234)
- mil zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (199.252.180.234)
- mil/DNSKEY: No response was received from the server over TCP (tried 2 times). See RFC 1035, Sec. 4.2. (199.252.162.234, TCP_-_EDNS0_4096_D_KN)
- mil/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.252.157.234, UDP_-_NOEDNS_)
- mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (199.252.162.234, 199.252.180.234, UDP_-_EDNS0_512_D_KN)
- qw5vgazcdt.dfas.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- dfas.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- dfas.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- dfas.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (13)
- dfas.mil/DS (alg 8, id 17326): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- dfas.mil/DS (alg 8, id 17326): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- dfas.mil/DS (alg 8, id 17326): 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.
- dfas.mil/DS (alg 8, id 17326): 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.
- dfas.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. (204.34.89.139, 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.
- qw5vgazcdt.dfas.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- dfas.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- dfas.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- dfas.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
