bn
Updated:
2022-05-19 21:25:47 UTC (917 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (1)
- bn/SOA
Secure (4)
- bn/NS
- bn/NSEC3PARAM
- bn/SOA
- bn/SOA
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 47671)
- bn/DNSKEY (alg 8, id 31740)
- bn/DNSKEY (alg 8, id 42604)
- bn/DNSKEY (alg 8, id 62205)
- bn/DNSKEY (alg 8, id 6468)
- bn/DS (alg 8, id 26224)
- bn/DS (alg 8, id 42604)
Non_existent (1)
- bn/DNSKEY (alg 8, id 26224)
Delegation status
Secure (1)
- . to bn
Notices
Errors (16)
- . to bn: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (194.0.1.33, 202.12.31.53, 204.61.216.87, 2001:500:14:6087:ad::1, 2001:dd8:12::53, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
- . to bn: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (194.0.1.33, 202.12.31.53, 204.61.216.87, 2001:500:14:6087:ad::1, 2001:dd8:12::53, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2001:500:12::d0d, UDP_-_EDNS0_512_D_KN)
- bn zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (202.93.214.163)
- bn/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (202.93.214.163, UDP_-_NOEDNS_)
- bn/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (202.93.214.163, UDP_-_EDNS0_512_D_KN)
- bn/NS: No response was received from the server over TCP (tried 4 times). See RFC 1035, Sec. 4.2. (202.93.214.163, TCP_-_EDNS0_4096_D)
- bn/NSEC3PARAM: No response was received from the server over TCP (tried 5 times). See RFC 1035, Sec. 4.2. (202.93.214.163, TCP_-_EDNS0_4096_D_KN)
- bn/SOA: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 11 times) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (202.93.214.163, UDP_-_NOEDNS_)
- bn/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (202.93.214.163, TCP_-_EDNS0_4096_D_N)
- bn/SOA: No response was received from the server over TCP (tried 4 times). See RFC 1035, Sec. 4.2. (202.93.214.163, TCP_-_EDNS0_4096_D)
- bn/SOA: No response was received from the server over UDP (tried 11 times) until EDNS was disabled. See RFC 6891, Sec. 6.2.6. (202.93.214.163, UDP_-_EDNS0_4096_D_KN)
- bn/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (202.93.214.163, UDP_-_NOEDNS__0x20)
- bn/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- bn/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- fbuqc0l8we.bn/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (2)
- bn/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- fbuqc0l8we.bn/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
