bn | DNSViz

Updated: 2021-09-09 19:10:45 UTC (1173 days ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 26838)
bn/DNSKEY (alg 8, id 26224)
bn/DNSKEY (alg 8, id 54543)
bn/DNSKEY (alg 8, id 9994)
bn/DS (alg 8, id 26224)

RRSIG bn/SOA alg 8, id 54543: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
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 TCP (tried 12 times). See RFC 1035, Sec. 4.2. (202.93.214.163, TCP_-_EDNS0_4096_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)
sn9b6l15e2.bn/A has errors; select the "Denial of existence" DNSSEC option to see them.
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.

bn/NSEC3PARAM: 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 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, UDP_-_EDNS0_4096_D_KN_0x20)
sn9b6l15e2.bn/A has warnings; select the "Denial of existence" DNSSEC option to see them.
bn/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.