baidu.com | DNSViz

baidu.com

Updated: 2022-12-08 00:59:31 UTC (719 days ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

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 (1)

./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (192.112.36.4, UDP_-_EDNS0_512_D_KN)

Warnings (2)

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.

DNSKEY legend

Full legend

	SEP bit set
	Revoke bit set
	Trust anchor

See also

DNSSEC Debugger by Verisign Labs.

Download: png | svg

Warning

JavaScript is required to make the graph below interactive.

DNSSEC authentication graph