baidu.com
Updated:
2022-10-26 13:37:18 UTC (762 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 18733)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of baidu.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 53929)
- com/DS (alg 8, id 30909)
Delegation status
Insecure (1)
- com to baidu.com
Secure (1)
- . to com
Notices
Errors (3)
- baidu.com/MX: There was an error communicating with the server over UDP (EAGAIN). See RFC 1035, Sec. 4.2. (111.45.3.226, UDP_-_EDNS0_4096_D_KN)
- baidu.com/NS: There was an error communicating with the server over UDP (EAGAIN). See RFC 1035, Sec. 4.2. (111.45.3.226, UDP_-_EDNS0_4096_D_KN)
- baidu.com/TXT: There was an error communicating with the server over UDP (EAGAIN). See RFC 1035, Sec. 4.2. (111.45.3.226, UDP_-_EDNS0_4096_D_KN)
Warnings (3)
- 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.
JavaScript is required to make the graph below interactive.
