nro.mil
Updated:
2023-07-10 18:52:45 UTC (504 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 (13)
- ./DNSKEY (alg 8, id 11019)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- mil/DNSKEY (alg 8, id 40318)
- mil/DNSKEY (alg 8, id 62470)
- mil/DNSKEY (alg 8, id 62514)
- mil/DS (alg 8, id 62470)
- nro.mil/DNSKEY (alg 8, id 29556)
- nro.mil/DNSKEY (alg 8, id 30540)
- nro.mil/DNSKEY (alg 8, id 62806)
- nro.mil/DS (alg 8, id 10330)
- nro.mil/DS (alg 8, id 62806)
- nro.mil/DS (alg 8, id 62806)
Non_existent (1)
- nro.mil/DNSKEY (alg 8, id 10330)
Delegation status
Secure (2)
- . to mil
- mil to nro.mil
Notices
Errors (7)
- mil to nro.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. (209.22.180.120, 214.3.129.40, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
- mil to nro.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. (209.22.180.120, 214.3.129.40, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
- mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2608:c144:1:155::234)
- nro.mil/CNAME 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.
- 91k6ju7qmy.nro.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (23)
- ./DNSKEY (alg 8, id 11019): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 11019): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:200::b, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 20326): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 20326): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:200::b, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 60955): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 60955): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:200::b, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:200::b, UDP_-_EDNS0_512_D_KN)
- nro.mil/DNSKEY (alg 8, id 29556): 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/DNSKEY (alg 8, id 30540): 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/DNSKEY (alg 8, id 62806): 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/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/DS (alg 8, id 62806): 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 62806): 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 62806): 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 62806): 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/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- nro.mil/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- 91k6ju7qmy.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.
- nro.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
