View on GitHub

DNSViz: A DNS visualization tool

nic.mx

Updated: 2024-12-16 18:49:11 UTC (4 months ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (6)
  • nic.mx/A
  • nic.mx/AAAA
  • nic.mx/MX
  • nic.mx/NS
  • nic.mx/SOA
  • nic.mx/TXT
Secure (2)
  • mx/SOA
  • mx/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 61050)
  • NSEC3 proving non-existence of nic.mx/DS
  • mx/DNSKEY (alg 8, id 55120)
  • mx/DNSKEY (alg 8, id 62752)
  • mx/DS (alg 8, id 62752)

Delegation statusDelegation status

Insecure (1)
  • mx to nic.mx
Secure (1)
  • . to mx

NoticesNotices

Errors (37)
  • 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) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (2001:1250:a000::1, 2001:1250:c000::1)
  • nic.mx zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (2001:1250:a000::1, 2001:1250:b000::1, 2001:1250:c000::1)
  • nic.mx zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (2001:1250:b000::1)
  • nic.mx/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:1250:a000::1, UDP_-_NOEDNS_)
  • nic.mx/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2001:1250:b000::1, 2001:1250:c000::1, UDP_-_NOEDNS_)
  • nic.mx/AAAA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:1250:b000::1, UDP_-_NOEDNS_)
  • nic.mx/AAAA: No response was received from the server over UDP (tried 13 times). See RFC 1035, Sec. 4.2. (2001:1250:a000::1, UDP_-_NOEDNS_)
  • nic.mx/AAAA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2001:1250:c000::1, UDP_-_NOEDNS_)
  • nic.mx/DNSKEY: No response was received from the server over UDP (tried 17 times). See RFC 1035, Sec. 4.2. (2001:1250:c000::1, UDP_-_NOEDNS_)
  • nic.mx/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2001:1250:a000::1, UDP_-_EDNS0_512_D_KN)
  • nic.mx/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2001:1250:a000::1, 2001:1250:b000::1, 2001:1250:c000::1, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • nic.mx/MX: No response was received from the server over UDP (tried 13 times). See RFC 1035, Sec. 4.2. (2001:1250:a000::1, UDP_-_NOEDNS_)
  • nic.mx/MX: No response was received from the server over UDP (tried 17 times). See RFC 1035, Sec. 4.2. (2001:1250:b000::1, UDP_-_NOEDNS_)
  • nic.mx/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2001:1250:a000::1, 2001:1250:c000::1, UDP_-_EDNS0_512_D_KN)
  • nic.mx/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2001:1250:b000::1, 2001:1250:c000::1, UDP_-_EDNS0_512_D_KN, 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:a000::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/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2001:1250:b000::1, 2001:1250:c000::1, UDP_-_NOEDNS_)
  • nic.mx/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (2001:1250:b000::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. (2001:1250:c000::1, TCP_-_NOEDNS_)
  • nic.mx/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:1250:b000::1, UDP_-_NOEDNS_)
  • nic.mx/SOA: No response was received from the server over UDP (tried 13 times). See RFC 1035, Sec. 4.2. (2001:1250:a000::1, 2001:1250:b000::1, 2001:1250:c000::1, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • nic.mx/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2001:1250:a000::1, 2001:1250:b000::1, 2001:1250:c000::1, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • nic.mx/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2001:1250:a000::1, TCP_-_NOEDNS_)
  • nic.mx/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:1250:a000::1, UDP_-_NOEDNS_)
  • nic.mx/TXT: No response was received from the server over UDP (tried 13 times). See RFC 1035, Sec. 4.2. (2001:1250:b000::1, UDP_-_NOEDNS_)
  • nic.mx/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2001:1250:c000::1, UDP_-_NOEDNS_)
  • nic.mx/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
  • 9riy4.uybs1.nic.mx/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • nic.mx/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • nic.mx/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • nic.mx/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • nic.mx/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • nic.mx/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
  • 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/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