View on GitHub

DNSViz: A DNS visualization tool

infoblox.com

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

RRset statusRRset status

Secure (7)
  • infoblox.com/A
  • infoblox.com/AAAA
  • infoblox.com/MX
  • infoblox.com/NS
  • infoblox.com/NSEC3PARAM
  • infoblox.com/SOA
  • infoblox.com/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (14)
  • ./DNSKEY (alg 8, id 11019)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 46551)
  • com/DS (alg 8, id 30909)
  • infoblox.com/DNSKEY (alg 8, id 2475)
  • infoblox.com/DNSKEY (alg 8, id 36172)
  • infoblox.com/DNSKEY (alg 8, id 3870)
  • infoblox.com/DNSKEY (alg 8, id 40885)
  • infoblox.com/DS (alg 8, id 36172)
  • infoblox.com/DS (alg 8, id 36172)
  • infoblox.com/DS (alg 8, id 40885)
  • infoblox.com/DS (alg 8, id 40885)

Delegation statusDelegation status

Secure (2)
  • . to com
  • com to infoblox.com

NoticesNotices

Errors (5)
  • infoblox.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:550:2:3::183:211, 2001:550:2:3::183:212)
  • infoblox.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:550:2:3::183:211, 2001:550:2:3::183:212, UDP_-_NOEDNS_)
  • infoblox.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:550:2:3::183:211, 2001:550:2:3::183:212, UDP_-_NOEDNS_)
  • cft385oerv.infoblox.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • infoblox.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
  • com to infoblox.com: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the com zone): ns7.infoblox.com See RFC 1034, Sec. 4.2.2.
  • infoblox.com/DS (alg 8, id 36172): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • infoblox.com/DS (alg 8, id 36172): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • infoblox.com/DS (alg 8, id 36172): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • infoblox.com/DS (alg 8, id 36172): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • infoblox.com/DS (alg 8, id 40885): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • infoblox.com/DS (alg 8, id 40885): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • infoblox.com/DS (alg 8, id 40885): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • infoblox.com/DS (alg 8, id 40885): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • cft385oerv.infoblox.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • infoblox.com/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