Your site's icons: declared, conventional, and matched to three consumers
Paste a URL. Iconscan reads every icon declaration in the page, requests each file, and tells you what came back — present with real dimensions, wrong format, or missing entirely.
Scan a siteHow it works
- You provide a URL. Any public web page that declares icons in its
<head>. - Iconscan fetches the page and collects every icon entry:
<link rel="icon">,apple-touch-icon, manifest icons, and more. - Each icon is checked individually. The tool fetches the file, detects its actual format from magic bytes, and parses its pixel dimensions from binary headers.
- Two conventional paths are also tested.
/favicon.icoand/apple-touch-icon.pngat the site root — paths browsers request without being told. - You get a verdict. A table of every icon and its status, plus a summary of what three consumers (browser tab, Google search, iOS home-screen) would each end up using.
What it checks
Declared icons
Every <link rel="icon">, shortcut icon, apple-touch-icon, mask-icon and manifest icon declared in the page.
Conventional root paths
/favicon.ico and /apple-touch-icon.png — files browsers request by convention even when not declared.
Actual vs. declared
Magic-byte format detection, real pixel dimensions from binary headers, and whether the declared type matches what was served.
Consumer summary
Which icon each of three consumers would actually use: browser tab, Google Search result, and iOS home-screen bookmark.
example.com, cloudflare.com). Those hosts will report as unreachable. The page HTML itself can be fetched (HTTP fetch succeeds), but individual icon fetches to Cloudflare-fronted origins may fail.
Who this is for
Someone whose icon is missing in one place (Google search results, iOS home screen) and fine in another (browser tab), who wants to know which file is absent — rather than being told to “clear the cache.”
<link rel="icon"> or /favicon.icoapple-touch-icon or /apple-touch-icon.png