mx
Updated:
2023-04-04 18:06:07 UTC (597 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (3)
- mx/NS
- mx/NSEC3PARAM
- mx/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- ./DNSKEY (alg 8, id 951)
- mx/DNSKEY (alg 8, id 10935)
- mx/DNSKEY (alg 8, id 61885)
- mx/DS (alg 8, id 61885)
Delegation status
Secure (1)
- . to mx
Notices
Errors (10)
- mx zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (200.23.1.1, 200.94.176.1)
- mx zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (200.23.1.1, 200.94.176.1)
- mx/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (200.23.1.1, 200.94.176.1, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
- mx/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (200.23.1.1, 200.94.176.1, UDP_-_NOEDNS_)
- mx/NSEC3PARAM: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (200.23.1.1, 200.94.176.1, UDP_-_NOEDNS_)
- mx/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (200.23.1.1, 200.94.176.1, TCP_-_NOEDNS_)
- mx/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (200.23.1.1, 200.94.176.1, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
- mx/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- mx/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- 6k9rfgtbam.mx/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (2)
- mx/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- 6k9rfgtbam.mx/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
