ncifcrf.gov
Updated:
2022-05-23 18:41:16 UTC (914 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- ncifcrf.gov/A
- ncifcrf.gov/AAAA
- ncifcrf.gov/MX
- ncifcrf.gov/NS
- ncifcrf.gov/SOA
- ncifcrf.gov/TXT
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 47671)
- gov/DNSKEY (alg 8, id 2706)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- ncifcrf.gov/DNSKEY (alg 5, id 27216)
- ncifcrf.gov/DNSKEY (alg 5, id 60628)
- ncifcrf.gov/DS (alg 5, id 60628)
- ncifcrf.gov/DS (alg 5, id 60628)
Delegation status
Secure (2)
- . to gov
- gov to ncifcrf.gov
Notices
Warnings (21)
- RRSIG ncifcrf.gov/A alg 5, id 27216: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG ncifcrf.gov/AAAA alg 5, id 27216: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG ncifcrf.gov/DNSKEY alg 5, id 27216: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG ncifcrf.gov/DNSKEY alg 5, id 27216: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG ncifcrf.gov/DNSKEY alg 5, id 60628: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG ncifcrf.gov/DNSKEY alg 5, id 60628: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG ncifcrf.gov/MX alg 5, id 27216: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG ncifcrf.gov/NS alg 5, id 27216: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG ncifcrf.gov/SOA alg 5, id 27216: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG ncifcrf.gov/TXT alg 5, id 27216: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- gov to ncifcrf.gov: Authoritative AAAA records exist for ns.nih.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- gov to ncifcrf.gov: Authoritative AAAA records exist for ns2.nih.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- gov to ncifcrf.gov: Authoritative AAAA records exist for ns3.nih.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- ncifcrf.gov/DS (alg 5, id 60628): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ncifcrf.gov/DS (alg 5, id 60628): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ncifcrf.gov/DS (alg 5, id 60628): 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.
- ncifcrf.gov/DS (alg 5, id 60628): 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.
- pyugn0z7dw.ncifcrf.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- ncifcrf.gov/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
- ncifcrf.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- ncifcrf.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
