mail.mil
Updated:
2021-05-24 17:37:43 UTC (1271 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- mail.mil/MX
- mail.mil/NS
- mail.mil/SOA
- mail.mil/TXT
DNSKEY/DS/NSEC status
Secure (13)
- ./DNSKEY (alg 8, id 14631)
- ./DNSKEY (alg 8, id 20326)
- mail.mil/DNSKEY (alg 8, id 28882)
- mail.mil/DNSKEY (alg 8, id 37117)
- mail.mil/DNSKEY (alg 8, id 40044)
- mail.mil/DNSKEY (alg 8, id 48547)
- mail.mil/DS (alg 8, id 48547)
- mail.mil/DS (alg 8, id 48547)
- mil/DNSKEY (alg 8, id 16560)
- mil/DNSKEY (alg 8, id 51349)
- mil/DNSKEY (alg 8, id 61794)
- mil/DS (alg 8, id 51349)
- mil/DS (alg 8, id 51349)
Delegation status
Secure (2)
- . to mil
- mil to mail.mil
Notices
Errors (10)
- mail.mil zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (214.3.160.20)
- mail.mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (214.3.125.233)
- mail.mil/DNSKEY: No response was received from the server over TCP (tried 2 times). See RFC 1035, Sec. 4.2. (214.3.160.20, TCP_-_EDNS0_4096_D_KN)
- mail.mil/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (214.3.125.233, UDP_-_NOEDNS_)
- mail.mil/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (214.3.160.20, TCP_-_EDNS0_4096_D_N)
- mail.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- mail.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- mail.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- mail.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- osr3y8jud5.mail.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
- mail.mil/DS (alg 8, id 48547): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- mail.mil/DS (alg 8, id 48547): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- mail.mil/DS (alg 8, id 48547): 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.
- mail.mil/DS (alg 8, id 48547): 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): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- mil/DS (alg 8, id 51349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.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.
- osr3y8jud5.mail.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- mail.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- mail.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- mail.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
