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 (2)
  • com/SOA
  • com/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 30903)
  • NSEC3 proving non-existence of baidu.com/DS
  • com/DNSKEY (alg 13, id 19718)
  • com/DNSKEY (alg 13, id 4534)
  • com/DS (alg 13, id 19718)

Delegation statusDelegation status

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

NoticesNotices

Errors (10)
  • baidu.com zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (111.45.3.226)
  • baidu.com/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (111.45.3.226, UDP_-_EDNS0_512_D_KN)
  • baidu.com/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (111.45.3.226, UDP_-_EDNS0_512_D_KN)
  • baidu.com/MX: No response was received from the server over UDP (tried 7 times). See RFC 1035, Sec. 4.2. (111.45.3.226, UDP_-_EDNS0_4096_D)
  • baidu.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (111.45.3.226, UDP_-_NOEDNS_)
  • baidu.com/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (111.45.3.226, TCP_-_EDNS0_4096_D_N)
  • baidu.com/SOA: No response was received from the server over UDP (tried 5 times). See RFC 1035, Sec. 4.2. (111.45.3.226, UDP_-_EDNS0_512_)
  • baidu.com/SOA: No response was received from the server over UDP (tried 8 times). See RFC 1035, Sec. 4.2. (111.45.3.226, UDP_-_EDNS0_512_)
  • baidu.com/SOA: No response was received from the server over UDP (tried 9 times). See RFC 1035, Sec. 4.2. (111.45.3.226, UDP_-_EDNS0_512_)
  • baidu.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
  • baidu.com/A: No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). See RFC 6891, Sec. 6.1.4. (111.45.3.226, UDP_-_EDNS0_4096_D_KN)
  • baidu.com/SOA: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (111.45.3.226, UDP_-_EDNS0_4096_D_KN)
  • 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.
  • baidu.com/DNSKEY 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