bitcoincore.org
Updated:
2025-10-28 16:17:02 UTC (39 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (7)
- bitcoincore.org/A
- bitcoincore.org/CDNSKEY
- bitcoincore.org/CDS
- bitcoincore.org/MX
- bitcoincore.org/NS
- bitcoincore.org/SOA
- bitcoincore.org/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 38696)
- ./DNSKEY (alg 8, id 61809)
- bitcoincore.org/DNSKEY (alg 13, id 54958)
- bitcoincore.org/DNSKEY (alg 13, id 56028)
- bitcoincore.org/DS (alg 13, id 56028)
- org/DNSKEY (alg 8, id 26974)
- org/DNSKEY (alg 8, id 37593)
- org/DNSKEY (alg 8, id 57769)
- org/DS (alg 8, id 26974)
Delegation status
Secure (2)
- . to org
- org to bitcoincore.org
Notices
Errors (16)
- bitcoincore.org zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (216.66.1.2, 2001:470:400::2)
- bitcoincore.org zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (216.66.1.2)
- bitcoincore.org/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (216.66.1.2, 2001:470:400::2, UDP_-_EDNS0_4096_D_KN)
- bitcoincore.org/CDNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (216.66.1.2, 2001:470:400::2, UDP_-_EDNS0_4096_D_KN)
- bitcoincore.org/CDS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (216.66.1.2, 2001:470:400::2, UDP_-_EDNS0_4096_D_KN)
- bitcoincore.org/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (216.66.1.2, 2001:470:400::2, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- bitcoincore.org/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (216.66.1.2, 2001:470:400::2, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- bitcoincore.org/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (216.66.1.2, UDP_-_EDNS0_4096_D_KN)
- bitcoincore.org/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (216.66.1.2, 2001:470:400::2, TCP_-_EDNS0_4096_D_N)
- bitcoincore.org/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (216.66.1.2, 2001:470:400::2, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- bitcoincore.org/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (216.66.1.2, UDP_-_EDNS0_4096_D_KN)
- bitcoincore.org/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- bitcoincore.org/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- bitcoincore.org/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
- sdu9e.od9hw.bitcoincore.org/A has errors; select the "Denial of existence" DNSSEC option to see them.
- bitcoincore.org/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (2)
- org to bitcoincore.org: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the org zone): ns-a.as397444.net See RFC 1034, Sec. 4.2.2.
- org to bitcoincore.org: The following NS name(s) were found in the delegation NS RRset (i.e., in the org zone), but not in the authoritative NS RRset: ns-a.as397444.org See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
