LinkedInBot — IP ranges, ASN verification and the Microsoft / AI context
by shop owners for shop owners.
The IP ranges of the LinkedIn crawler (LinkedInBot) to allowlist or block — plus why LinkedIn publishes no official IP list, how to verify by ASN (AS14413 + AS13443) and reverse DNS against *.fwd.linkedin.com, and what Microsoft ownership means for AI training.
LinkedIn runs the LinkedInBot for link previews when posting on LinkedIn. Like Meta and X, LinkedIn publishes no official IP list — verification is by ASN plus reverse DNS against *.fwd.linkedin.com. Here are the aggregated ranges (part of our PARC Security feed), how they were derived, and the Microsoft / AI context.
linkedin.json — view feed LinkedIn Post Inspector →
The ranges
A total of 51 prefixes (29 IPv4 + 22 IPv6), aggregated from two LinkedIn-owned ASNs. The full list is in the feed; derived from ASN ownership (no official LinkedIn list) and validated against active crawler IPs via FCrDNS.
No official IP list — verification by ASN
LinkedIn publishes no crawler IP list and documents the bot only sparsely (the official tool is the Post Inspector, which shows how LinkedInBot renders a URL). The reliable check is therefore the combination of ASN membership and FCrDNS against *.fwd.linkedin.com. For setups without ASN block support (e.g. SafeLine WAF), this feed provides the flat prefix list.
ASN constellation
- AS14413 — LinkedIn Corporation: part of the LinkedIn backbone.
- AS13443 — LinkedIn Corporation: the larger block of LinkedIn prefixes.
Microsoft acquired LinkedIn in 2016, but the network infrastructure still runs under LinkedIn’s own ASNs — not under Microsoft ASNs. Both ASNs are aggregated in the feed.
Verification: PTR pattern
{ip-with-dashes}.fwd.linkedin.com— for active crawler IPs, bidirectionally FCrDNS-verifiable (e.g.108-174-7-1.fwd.linkedin.com).- Backend IPs (newer EU subnets, internal workers) are often PTR-empty — operational addresses with no public branding.
As with Meta and X, the ASN approach is the reliable basis in the feed, not a pure FCrDNS filter.
Microsoft & AI context
LinkedIn has been a Microsoft subsidiary since 2016. The LinkedInBot officially serves only to generate link previews. Note, however, that LinkedIn / Microsoft content potentially feeds into AI training data (the Microsoft–OpenAI context). There is no dedicated, officially documented AI crawler user-agent for LinkedIn — if you want to exclude AI-training scraping on principle, block the LinkedIn ASNs by IP; if you only want to prevent link previews, you can block LinkedInBot by user-agent (which then costs you the preview when sharing).