View on GitHub

DNSViz: A DNS visualization tool

mx

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

RRset statusRRset status

Bogus (5)
  • mx/NS
  • mx/NSEC3PARAM
  • mx/NSEC3PARAM
  • mx/SOA
  • mx/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (2)
  • mx/DNSKEY (alg 8, id 10935)
  • mx/DNSKEY (alg 8, id 61885)
Secure (4)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • ./DNSKEY (alg 8, id 951)
  • mx/DS (alg 8, id 61885)

Delegation statusDelegation status

Bogus (1)
  • . to mx

NoticesNotices

Errors (13)
  • . to mx: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (189.201.244.1, 192.100.224.1, 201.131.252.1, 207.248.68.1, 2001:1258::1, 2001:13c7:7000::1, UDP_-_EDNS0_4096_D_KN)
  • RRSIG mx/DNSKEY alg 8, id 61885: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG mx/DNSKEY alg 8, id 61885: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • 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/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • mx/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • b7wkv2mr9a.mx/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (2)
  • b7wkv2mr9a.mx/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • mx/CNAME 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