dfas.mil
Updated:
2023-10-31 16:02:25 UTC (419 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- dfas.mil/MX
- dfas.mil/NS
- dfas.mil/NSEC3PARAM
- dfas.mil/SOA
- dfas.mil/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46780)
- dfas.mil/DNSKEY (alg 8, id 44764)
- dfas.mil/DNSKEY (alg 8, id 50841)
- dfas.mil/DNSKEY (alg 8, id 61194)
- dfas.mil/DS (alg 8, id 44764)
- dfas.mil/DS (alg 8, id 44764)
- mil/DNSKEY (alg 8, id 16801)
- mil/DNSKEY (alg 8, id 29343)
- mil/DNSKEY (alg 8, id 44065)
- mil/DS (alg 8, id 16801)
Delegation status
Secure (2)
- . to mil
- mil to dfas.mil
Notices
Errors (5)
- mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2608:140:c:157::234, UDP_-_EDNS0_512_D_KN)
- dfas.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- nb6548dsgw.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 44764): 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 44764): 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 44764): 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 44764): 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 44764): 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. (199.252.143.234, UDP_-_EDNS0_4096_D_KN)
- dfas.mil/DS (alg 8, id 44764): 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. (199.252.143.234, UDP_-_EDNS0_4096_D_KN)
- dfas.mil/DS (alg 8, id 44764): 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. (199.252.143.234, UDP_-_EDNS0_4096_D_KN)
- dfas.mil/DS (alg 8, id 44764): 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. (199.252.143.234, UDP_-_EDNS0_4096_D_KN)
- dfas.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- nb6548dsgw.dfas.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- dfas.mil/DS 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.
