ncifcrf.gov

Updated: 2020-06-20 14:18:11 UTC (1617 days ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

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 (22)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 46594)
./DNSKEY (alg 8, id 48903)
gov/DNSKEY (alg 8, id 40176)
gov/DNSKEY (alg 8, id 7698)
gov/DS (alg 8, id 7698)
gov/DS (alg 8, id 7698)
ncifcrf.gov/DNSKEY (alg 5, id 11313)
ncifcrf.gov/DNSKEY (alg 5, id 1230)
ncifcrf.gov/DNSKEY (alg 5, id 26233)
ncifcrf.gov/DNSKEY (alg 5, id 49455)
ncifcrf.gov/DNSKEY (alg 5, id 58258)
ncifcrf.gov/DNSKEY (alg 5, id 60886)
ncifcrf.gov/DNSKEY (alg 5, id 65491)
ncifcrf.gov/DS (alg 5, id 26233)
ncifcrf.gov/DS (alg 5, id 26233)
ncifcrf.gov/DS (alg 5, id 58258)
ncifcrf.gov/DS (alg 5, id 58258)
ncifcrf.gov/DS (alg 5, id 60886)
ncifcrf.gov/DS (alg 5, id 60886)
ncifcrf.gov/DS (alg 5, id 65491)
ncifcrf.gov/DS (alg 5, id 65491)

Delegation status

Secure (2)

. to gov
gov to ncifcrf.gov

Notices

Errors (5)

ncifcrf.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (2607:f220:402:1801::a570:4e6)
ncifcrf.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2607:f220:418:4101::80e7:401)
ncifcrf.gov/A: No response was received from the server over UDP (tried 13 times). See RFC 1035, Sec. 4.2. (2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D)
ncifcrf.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:f220:418:4101::80e7:401, UDP_-_NOEDNS_)
ncifcrf.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (2607:f220:402:1801::a570:4e6, TCP_-_EDNS0_4096_D)

Warnings (97)

RRSIG ncifcrf.gov/A alg 5, id 11313: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG ncifcrf.gov/A alg 5, id 1230: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG ncifcrf.gov/A alg 5, id 49455: 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 11313: 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 1230: 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 49455: 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 11313: 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 11313: 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 11313: 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 11313: 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 11313: 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 11313: 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 11313: 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 1230: 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 1230: 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 1230: 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 1230: 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 1230: 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 1230: 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 1230: 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 26233: 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 26233: 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 26233: 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 26233: 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 26233: 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 26233: 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 26233: 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 49455: 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 49455: 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 49455: 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 49455: 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 49455: 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 49455: 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 49455: 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 58258: 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 58258: 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 58258: 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 58258: 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 58258: 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 58258: 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 58258: 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 60886: 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 60886: 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 60886: 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 60886: 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 60886: 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 60886: 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 60886: 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 65491: 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 65491: 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 65491: 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 65491: 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 65491: 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 65491: 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 65491: 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 11313: 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 1230: 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 49455: 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 11313: 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 1230: 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 49455: 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 11313: 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 1230: 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 49455: 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 11313: 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 1230: 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 49455: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
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.
ncifcrf.gov/DNSKEY (alg 5, id 11313): 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. (2607:f220:404:101::80e7:80fb, UDP_-_EDNS0_4096_D_K)
ncifcrf.gov/DNSKEY (alg 5, id 1230): 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. (2607:f220:404:101::80e7:80fb, UDP_-_EDNS0_4096_D_K)
ncifcrf.gov/DNSKEY (alg 5, id 26233): 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. (2607:f220:404:101::80e7:80fb, UDP_-_EDNS0_4096_D_K)
ncifcrf.gov/DNSKEY (alg 5, id 49455): 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. (2607:f220:404:101::80e7:80fb, UDP_-_EDNS0_4096_D_K)
ncifcrf.gov/DNSKEY (alg 5, id 58258): 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. (2607:f220:404:101::80e7:80fb, UDP_-_EDNS0_4096_D_K)
ncifcrf.gov/DNSKEY (alg 5, id 60886): 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. (2607:f220:404:101::80e7:80fb, UDP_-_EDNS0_4096_D_K)
ncifcrf.gov/DNSKEY (alg 5, id 65491): 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. (2607:f220:404:101::80e7:80fb, UDP_-_EDNS0_4096_D_K)
ncifcrf.gov/DS (alg 5, id 26233): 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 26233): 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 26233): 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 26233): 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 58258): 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 58258): 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 58258): 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 58258): 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 60886): 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 60886): 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 60886): 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 60886): 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 65491): 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 65491): 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 65491): 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 65491): 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.
ulty4hcsqr.ncifcrf.gov/A 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.