bn
Updated:
2022-05-18 02:34:33 UTC (703 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (3)
- bn/NS
- bn/NSEC3PARAM
- bn/SOA
DNSKEY/DS/NSEC status
Bogus (3)
- bn/DNSKEY (alg 8, id 26224)
- bn/DNSKEY (alg 8, id 62205)
- bn/DNSKEY (alg 8, id 9994)
Secure (3)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 47671)
- bn/DS (alg 8, id 26224)
Delegation status
Bogus (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. (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)
- RRSIG bn/DNSKEY alg 8, id 26224: The Signature Expiration field of the RRSIG RR (2022-05-17 23:59:59+00:00) is 2 hours, 34 minutes in the past.
- RRSIG bn/DNSKEY alg 8, id 26224: The Signature Expiration field of the RRSIG RR (2022-05-17 23:59:59+00:00) is 2 hours, 34 minutes in the past.
- RRSIG bn/DNSKEY alg 8, id 26224: The Signature Expiration field of the RRSIG RR (2022-05-17 23:59:59+00:00) is 2 hours, 34 minutes in the past.
- RRSIG bn/DNSKEY alg 8, id 9994: The Signature Expiration field of the RRSIG RR (2022-05-17 23:59:59+00:00) is 2 hours, 34 minutes in the past.
- RRSIG bn/DNSKEY alg 8, id 9994: The Signature Expiration field of the RRSIG RR (2022-05-17 23:59:59+00:00) is 2 hours, 34 minutes in the past.
- RRSIG bn/DNSKEY alg 8, id 9994: The Signature Expiration field of the RRSIG RR (2022-05-17 23:59:59+00:00) is 2 hours, 34 minutes in the past.
- RRSIG bn/SOA alg 8, id 62205: The cryptographic signature of the RRSIG RR does not properly validate.
- bn zone: The server(s) were not responsive to queries over TCP. (202.93.214.163)
- bn/DNSKEY: No response was received from the server over TCP (tried 6 times). (202.93.214.163, TCP_-_EDNS0_4096_)
- bn/DNSKEY: No response was received from the server over UDP (tried 4 times). (202.93.214.163, UDP_-_EDNS0_512_D_KN)
- bn/NS: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 11 times) with EDNS enabled. (202.93.214.163, UDP_-_NOEDNS_)
- bn/NS: No response was received from the server over UDP (tried 11 times) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). (202.93.214.163, UDP_-_EDNS0_4096_D_KN)
- bn/NS: The DNSSEC records necessary to validate the response could not be retrieved from the server. (202.93.214.163, UDP_-_EDNS0_4096_D_KN)
- bn/SOA: No response was received from the server over TCP (tried 3 times). (202.93.214.163, TCP_-_EDNS0_4096_D_N)
- bn/SOA: No response was received from the server over UDP (tried 12 times). (202.93.214.163, UDP_-_NOEDNS_)
Warnings (2)
- bn/NSEC3PARAM: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). (202.93.214.163, UDP_-_EDNS0_4096_D_KN)
- bn/SOA: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). (202.93.214.163, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
