nro.mil
Updated:
2022-07-18 12:43:44 UTC (863 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- nro.mil/MX
- nro.mil/NS
- nro.mil/NSEC3PARAM
- nro.mil/SOA
- nro.mil/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 20826)
- mil/DNSKEY (alg 8, id 50350)
- mil/DNSKEY (alg 8, id 51621)
- mil/DNSKEY (alg 8, id 56347)
- mil/DS (alg 8, id 56347)
- nro.mil/DNSKEY (alg 8, id 10330)
- nro.mil/DNSKEY (alg 8, id 31515)
- nro.mil/DNSKEY (alg 8, id 53985)
- nro.mil/DS (alg 8, id 10330)
- nro.mil/DS (alg 8, id 10330)
Delegation status
Secure (2)
- . to mil
- mil to nro.mil
Notices
Errors (9)
- mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (199.252.143.234)
- nro.mil/DNSKEY: No response was received from the server over TCP (tried 4 times). See RFC 1035, Sec. 4.2. (209.22.180.120, TCP_-_EDNS0_4096_D)
- nro.mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (214.3.129.40, UDP_-_EDNS0_512_D_KN)
- nro.mil/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (214.3.129.40, UDP_-_EDNS0_512_D_KN)
- nro.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- nro.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- g6tlrfjyaz.nro.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- nro.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- nro.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
- nro.mil/DS (alg 8, id 10330): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- nro.mil/DS (alg 8, id 10330): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- nro.mil/DS (alg 8, id 10330): 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.
- nro.mil/DS (alg 8, id 10330): 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.
- nro.mil/SOA: 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. (209.22.180.120, UDP_-_EDNS0_4096_D_KN)
- nro.mil/TXT: 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. (209.22.180.120, UDP_-_EDNS0_4096_D_KN)
- nro.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- g6tlrfjyaz.nro.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- nro.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- nro.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
