mofa.gov.bd
Updated:
2023-10-30 14:22:14 UTC (about a year ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (6)
- gov.bd/SOA
- gov.bd/SOA
- mofa.gov.bd/A
- mofa.gov.bd/MX
- mofa.gov.bd/NS
- mofa.gov.bd/SOA
Secure (1)
- bd/SOA
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46780)
- NSEC proving non-existence of gov.bd/DS
- bd/DNSKEY (alg 8, id 19320)
- bd/DNSKEY (alg 8, id 26044)
- bd/DS (alg 8, id 26044)
- bd/DS (alg 8, id 26044)
Delegation status
Insecure (2)
- bd to gov.bd
- gov.bd to mofa.gov.bd
Secure (1)
- . to bd
Notices
Errors (2)
- bd zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2407:5000:88:4::231, 2407:5000:88:4::232, 2407:5000:88:5::3)
- gov.bd zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2407:5000:88:4::231, 2407:5000:88:4::232, 2407:5000:88:5::3)
Warnings (4)
- bd/DS (alg 8, id 26044): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- bd/DS (alg 8, id 26044): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- bd/DS (alg 8, id 26044): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- bd/DS (alg 8, id 26044): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
JavaScript is required to make the graph below interactive.
