mail.mil
Updated:
2021-10-29 11:22:44 UTC (1153 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (5)
- mail.mil/MX
- mail.mil/NS
- mail.mil/NSEC3PARAM
- mail.mil/SOA
- mail.mil/TXT
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- mail.mil/DS (alg 8, id 48547)
- mil/DNSKEY (alg 8, id 39879)
- mil/DNSKEY (alg 8, id 56347)
- mil/DNSKEY (alg 8, id 61224)
- mil/DS (alg 8, id 56347)
Non_existent (2)
- mail.mil/DNSKEY (alg 8, id 40044)
- mail.mil/DNSKEY (alg 8, id 48547)
Delegation status
Bogus (1)
- mil to mail.mil
Secure (1)
- . to mil
Notices
Errors (10)
- 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 UDP (tried 4 times). See RFC 1035, Sec. 4.2. (214.3.160.20, UDP_-_EDNS0_512_D_KN)
- mail.mil/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (152.229.110.236, 214.3.160.20, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
- 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_)
- mil to mail.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.
- 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.
- 5wyhx0oncd.mail.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
- 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.
- mail.mil/DS (alg 8, id 48547): 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.180.234, UDP_-_EDNS0_4096_D_KN)
- mail.mil/DS (alg 8, id 48547): 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.180.234, UDP_-_EDNS0_4096_D_KN)
- 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/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
- 5wyhx0oncd.mail.mil/A 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.
JavaScript is required to make the graph below interactive.
