Link Header Inspect
Analyze Link headers in your browser to detect wrong attributes or unintended values. No input is sent to a server.
Status
Runs in your browser. No input is sent to a server.
How to use
Paste Link headers and click “Parse” to split URI and attributes.
Notes (this tool)
- Accepts both full `Link:` lines and raw Link values.
About this page
What does this tool do?
Split Link header values and list `<URI>` with parameters such as `rel`, `as`, `type`, and `crossorigin`.
Even with multiple Link entries in one response, you can inspect them while preserving order.
Typical use cases
- Check preload `as` mismatches (script/style/font etc.)
- Validate canonical/next/prev delivery through HTTP headers
- Verify Link headers are not dropped or modified by CDN layers
Syntax basics
- Single entry format: `<https://example.com/app.js>; rel=preload; as=script`
- Multiple entries are comma-separated.
- `rel` is the key semantic attribute.
Recommended workflow
- Paste raw Link headers from response
- Check whether rel values match expected link relationships
- For preload, validate as/type/crossorigin consistency
Common pitfalls
- Missing `as` on preload and losing expected effect
- Mismatch between HTTP canonical and HTML canonical
- Missing crossorigin on font preload causing double fetches
What this tool does
- Parse Link values into URI + attributes
- Summarize rel values
- Copyable parsed output
Operational notes
- Final behavior depends on browser/CDN implementation; verify with network traces.
- For SEO canonical use-cases, avoid inconsistent dual management with HTML tags.
Referenced specs
- RFC 8288: Web Linking
- MDN: Link header
FAQ
Is it equivalent to HTML `<link>` tags?
Semantics are similar for many rel values, but delivery path and scope differ, so verify consistency between header and HTML.
Can I paste multiple Link header lines?
Yes. You can paste separate lines or a comma-joined value.
References
Next to view (diagnostic order)
These links are generated from site_map rules in recommended diagnostic order.
- Response Headers Parser — Parse response headers into structured data
- HTTP Status Inspect — Analyze HTTP status codes and suggest handling direction
- Location Inspect — Parse Location header and split destination URL
- Redirect Chain Inspect — Analyze redirect chains to detect loops and waste hops
- Content-Type Inspect — Parse Content-Type and inspect MIME/charset
- How to choose response header tools — Map Retry-After, Server-Timing, Link, Content-Type, and nosniff checks by symptom
- Set-Cookie Inspect — Parse Set-Cookie attributes and review delivery policy
- Server-Timing Inspect — Parse Server-Timing and inspect latency metrics
Same-theme links
Response Header Diagnostics
Step through raw headers to inspect Retry-After, Server-Timing, Link, and Content-Type
- HTTP Header Parser — Parse raw headers into structured lists
- Response Headers Parser — Parse response headers into structured data
- Set-Cookie Inspect — Parse Set-Cookie attributes and review delivery policy
- Cookie Domain/Path Matcher — Evaluate cookie send conditions by Domain/Path/Secure
- SameSite Cookie Simulator — Simulate cookie send behavior from SameSite and request context
- Set-Cookie Conflict Checker — Detect same-name cookie conflicts and overwrite risks
- Cookie Size Checker — Estimate Cookie header size and check limit risks
- Retry-After Inspect — Parse Retry-After and inspect retry wait behavior
- Server-Timing Inspect — Parse Server-Timing and inspect latency metrics
- Content-Type Inspect — Parse Content-Type and inspect MIME/charset
- X-Content-Type-Options Inspect — Parse X-Content-Type-Options and validate nosniff
- HTTP Status Inspect — Analyze HTTP status codes and suggest handling direction
Example
Link: <https://cdn.example.com/app.js>; rel=preload; as=script
Link: <https://example.com/>; rel=canonical