nic.mx

Updated: 2022-09-21 05:25:04 UTC (738 days ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 18733)
./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 20826)
NSEC3 proving non-existence of nic.mx/DS
mx/DNSKEY (alg 8, id 19441)
mx/DNSKEY (alg 8, id 61885)
mx/DS (alg 8, id 61885)

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: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (200.23.1.1, UDP_-_EDNS0_512_D_KN)
nic.mx zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (200.23.1.1, 200.94.176.1)
nic.mx/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (200.23.1.1, TCP_-_EDNS0_4096_D_N)
nic.mx/SOA: No response was received from the server over TCP (tried 5 times). See RFC 1035, Sec. 4.2. (200.94.176.1, TCP_-_EDNS0_4096_D_N)
nic.mx/DS has errors; select the "Denial of existence" DNSSEC option to see them.

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/A: 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. (200.94.176.1, UDP_-_EDNS0_4096_D_KN)
nic.mx/NSEC3PARAM 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.