nrc.gov
Updated:
2020-08-17 23:07:34 UTC (1559 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- nrc.gov/A
- nrc.gov/MX
- nrc.gov/NS
- nrc.gov/SOA
- nrc.gov/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46594)
- gov/DNSKEY (alg 8, id 26665)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- nrc.gov/DNSKEY (alg 8, id 55441)
- nrc.gov/DNSKEY (alg 8, id 58014)
- nrc.gov/DNSKEY (alg 8, id 60858)
- nrc.gov/DS (alg 8, id 55441)
- nrc.gov/DS (alg 8, id 55441)
Delegation status
Secure (2)
- . to gov
- gov to nrc.gov
Notices
Errors (8)
- nrc.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (192.198.87.242, 2001:49f0:d064:6:1000::187, 2607:5600:143:0:1000::101)
- nrc.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:49f0:d064:6:1000::187, UDP_-_NOEDNS_)
- nrc.gov/A: The UDP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (192.198.87.242, 2607:5600:143:0:1000::101, UDP_-_EDNS0_4096_D_K)
- nrc.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:49f0:d064:6:1000::187, UDP_-_NOEDNS_)
- nrc.gov/NS: The UDP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (192.198.87.242, 2607:5600:143:0:1000::101, UDP_-_EDNS0_4096_D_K)
- nrc.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- n4iz8w396x.nrc.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- nrc.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (14)
- gov to nrc.gov: Authoritative AAAA records exist for ns1.nrc.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- gov to nrc.gov: Authoritative AAAA records exist for ns2.nrc.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- gov to nrc.gov: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gov zone): dnssec14.datamtn.com See RFC 1034, Sec. 4.2.2.
- gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gov/DS (alg 8, id 7698): 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.
- gov/DS (alg 8, id 7698): 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.
- nrc.gov/DS (alg 8, id 55441): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- nrc.gov/DS (alg 8, id 55441): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- nrc.gov/DS (alg 8, id 55441): 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.
- nrc.gov/DS (alg 8, id 55441): 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.
- nrc.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- n4iz8w396x.nrc.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- nrc.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
