nro.gov
Updated:
2024-06-08 05:18:09 UTC (103 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (10)
- ./SOA
- nro.gov/A (NXDOMAIN)
- nro.gov/AAAA (NXDOMAIN)
- nro.gov/CDNSKEY (NXDOMAIN)
- nro.gov/CDS (NXDOMAIN)
- nro.gov/MX (NXDOMAIN)
- nro.gov/NS (NXDOMAIN)
- nro.gov/NSEC3PARAM (NXDOMAIN)
- nro.gov/SOA (NXDOMAIN)
- nro.gov/TXT (NXDOMAIN)
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 5613)
- gov/DNSKEY (alg 13, id 2536)
- gov/DNSKEY (alg 13, id 35496)
- gov/DS (alg 13, id 2536)
- nro.gov/DS (alg 8, id 10051)
- nro.gov/DS (alg 8, id 27892)
Non_existent (2)
- nro.gov/DNSKEY (alg 8, id 10051)
- nro.gov/DNSKEY (alg 8, id 27892)
Delegation status
Bogus (1)
- gov to nro.gov
Secure (1)
- . to gov
Notices
Errors (24)
- ./SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (209.22.180.120, 214.3.129.40, UDP_-_EDNS0_4096_D_KN)
- gov to nro.gov: 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, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- gov to nro.gov: 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, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- nro.gov/A (NXDOMAIN): An SOA RR with owner name (.) not matching the zone name (nro.gov) was returned with the NXDOMAIN response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.1. (209.22.180.120, 214.3.129.40, UDP_-_EDNS0_4096_D_KN)
- nro.gov/A (NXDOMAIN): No NSEC RR(s) were returned to validate the NXDOMAIN response. See RFC 4035, Sec. 3.1.3.2, RFC 5155, Sec. 7.2.2. (209.22.180.120, 214.3.129.40, UDP_-_EDNS0_4096_D_KN)
- nro.gov/AAAA (NXDOMAIN): An SOA RR with owner name (.) not matching the zone name (nro.gov) was returned with the NXDOMAIN response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.1. (209.22.180.120, 214.3.129.40, UDP_-_EDNS0_4096_D_KN)
- nro.gov/AAAA (NXDOMAIN): No NSEC RR(s) were returned to validate the NXDOMAIN response. See RFC 4035, Sec. 3.1.3.2, RFC 5155, Sec. 7.2.2. (209.22.180.120, 214.3.129.40, UDP_-_EDNS0_4096_D_KN)
- nro.gov/CDNSKEY (NXDOMAIN): An SOA RR with owner name (.) not matching the zone name (nro.gov) was returned with the NXDOMAIN response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.1. (209.22.180.120, 214.3.129.40, UDP_-_EDNS0_4096_D_KN)
- nro.gov/CDNSKEY (NXDOMAIN): No NSEC RR(s) were returned to validate the NXDOMAIN response. See RFC 4035, Sec. 3.1.3.2, RFC 5155, Sec. 7.2.2. (209.22.180.120, 214.3.129.40, UDP_-_EDNS0_4096_D_KN)
- nro.gov/CDS (NXDOMAIN): An SOA RR with owner name (.) not matching the zone name (nro.gov) was returned with the NXDOMAIN response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.1. (209.22.180.120, 214.3.129.40, UDP_-_EDNS0_4096_D_KN)
- nro.gov/CDS (NXDOMAIN): No NSEC RR(s) were returned to validate the NXDOMAIN response. See RFC 4035, Sec. 3.1.3.2, RFC 5155, Sec. 7.2.2. (209.22.180.120, 214.3.129.40, UDP_-_EDNS0_4096_D_KN)
- nro.gov/MX (NXDOMAIN): An SOA RR with owner name (.) not matching the zone name (nro.gov) was returned with the NXDOMAIN response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.1. (209.22.180.120, 214.3.129.40, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- nro.gov/MX (NXDOMAIN): No NSEC RR(s) were returned to validate the NXDOMAIN response. See RFC 4035, Sec. 3.1.3.2, RFC 5155, Sec. 7.2.2. (209.22.180.120, 214.3.129.40, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- nro.gov/NS (NXDOMAIN): An SOA RR with owner name (.) not matching the zone name (nro.gov) was returned with the NXDOMAIN response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.1. (209.22.180.120, 214.3.129.40, UDP_-_EDNS0_4096_D_KN)
- nro.gov/NS (NXDOMAIN): No NSEC RR(s) were returned to validate the NXDOMAIN response. See RFC 4035, Sec. 3.1.3.2, RFC 5155, Sec. 7.2.2. (209.22.180.120, 214.3.129.40, UDP_-_EDNS0_4096_D_KN)
- nro.gov/NSEC3PARAM (NXDOMAIN): An SOA RR with owner name (.) not matching the zone name (nro.gov) was returned with the NXDOMAIN response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.1. (209.22.180.120, 214.3.129.40, UDP_-_EDNS0_4096_D_KN)
- nro.gov/NSEC3PARAM (NXDOMAIN): No NSEC RR(s) were returned to validate the NXDOMAIN response. See RFC 4035, Sec. 3.1.3.2, RFC 5155, Sec. 7.2.2. (209.22.180.120, 214.3.129.40, UDP_-_EDNS0_4096_D_KN)
- nro.gov/SOA (NXDOMAIN): An SOA RR with owner name (.) not matching the zone name (nro.gov) was returned with the NXDOMAIN response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.1. (209.22.180.120, 214.3.129.40, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- nro.gov/SOA (NXDOMAIN): No NSEC RR(s) were returned to validate the NXDOMAIN response. See RFC 4035, Sec. 3.1.3.2, RFC 5155, Sec. 7.2.2. (209.22.180.120, 214.3.129.40, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- nro.gov/TXT (NXDOMAIN): An SOA RR with owner name (.) not matching the zone name (nro.gov) was returned with the NXDOMAIN response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.1. (209.22.180.120, 214.3.129.40, UDP_-_EDNS0_4096_D_KN)
- nro.gov/TXT (NXDOMAIN): No NSEC RR(s) were returned to validate the NXDOMAIN response. See RFC 4035, Sec. 3.1.3.2, RFC 5155, Sec. 7.2.2. (209.22.180.120, 214.3.129.40, UDP_-_EDNS0_4096_D_KN)
- nro.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- 8vcp0.gmywp.nro.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- nro.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (1)
- gov to nro.gov: The following NS name(s) were found in the delegation NS RRset (i.e., in the gov zone), but not in the authoritative NS RRset: a11svidzns001.nro.mil, w31svidzns001.nro.mil See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
