Help Centre
Getting started, troubleshooting, and known limitations for Favlint.
Getting started
Go to the App page, enter the full URL of the site you want to check (including https://), and click Scan. Favlint will:
- Fetch the page's HTML
- Read every icon declared in the
<head> - Request each icon file (plus the conventional root paths
/favicon.icoand/apple-touch-icon.png) - Report which are present, misconfigured, or missing
Note: The scanning backend is not yet deployed. The app page currently shows a preview of the planned interface — automated icon checks are not available yet. See Known limitations.
Frequently asked questions
The scanning backend that checks icon files is still under development and has not been deployed. The App page shows the planned user interface — the form, the loading skeleton, and the results table — but the backend API endpoint (/api/check) does not exist yet. Clicking Scan currently produces a network error because there is no server to handle the request.
We will announce when scanning is live. No sign-up or email is needed to use the tool when it ships.
This is the exact problem Favlint is built to solve. "Declared but missing" usually means one of:
- The path in
<link href="...">points to a file that doesn't exist on the server (typo, wrong relative path, missing file). - The file exists but the server returns a 404 or 403 for that specific path.
- The file exists but the Content-Type header says something unexpected, causing the browser (or Favlint) to treat it as unavailable.
Once the scanning backend is live, Favlint will fetch each icon individually and report the exact HTTP status code, so you know whether it's a missing file, a server config issue, or a format problem.
Favlint is built on Cloudflare Workers. A Cloudflare Worker cannot open a socket back into Cloudflare's own network — it would be connecting to itself. This means any site proxied through Cloudflare (identified by its IP range or the presence of a Cloudflare edge certificate) will appear unreachable when Favlint tries to fetch its icons.
This is a platform limitation of Cloudflare Workers, not a bug with the scan. We cannot work around it on the current infrastructure. If your site is behind Cloudflare, you can check your icons by looking at the raw file paths directly or by testing on a non-Cloudflare staging environment.
There is no single answer — different consumers need different formats. Here is the modern minimum set:
- Browser tab:
/favicon.ico(ICO format, 32x32 or multi-resolution 16x16 + 32x32). Also declare a<link rel="icon" type="image/svg+xml" href="favicon.svg">for modern browsers that support SVG favicons. - iOS home screen:
/apple-touch-icon.png(PNG, 180x180). Declared via<link rel="apple-touch-icon" href="/apple-touch-icon.png">in the<head>. - Google Search results: Google uses the favicon.ico (or declared icon) for the search result snippet. A 48x48 PNG or SVG works best.
- Android / Chrome:
<link rel="icon" type="image/png" sizes="192x192" href="/android-chrome-192x192.png">and a<link rel="manifest" href="/site.webmanifest">.
Favlint checks all of these automatically once the scanning backend is live.
No. Favlint does not create user accounts, set cookies, or store any data. When you submit a URL:
- The URL is used only to fetch the page and its icons.
- The scan runs entirely in memory and is discarded after the response is sent.
- No scan history, no database, no cache of results.
Standard ephemeral web server logs (timestamp, request path, approximate IP) are retained briefly for operational purposes (rate limiting, abuse prevention) and are not retained beyond 7 days. See the Privacy policy for full details.
Not yet. The Pro subscription selector and checkout interface on the Pricing page are a demonstration only. No payment processing has been connected — no card details are collected, no billing information is stored, and no Pro membership is activated through this interface.
Until a payment processor is integrated, the Free tier is the only available plan. All scan functionality (including the planned Pro features) will be explained on the pricing page when they ship. We will not charge anyone without clear notice.
Not yet. Favlint is operated by an individual who has not established a legal entity, registered address, or jurisdiction. The Terms of service and Privacy policy documents describe what happens in practice today, but binding commitments require a legal entity. The operator plans to establish one and will update these pages accordingly.
Known limitations
-
Scanning backend not deployed
The core favicon-checking engine does not exist yet. The App page shows a preview of the interface (form, loading skeleton, results table) but the API has not been built. Entering a URL and clicking Scan produces a network error.
Under development
-
Payment processing not connected
The Pro subscription interface on the Pricing page is a demo only. No payment can be accepted, no Pro accounts can be created. The checkout form uses pre-filled demo values and the "Complete subscription" button shows a local success message but sends no data anywhere.
Demo only
-
Cloudflare-hosted sites unreachable
Because Favlint runs on Cloudflare Workers, it cannot connect to sites proxied through Cloudflare. The Worker sees itself and returns a network error. This is a platform limitation.
Platform limitation
-
No user accounts or persistent storage
There is no database, no login, no subscription system. Each scan (when live) will be a single ephemeral check with no history.
By design
-
No legal entity yet
The service has no registered company, address, or jurisdiction. Terms and privacy documents reflect current practices but are not legally binding commitments.
Pending
-
No email or contact system
There is no support mailbox, contact form, or automated notification system. See "How to contact us" below.
Pending
How to contact us
There is no support mailbox or contact form available at this time. The service is operated by an individual who has not yet established a company or a dedicated support channel.
Since Favlint does not store submitted URLs, create accounts, or retain scan results, there is no account-specific data to recover or troubleshoot. Most questions about how the tool works are answered on this page or in the Privacy policy.
If you need to report an issue or have a specific request for the operator, please note that no reply can be guaranteed at this time. A proper support channel will be established when the legal entity is formed and the scanning service is live.
A support contact method is a recorded requirement — see the site owner's needs list.