linkedin.com | DNSViz

linkedin.com

Updated: 2023-03-20 04:37:00 UTC (618 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 (3)

com/SOA
com/SOA
com/SOA

DNSKEY/DS/NSEC status

Secure (6)

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

Delegation status

Insecure (1)

com to linkedin.com

Secure (1)

. to com

Notices

Warnings (1)

linkedin.com/TXT: 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. (2600:2000:2210::43, 2600:2000:2220::43, 2600:2000:2230::43, 2600:2000:2240::43, UDP_-_EDNS0_4096_D_KN)

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