Favidetect

Paste a URL. Favidetect reads the page's <head>, collects every icon it declares — favicon.ico, apple-touch-icon, every <link rel="icon"> with its sizes and type — then requests each one and reports what came back.

It also checks the two root fallbacks that clients request by convention: /favicon.ico and /apple-touch-icon.png — because a page can declare everything correctly and still show a blank tab when the root file 404s.

Output: a table of what a browser, a search result, and an iOS home-screen bookmark would each end up using, and which of those three has nothing to use.

Enter a URL in the app to run a live check.


How it works

1
Fetch the page
Favidetect reads the HTML of the URL you provide, parsing every <link> tag in <head> that declares an icon.
2
Check every declaration
Each icon URL is fetched independently. Status, format, and pixel dimensions are extracted from the response body by inspecting the binary header — no external libraries.
3
Add the root fallbacks
/favicon.ico and /apple-touch-icon.png are checked even if the page does not declare them, because browsers and devices request them by convention.
4
Show the verdict
A table of all icons with per-file status, format, size, and type-match information. A summary shows which usage slots (browser tab, search result, iOS home screen) are covered and which are not.

Sample output

A real result for a well-configured site looks like this:

Rel Path Status Format Size
icon /favicon.ico Present ICO 32×32
icon /favicon-16x16.png Present PNG 16×16
icon /favicon-32x32.png Present PNG 32×32
apple-touch-icon /apple-touch-icon.png Present PNG 180×180
icon (root) /favicon.ico Missing
Browser tab
✓ Has icon
Search result
✓ Has icon
iOS home screen
✗ No icon

Check your site now

No registration. No email. Paste a URL and get a complete diagnostic table.