linkedin.com | DNSViz

linkedin.com

Updated: 2021-09-29 06:54:23 UTC (1153 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 (7)

linkedin.com/A
linkedin.com/AAAA
linkedin.com/MX
linkedin.com/NS
linkedin.com/SOA
linkedin.com/SOA
linkedin.com/TXT

Secure (1)

com/SOA

DNSKEY/DS/NSEC status

Secure (7)

./DNSKEY (alg 8, id 14748)
./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 26838)
NSEC3 proving non-existence of linkedin.com/DS
com/DNSKEY (alg 8, id 30909)
com/DNSKEY (alg 8, id 39343)
com/DS (alg 8, id 30909)

Delegation status

Insecure (1)

com to linkedin.com

Secure (1)

. to com

Notices

Errors (1)

linkedin.com/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (204.13.250.43, 204.13.251.43, 208.78.70.43, 208.78.71.43, 2001:500:90:1::43, 2001:500:94:1::43, UDP_-_EDNS0_512_)

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