Help Centre

Last updated: August 30, 2026

Getting started

Icontest checks which favicons and site icons actually exist on any public URL. You paste a URL, the tool fetches the page, finds every icon declared in the <head>, and requests each one to report what comes back. It also checks the two paths browsers request by convention even when no icon is declared: /favicon.ico and /apple-touch-icon.png at the host root.

1 Go to the app page. No account, no sign-up, no payment card needed — the tool is currently free to try.
2 Paste any public URL. A landing site, web app, documentation domain — as long as it's reachable from the internet.
3 Click "Scan URL". The tool fetches the page, extracts every icon declaration, and requests each icon URL.
4 Read the results. A table shows each icon's URL, HTTP status, content-type, and real pixel dimensions. Below that, summaries tell you what a browser tab, an iOS home screen, and a search result would each end up using, and which of those three has nothing to use.

That's it. There is no step five. Each scan is self-contained — nothing is saved, nothing is emailed, nothing is monitored over time. If you need a record of the results, copy the table.

Frequently asked questions

1. My favicon shows in the browser tab but Icontest says it's missing — why?

This usually means the page declares one icon but the browser uses a different one. Browsers have fallback behaviour:

If the declared icon exists but returns a 404, the browser falls back to /favicon.ico at the root — even if the page never declared it.
If neither exists, the browser may still show a tab icon from the cache (previous visit).
Icontest reports what's actually on the wire right now — it does not show a cached icon that used to exist.

Check the "Root fallbacks" section of your scan results. If /favicon.ico at the host root returns 200, that's likely what the browser is using, even if your declared icon is missing.

2. Why does my favicon appear on some pages of my site but not others?

Each page can declare its own icons independently. Common causes:

Some pages have the icon declaration in the <head> and others don't.
A template or CMS might inject different icon paths for different sections (e.g., a blog subdirectory may use relative paths that resolve differently).
Root fallback (/favicon.ico) is the last resort — if a page doesn't declare any icon and the root path is missing, the browser shows a blank tab.

Scan the specific pages that show a blank tab — compare their declared icons against one that works. The diff tells you exactly which file is missing.

3. My apple-touch-icon is missing — can you create one?

No. Icontest is a diagnostic tool — it reports what's present and what's missing, but it does not generate or design icons.

To fix a missing apple-touch-icon:

Create a PNG image (we recommend 180×180 pixels for modern iOS devices, though the tool supports any size).
Place it at the path your page declares in <link rel="apple-touch-icon">, or at /apple-touch-icon.png at the root (the path iOS checks by convention even when undeclared).
Re-scan after publishing — the tool will confirm the icon is now returning HTTP 200 with the correct dimensions.

4. The tool says a host is "unreachable" — what does that mean?

Icontest runs on Cloudflare Workers. Cloudflare Workers cannot reach hosts that are also behind Cloudflare. When the target server is proxied through Cloudflare, the Workers runtime is blocked from connecting — this is a platform limitation, not a sign that the target server is down or misconfigured.

If your site is behind Cloudflare and Icontest reports it as unreachable, check the site from your own browser or a non-Cloudflare diagnostic tool. The icon is likely serving correctly to real visitors.

This is a known limitation. There is currently no workaround from within Icontest.

5. Are my scanned URLs or results stored anywhere?

No. Icontest is a stateless, single-shot tool. Here is the full data lifecycle for a scan:

Your URL is sent to the API endpoint via HTTP POST.
The API fetches the page and every declared icon URL.
Results are returned in the HTTP response and displayed in your browser.
The URL, page content, and icon content are not stored, logged, or retained after the response is delivered.

There is no database, no session store, no analytics script, and no cookie. See the privacy policy for full details.

6. How do I pay? I clicked "Subscribe" on the pricing page but nothing happened.

The payment system is not connected yet. The checkout form on the pricing page is a demonstration of what the flow will look like — no real payment is taken, and no subscription is created.

The tool is currently free to try. Once a payment processor is connected, the pricing page will be updated with real payment handling, and this FAQ will be updated accordingly.

Known limitations

Icontest is a small, honest tool. These are the features it does not yet have, and the platform constraints it operates under:

Area	Status	Note
Payment processing	Not connected	The checkout form is a demo. No real payments are taken. The tool is free until a processor is connected.
Email support	Not reachable	There is no mailbox or contact email set up yet. See "Contact" below.
Email notifications	Not available	The tool does not email you results, alerts, receipts, or reminders. Results appear on the page or not at all.
Account system	Not available	No sign-up, no login, no saved history. Each scan is independent. Copy your results if you need a record.
Monitoring / scheduling	Not available	Icontest checks one URL at the moment you request it. It does not re-check URLs over time or alert you when they change.
Image generation	Not available	The tool does not create, suggest, or design icons. It only reports what is already served.
Cloudflare Workers limitation	Platform constraint	Hosts behind Cloudflare report as unreachable. This affects all tools running on the Workers runtime, not just Icontest.
No legal entity	Not registered	Until the operator registers an entity, there is no jurisdiction, no governing law, and no binding contract. The terms and privacy policy are statements of intent.

Contact

No contact route has been established yet. The operator has not registered a legal entity or provided a means of contact by email or phone. There is no mailbox on any domain in this fleet — any address you see elsewhere on this site is a placeholder, not a working route.

If you need help with a specific scan result, the best next step is to review the FAQs above and re-read the scan output carefully — the tool shows you exactly which HTTP status codes, content types, and pixel dimensions each icon returned.

For issues that cannot be resolved from this page — payment-related questions once billing is active, legal inquiries, or partnership requests — the owner needs to set up a contact route. This requirement has been recorded but not yet actioned.