gov.mg
Updated:
2023-09-25 08:46:59 UTC (467 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- gov.mg/A
- gov.mg/MX
- gov.mg/NS
- gov.mg/SOA
- gov.mg/TXT
Secure (1)
- mg/SOA
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 11019)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46780)
- NSEC3 proving non-existence of gov.mg/DS
- mg/DNSKEY (alg 8, id 31916)
- mg/DNSKEY (alg 8, id 55276)
- mg/DS (alg 8, id 31916)
Delegation status
Insecure (1)
- mg to gov.mg
Secure (1)
- . to mg
Notices
Errors (7)
- NSEC3 proving non-existence of gov.mg/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of gov.mg/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- gov.mg zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (41.207.52.196)
- gov.mg/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (41.207.52.196, UDP_-_NOEDNS_)
- gov.mg/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (41.207.52.196, UDP_-_NOEDNS_)
- gov.mg/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (51.178.182.212, UDP_-_NOEDNS_)
- gov.mg/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
- NSEC3 proving non-existence of gov.mg/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of gov.mg/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- gov.mg/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
