View on GitHub

DNSViz: A DNS visualization tool

tricare.mil

Updated: 2021-01-19 20:17:43 UTC (1278 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)
  • tricare.mil/A
  • tricare.mil/NS
  • tricare.mil/SOA
  • tricare.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 42351)
  • mil/DNSKEY (alg 8, id 19128)
  • mil/DNSKEY (alg 8, id 24363)
  • mil/DNSKEY (alg 8, id 51349)
  • mil/DS (alg 8, id 51349)
  • mil/DS (alg 8, id 51349)
  • tricare.mil/DNSKEY (alg 8, id 29598)
  • tricare.mil/DNSKEY (alg 8, id 5130)
  • tricare.mil/DNSKEY (alg 8, id 53695)
  • tricare.mil/DS (alg 8, id 53695)
  • tricare.mil/DS (alg 8, id 53695)

Delegation statusDelegation status

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

NoticesNotices

Errors (11)
  • mil/DS (alg 8, id 51349): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mil/DS (alg 8, id 51349): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • tricare.mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (214.2.253.50, 214.2.253.52)
  • tricare.mil/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (214.2.253.50, 214.2.253.52, UDP_-_NOEDNS_)
  • tricare.mil/DS (alg 8, id 53695): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • tricare.mil/DS (alg 8, id 53695): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • tricare.mil/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (214.2.253.50, 214.2.253.52, UDP_-_NOEDNS_)
  • tricare.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • tricare.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • nsfjq713o9.tricare.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • tricare.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (9)
  • mil to tricare.mil: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the mil zone): ns01-cernls-auth1.health.mil, ns01-cernls-auth2.health.mil See RFC 1034, Sec. 4.2.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.
  • tricare.mil/DS (alg 8, id 53695): 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.
  • tricare.mil/DS (alg 8, id 53695): 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.
  • tricare.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • tricare.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nsfjq713o9.tricare.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • tricare.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.

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