inherentresolve.mil

Updated: 2021-01-15 14:05:37 UTC (1437 days ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

Notices

DNSSEC Authentication Chain

RRset status

Bogus (5)

inherentresolve.mil/A
inherentresolve.mil/NS
inherentresolve.mil/SOA
inherentresolve.mil/SOA
inherentresolve.mil/TXT

DNSKEY/DS/NSEC status

Bogus (4)

inherentresolve.mil/DNSKEY (alg 8, id 21469)
inherentresolve.mil/DNSKEY (alg 8, id 2688)
inherentresolve.mil/DNSKEY (alg 8, id 47722)
inherentresolve.mil/DNSKEY (alg 8, id 48408)

Secure (7)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 42351)
inherentresolve.mil/DS (alg 8, id 38062)
mil/DNSKEY (alg 8, id 24363)
mil/DNSKEY (alg 8, id 51349)
mil/DS (alg 8, id 51349)
mil/DS (alg 8, id 51349)

Non_existent (1)

inherentresolve.mil/DNSKEY (alg 8, id 38062)

Delegation status

Bogus (1)

mil to inherentresolve.mil

Secure (1)

. to mil

Notices

Errors (9)

inherentresolve.mil/DNSKEY (alg 8, id 2688): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (214.26.71.170, 214.27.97.204, UDP_-_EDNS0_4096_D_KN)
inherentresolve.mil/DNSKEY (alg 8, id 48408): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (214.26.165.219, UDP_-_EDNS0_4096_D_KN)
inherentresolve.mil/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (214.26.71.170, TCP_-_EDNS0_4096_D_N)
mil to inherentresolve.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. (214.26.71.170, 214.26.165.219, 214.27.97.204, UDP_-_EDNS0_4096_D_KN)
mil to inherentresolve.mil: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (214.26.71.170, 214.26.165.219, 214.27.97.204, UDP_-_EDNS0_4096_D_KN)
inherentresolve.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
inherentresolve.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
inherentresolve.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
7eywkfvgs3.inherentresolve.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (14)

RRSIG inherentresolve.mil/TXT alg 8, id 48408: The value of the Signature Inception field of the RRSIG RR (2021-01-15 14:05:29+00:00) is within possible clock skew range (8 seconds) of the current time (2021-01-15 14:05:37+00:00). See RFC 4035, Sec. 5.3.1.
inherentresolve.mil/DNSKEY (alg 8, id 21469): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (214.26.71.170, 214.27.97.204, UDP_-_EDNS0_4096_D_KN)
inherentresolve.mil/DNSKEY (alg 8, id 47722): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (214.26.165.219, UDP_-_EDNS0_4096_D_KN)
inherentresolve.mil/DS (alg 8, id 38062): 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.154.234, UDP_-_EDNS0_4096_D_KN)
inherentresolve.mil/DS (alg 8, id 38062): 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.154.234, UDP_-_EDNS0_4096_D_KN)
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.
inherentresolve.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
inherentresolve.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
inherentresolve.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
inherentresolve.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
7eywkfvgs3.inherentresolve.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.