ncifcrf.gov
Updated:
2023-03-22 00:19:12 UTC (612 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (6)
- ncifcrf.gov/A
- ncifcrf.gov/AAAA
- ncifcrf.gov/MX
- ncifcrf.gov/NS
- ncifcrf.gov/SOA
- ncifcrf.gov/TXT
Secure (1)
- gov/SOA
DNSKEY/DS/NSEC status
Insecure (2)
- ncifcrf.gov/DNSKEY (alg 5, id 17250)
- ncifcrf.gov/DNSKEY (alg 5, id 7921)
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 951)
- NSEC3 proving non-existence of ncifcrf.gov/DS
- gov/DNSKEY (alg 8, id 24250)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Insecure (1)
- gov to ncifcrf.gov
Secure (1)
- . to gov
Notices
Errors (3)
- NSEC3 proving non-existence of ncifcrf.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of ncifcrf.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- ncifcrf.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (20)
- NSEC3 proving non-existence of ncifcrf.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of ncifcrf.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- RRSIG ncifcrf.gov/A alg 5, id 17250: 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 17250: 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 17250: 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 17250: 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 7921: 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 7921: 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 17250: 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 17250: 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 17250: 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 17250: 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 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.
- 8nki7mj9dt.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.
JavaScript is required to make the graph below interactive.
