View on GitHub

DNSViz: A DNS visualization tool

militaryonesource.mil

Updated: 2024-05-29 15:20:28 UTC (207 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Secure (4)
  • militaryonesource.mil/A
  • militaryonesource.mil/NS
  • militaryonesource.mil/SOA
  • militaryonesource.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 5613)
  • mil/DNSKEY (alg 8, id 16801)
  • mil/DNSKEY (alg 8, id 45154)
  • mil/DNSKEY (alg 8, id 9246)
  • mil/DS (alg 8, id 16801)
  • militaryonesource.mil/DNSKEY (alg 13, id 14815)
  • militaryonesource.mil/DNSKEY (alg 13, id 17597)
  • militaryonesource.mil/DS (alg 13, id 17597)
  • militaryonesource.mil/DS (alg 13, id 17597)

Delegation statusDelegation status

Secure (2)
  • . to mil
  • mil to militaryonesource.mil

NoticesNotices

Warnings (8)
  • militaryonesource.mil/A: 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:c144:1:155::243, 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/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:120:c:162::243, 2608:4122:2:154::243, 2608:4163:1:143::243, 2608:c144:1:155::243, 2608:c184:1:180::243, UDP_-_EDNS0_4096_D_KN)
  • militaryonesource.mil/SOA: 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_0x20)
  • 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:c184:1:180::243, UDP_-_EDNS0_4096_D_KN)

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph