tricare.mil
Updated:
2020-06-30 18:08:49 UTC (1635 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (4)
- tricare.mil/A
- tricare.mil/NS
- tricare.mil/SOA
- tricare.mil/TXT
Secure (1)
- mil/SOA
DNSKEY/DS/NSEC status
Insecure (3)
- tricare.mil/DNSKEY (alg 8, id 13611)
- tricare.mil/DNSKEY (alg 8, id 3285)
- tricare.mil/DNSKEY (alg 8, id 53695)
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46594)
- ./DNSKEY (alg 8, id 48903)
- NSEC3 proving non-existence of tricare.mil/DS
- mil/DNSKEY (alg 8, id 48726)
- mil/DNSKEY (alg 8, id 7765)
- mil/DNSKEY (alg 8, id 8223)
- mil/DS (alg 8, id 7765)
- mil/DS (alg 8, id 7765)
Delegation status
Insecure (1)
- mil to tricare.mil
Secure (1)
- . to mil
Notices
Errors (10)
- NSEC3 proving non-existence of tricare.mil/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of tricare.mil/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- 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/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.
- tricare.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- 58l6d130ig.tricare.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- tricare.mil/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
- NSEC3 proving non-existence of tricare.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of tricare.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- 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 7765): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- mil/DS (alg 8, id 7765): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- mil/DS (alg 8, id 7765): 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 7765): 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.
- 58l6d130ig.tricare.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- tricare.mil/DS 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.
JavaScript is required to make the graph below interactive.
