militaryonesource.mil

Updated: 2023-11-30 13:31:56 UTC (388 days ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

Notices

DNSSEC Authentication Chain

RRset status

Secure (4)

militaryonesource.mil/A
militaryonesource.mil/NS
militaryonesource.mil/SOA
militaryonesource.mil/TXT

DNSKEY/DS/NSEC status

Secure (13)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 46780)
mil/DNSKEY (alg 8, id 16801)
mil/DNSKEY (alg 8, id 29343)
mil/DNSKEY (alg 8, id 51225)
mil/DS (alg 8, id 16801)
militaryonesource.mil/DNSKEY (alg 13, id 17597)
militaryonesource.mil/DNSKEY (alg 13, id 29526)
militaryonesource.mil/DNSKEY (alg 13, id 42667)
militaryonesource.mil/DS (alg 13, id 17597)
militaryonesource.mil/DS (alg 13, id 17597)
militaryonesource.mil/DS (alg 13, id 42667)
militaryonesource.mil/DS (alg 13, id 42667)

Delegation status

Secure (2)

. to mil
mil to militaryonesource.mil

Notices

Errors (2)

mil to militaryonesource.mil: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.252.143.243, 199.252.157.235, 2608:140:c:157::235, 2608:4163:1:143::243, UDP_-_EDNS0_4096_D_KN)
mil to militaryonesource.mil: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no DS RR matched a DNSKEY with algorithm 13 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.252.143.243, 199.252.157.235, 2608:140:c:157::235, 2608:4163:1:143::243, UDP_-_EDNS0_4096_D_KN)

Warnings (14)

mil/DNSKEY (alg 8, id 16801): 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.155.234, UDP_-_EDNS0_4096_D_KN)
mil/DNSKEY (alg 8, id 29343): 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.155.234, UDP_-_EDNS0_4096_D_KN)
mil/DNSKEY (alg 8, id 51225): 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.155.234, UDP_-_EDNS0_4096_D_KN)
militaryonesource.mil/DS (alg 13, id 17597): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
militaryonesource.mil/DS (alg 13, id 17597): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
militaryonesource.mil/DS (alg 13, id 17597): 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.
militaryonesource.mil/DS (alg 13, id 17597): 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.
militaryonesource.mil/DS (alg 13, id 42667): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
militaryonesource.mil/DS (alg 13, id 42667): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
militaryonesource.mil/DS (alg 13, id 42667): 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.
militaryonesource.mil/DS (alg 13, id 42667): 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.
militaryonesource.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. (2608:4163:1:143::243, UDP_-_EDNS0_4096_D_KN)
militaryonesource.mil/TXT: 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. (2608:140:c:157::235, UDP_-_EDNS0_4096_D_KN)
militaryonesource.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.