baidu.com
Updated:
2023-08-29 13:53:40 UTC (453 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset 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 status
Secure (6)
- ./DNSKEY (alg 8, id 11019)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of baidu.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 4459)
- com/DS (alg 8, id 30909)
Delegation status
Insecure (1)
- com to baidu.com
Secure (1)
- . to com
Notices
Errors (2)
- baidu.com zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (240e:bf:b801:1002:0:ff:b024:26de)
- baidu.com/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (240e:bf:b801:1002:0:ff:b024:26de, TCP_-_EDNS0_4096_D_N)
Warnings (3)
- baidu.com/NS: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (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.
JavaScript is required to make the graph below interactive.
