Last updated: August 31, 2026
Favscan is a diagnostic tool that tells you which favicon files a website declares — and which of those files actually exist at the location they claim. It also checks the two root fallbacks that browsers ask for by convention (/favicon.ico and /apple-touch-icon.png).
To use it:
That's it. No account, no signup, no data is sent to any server.
Not yet. The current version is a demonstration prototype. The scanner runs entirely in your browser and shows pre-canned example data for a small set of well-known sites (github.com, wikipedia.org, stackoverflow.com, and a default/unknown-domain fallback).
Real server-side scanning — where Favscan would actually fetch your page, read its <head>, and request each declared icon — is planned but not yet built.
That's expected with the current demo. Only four domains have unique example data:
example.com — shows a missing favicon.svg and a missing apple-touch-icongithub.com — shows all icons presentwikipedia.org — shows all icons presentstackoverflow.com — shows a wrong-format icon (16×16 served as text/html)Every other domain falls back to the default example, which shows all icons as missing. Real scanning would give unique results per site.
If your domain isn't one of the four curated examples (github.com, wikipedia.org, stackoverflow.com, example.com), the demo falls back to a default result that shows every icon as missing. This is simulated data, not a real diagnosis.
It does not mean your site actually has missing favicons. Once real scanning is built, the tool will examine your actual page and give an accurate report.
It means an icon file was served with a content type or pixel dimensions that don't match what the page's <link> tag declared. For example:
type="image/png" that is served as text/html (e.g. an HTML error page instead of the icon)sizes="16×16" that actually serves a different pixel size.ico file served with the wrong MIME typeIn the current demo, the only wrong-format example is stackoverflow.com's /img/favicon-16.png which is declared as 16×16 PNG but served as text/html.
No account needed. Favscan requires no registration, no login, and no persistent user data of any kind. Each scan is independent.
Because the current prototype runs entirely in your browser, no URL you enter is transmitted to any server. Scan results are displayed in your browser only and are not stored, logged, or retained. See the Privacy Policy for details.
Yes, real scanning is planned. The plan is to build a server-side worker that fetches the actual page and icon files to produce a real diagnosis. The planned platform is Cloudflare Workers, which has known limitations — see the Known limitations section below.
There is no published release date yet. The timeline depends on the operator's priorities and resources. This is a prototype, and it has not been committed to as a funded product.
When real scanning is implemented, Favscan will only be able to scan publicly accessible URLs — the same as any web-based diagnostic tool. Sites behind a login, on a VPN, on a local network, or on localhost will not be reachable from the server.
The current client-side demo doesn't fetch any URL at all, so this limitation only applies to the planned server-side version.
Pro features (batch scanning, scan history, API access) are planned but not yet available. The Pro subscription on the Pricing page is a demonstration mockup — no real payment is taken and no purchase is created.
See the Pricing page for the planned feature set and the Terms of Service for details on billing.
Favscan is a demonstration prototype. The following limitations are known and honest:
Email support is not yet available. This service does not have a mailbox or a support address configured. We are not reachable by email today.
If you have encountered a technical issue with the demonstration tool, please review the FAQs above first — they cover the most common questions about how the prototype works and what it does and doesn't do yet.
A contact route is on the operator's list of requirements, and this page will be updated the moment one exists.