View on GitHub

DNSViz: A DNS visualization tool

google.com.mm

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Secure (1)
  • com.mm/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (9)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 5613)
  • 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 statusDelegation status

Lame (1)
  • com.mm to google.com.mm
Secure (2)
  • . to mm
  • mm to com.mm

NoticesNotices

Errors (19)
  • 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 zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (216.239.32.99, 216.239.34.99, 216.239.36.99, 216.239.38.99, 2001:4860:4802:32::63, 2001:4860:4802:34::63, 2001:4860:4802:36::63, 2001:4860:4802:38::63)
  • google.com.mm zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (216.239.32.99, 216.239.34.99, 216.239.36.99, 216.239.38.99, 2001:4860:4802:32::63, 2001:4860:4802:34::63, 2001:4860:4802:36::63, 2001:4860:4802:38::63)
  • google.com.mm/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (216.239.32.99, 216.239.34.99, 216.239.36.99, 216.239.38.99, 2001:4860:4802:32::63, 2001:4860:4802:34::63, 2001:4860:4802:36::63, 2001:4860:4802:38::63, UDP_-_EDNS0_4096_D_KN)
  • google.com.mm/AAAA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (216.239.32.99, 216.239.34.99, 216.239.36.99, 216.239.38.99, 2001:4860:4802:32::63, 2001:4860:4802:34::63, 2001:4860:4802:36::63, 2001:4860:4802:38::63, UDP_-_EDNS0_4096_D_KN)
  • google.com.mm/CDNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (216.239.32.99, 216.239.34.99, 216.239.36.99, 216.239.38.99, 2001:4860:4802:32::63, 2001:4860:4802:34::63, 2001:4860:4802:36::63, 2001:4860:4802:38::63, UDP_-_EDNS0_4096_D_KN)
  • google.com.mm/CDS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (216.239.32.99, 216.239.34.99, 216.239.36.99, 216.239.38.99, 2001:4860:4802:32::63, 2001:4860:4802:34::63, 2001:4860:4802:36::63, 2001:4860:4802:38::63, UDP_-_EDNS0_4096_D_KN)
  • google.com.mm/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (216.239.32.99, 216.239.34.99, 216.239.36.99, 216.239.38.99, 2001:4860:4802:32::63, 2001:4860:4802:34::63, 2001:4860:4802:36::63, 2001:4860:4802:38::63, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • google.com.mm/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (216.239.32.99, 216.239.34.99, 216.239.36.99, 216.239.38.99, 2001:4860:4802:32::63, 2001:4860:4802:34::63, 2001:4860:4802:36::63, 2001:4860:4802:38::63, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • google.com.mm/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (216.239.32.99, 216.239.34.99, 216.239.36.99, 216.239.38.99, 2001:4860:4802:32::63, 2001:4860:4802:34::63, 2001:4860:4802:36::63, 2001:4860:4802:38::63, UDP_-_EDNS0_4096_D_KN)
  • google.com.mm/NSEC3PARAM: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (216.239.32.99, 216.239.34.99, 216.239.36.99, 216.239.38.99, 2001:4860:4802:32::63, 2001:4860:4802:34::63, 2001:4860:4802:36::63, 2001:4860:4802:38::63, UDP_-_EDNS0_4096_D_KN)
  • google.com.mm/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (216.239.32.99, 216.239.34.99, 216.239.36.99, 216.239.38.99, 2001:4860:4802:32::63, 2001:4860:4802:34::63, 2001:4860:4802:36::63, 2001:4860:4802:38::63, TCP_-_EDNS0_4096_D_N)
  • google.com.mm/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (216.239.32.99, 216.239.34.99, 216.239.36.99, 216.239.38.99, 2001:4860:4802:32::63, 2001:4860:4802:34::63, 2001:4860:4802:36::63, 2001:4860:4802:38::63, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • google.com.mm/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (216.239.32.99, 216.239.34.99, 216.239.36.99, 216.239.38.99, 2001:4860:4802:32::63, 2001:4860:4802:34::63, 2001:4860:4802:36::63, 2001:4860:4802:38::63, UDP_-_EDNS0_4096_D_KN)
  • google.com.mm/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • google.com.mm/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • google.com.mm/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • 21gvl.rqo8i.google.com.mm/A 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.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph