bn
Updated:
2021-07-19 11:46:53 UTC (1229 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (2)
- bn/NS
- bn/SOA
DNSKEY/DS/NSEC status
Bogus (3)
- bn/DNSKEY (alg 8, id 26224)
- bn/DNSKEY (alg 8, id 30096)
- bn/DNSKEY (alg 8, id 9994)
Secure (4)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- bn/DS (alg 8, id 26224)
- bn/DS (alg 8, id 9994)
Delegation status
Bogus (1)
- . to bn
Notices
Errors (15)
- . 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)
- RRSIG bn/DNSKEY alg 8, id 26224: The Signature Expiration field of the RRSIG RR (2021-07-17 23:59:59+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
- RRSIG bn/DNSKEY alg 8, id 26224: The Signature Expiration field of the RRSIG RR (2021-07-17 23:59:59+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
- RRSIG bn/DNSKEY alg 8, id 26224: The Signature Expiration field of the RRSIG RR (2021-07-17 23:59:59+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
- RRSIG bn/DNSKEY alg 8, id 9994: The Signature Expiration field of the RRSIG RR (2021-07-17 23:59:59+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
- RRSIG bn/DNSKEY alg 8, id 9994: The Signature Expiration field of the RRSIG RR (2021-07-17 23:59:59+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
- RRSIG bn/DNSKEY alg 8, id 9994: The Signature Expiration field of the RRSIG RR (2021-07-17 23:59:59+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
- bn zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (202.93.214.163)
- bn zone: There was an error resolving the following NS name(s) to address(es): ns1.bnnic.bn, ns2.bnnic.bn
- bn/DNSKEY: No response was received from the server over TCP (tried 10 times). See RFC 1035, Sec. 4.2. (202.93.214.163, TCP_-_EDNS0_4096_D_N)
- 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/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/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.
- mq2tvn0ea3.bn/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- bn/NS: 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. (202.93.214.163, UDP_-_EDNS0_4096_D_KN)
- bn/SOA: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (202.93.214.163, UDP_-_EDNS0_4096_D_KN)
- bn/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- mq2tvn0ea3.bn/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
