google.com.mm
Updated:
2022-01-07 22:27:25 UTC (1442 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (9)
- google.com.mm/A
- google.com.mm/A
- google.com.mm/AAAA
- google.com.mm/AAAA
- google.com.mm/MX
- google.com.mm/NS
- google.com.mm/SOA
- google.com.mm/SOA
- google.com.mm/TXT
Secure (1)
- com.mm/SOA
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- NSEC3 proving non-existence of google.com.mm/DS
- com.mm/DNSKEY (alg 8, id 22462)
- com.mm/DNSKEY (alg 8, id 65160)
- com.mm/DS (alg 8, id 22462)
- mm/DNSKEY (alg 8, id 18589)
- mm/DNSKEY (alg 8, id 32298)
- mm/DS (alg 8, id 18589)
Delegation status
Insecure (1)
- com.mm to google.com.mm
Secure (2)
- . to mm
- mm to com.mm
Notices
Errors (3)
- NSEC3 proving non-existence of google.com.mm/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 google.com.mm/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- google.com.mm/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
- NSEC3 proving non-existence of google.com.mm/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of google.com.mm/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- google.com.mm/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
