View on GitHub

DNSViz: A DNS visualization tool

baidu.com

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

RRset statusRRset status

Insecure (5)
  • baidu.com/A
  • baidu.com/MX
  • baidu.com/NS
  • baidu.com/SOA
  • baidu.com/TXT
Secure (1)
  • com/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 20826)
  • NSEC3 proving non-existence of baidu.com/DS
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 32298)
  • com/DS (alg 8, id 30909)

Delegation statusDelegation status

Insecure (1)
  • com to baidu.com
Secure (1)
  • . to com

NoticesNotices

Warnings (4)
  • com to baidu.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): dns.baidu.com See RFC 1034, Sec. 4.2.2.
  • com to baidu.com: The following NS name(s) were found in the delegation NS RRset (i.e., in the com zone), but not in the authoritative NS RRset: ns1.baidu.com See RFC 1034, Sec. 4.2.2.
  • com to baidu.com: The glue address(es) for ns3.baidu.com (112.80.248.64) differed from its authoritative address(es) (36.152.45.193, 112.80.248.64). See RFC 1034, Sec. 4.2.2.
  • com to baidu.com: The glue address(es) for ns4.baidu.com (14.215.178.80) differed from its authoritative address(es) (14.215.178.80, 111.45.3.226). See RFC 1034, Sec. 4.2.2.

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