NSEC3 proving non-existence of nic.mx/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 nic.mx/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
mx/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (2001:1201:10::1, UDP_-_EDNS0_4096_D_KN)
nic.mx zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:1250:b000::1, 2001:1250:c000::1)
nic.mx/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:1250:b000::1, 2001:1250:c000::1, UDP_-_NOEDNS_)
nic.mx/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:1250:b000::1, 2001:1250:c000::1, UDP_-_NOEDNS_)
nic.mx/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (2001:1201:10::1, UDP_-_EDNS0_4096_D_KN)
nic.mx/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (16)
. to mx: Authoritative AAAA records exist for e.mx-ns.mx, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
. to mx: Authoritative AAAA records exist for i.mx-ns.mx, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
. to mx: Authoritative AAAA records exist for o.mx-ns.mx, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
. to mx: Authoritative AAAA records exist for x.mx-ns.mx, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
NSEC3 proving non-existence of nic.mx/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of nic.mx/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
nic.mx/AAAA: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (2001:1250:a000::1, UDP_-_EDNS0_4096_D_KN)
nic.mx/MX: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (2001:1250:a000::1, UDP_-_EDNS0_4096_D_KN)
nic.mx/SOA: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (2001:1250:a000::1, UDP_-_EDNS0_4096_D_KN)
nic.mx/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. (2001:1250:a000::1, UDP_-_EDNS0_4096_D_KN)
nic.mx/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
nic.mx/CDNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
nic.mx/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
icxvw.0kr3p.nic.mx/A has warnings; select the "Denial of existence" DNSSEC option to see them.
nic.mx/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
nic.mx/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.