View on GitHub

DNSViz: A DNS visualization tool

mach2plus.com

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

RRset statusRRset status

Bogus (5)
  • mach2plus.com/A
  • mach2plus.com/MX
  • mach2plus.com/NS
  • mach2plus.com/SOA
  • mach2plus.com/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46780)
  • com/DNSKEY (alg 13, id 19718)
  • com/DNSKEY (alg 13, id 46171)
  • com/DS (alg 13, id 19718)
  • mach2plus.com/DS (alg 8, id 19277)
Non_existent (2)
  • com/DNSKEY (alg 8, id 63246)
  • mach2plus.com/DNSKEY (alg 8, id 19277)

Delegation statusDelegation status

Bogus (1)
  • com to mach2plus.com
Secure (1)
  • . to com

NoticesNotices

Errors (19)
  • com to mach2plus.com: 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.
  • mach2plus.com zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (172.64.53.117)
  • mach2plus.com/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (172.64.53.117, UDP_-_EDNS0_4096_D_KN)
  • mach2plus.com/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (172.64.52.73, UDP_-_EDNS0_4096_D_KN)
  • mach2plus.com/AAAA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (172.64.52.73, 172.64.53.117, UDP_-_EDNS0_4096_D_KN)
  • mach2plus.com/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (172.64.52.73, 172.64.53.117, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • mach2plus.com/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (172.64.52.73, 172.64.53.117, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • mach2plus.com/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (172.64.52.73, UDP_-_EDNS0_512_D_KN)
  • mach2plus.com/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (172.64.53.117, UDP_-_EDNS0_4096_D_KN)
  • mach2plus.com/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (172.64.52.73, UDP_-_EDNS0_4096_D_KN)
  • mach2plus.com/NSEC3PARAM: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (172.64.52.73, 172.64.53.117, UDP_-_EDNS0_4096_D_KN)
  • mach2plus.com/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (172.64.52.73, 172.64.53.117, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • mach2plus.com/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (172.64.52.73, 172.64.53.117, UDP_-_EDNS0_4096_D_KN)
  • mach2plus.com/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (172.64.53.117, TCP_-_EDNS0_4096_D_N)
  • mach2plus.com/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (172.64.53.117, UDP_-_EDNS0_4096_D_KN)
  • mach2plus.com/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (172.64.52.73, UDP_-_EDNS0_4096_D_KN)
  • ix21bn3pqd.mach2plus.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • mach2plus.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • mach2plus.com/CNAME has errors; 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