How the favicon checker works
- Enter a URL. The tool tries to fetch the page's HTML
<head>directly from your browser. - If the site blocks cross-origin requests (most do — see below), the checker retries through a public CORS proxy.
- If both attempts fail, paste the contents of the page's
<head>into the textarea and press Analyze HTML. Right-click → View Source in any browser, copy the<head>section. - The report lists every favicon link tag found, plus the standard sizes that are missing.
About CORS and public sites
Browsers refuse to read the body of cross-origin requests unless the destination server returns an Access-Control-Allow-Origin header. Most sites do not set that header on their root document, so a direct fetch from this page will be blocked. The CORS proxy fallback is courtesy of allorigins.win and may be rate-limited or down. The most reliable workflow is the paste-HTML fallback.
What gets checked
favicon.icoreference- PNG
16x16and32x32 apple-touch-icon(180×180)- Android Chrome
192x192and512x512 manifest.jsonlinkbrowserconfig.xmlreferencetheme-colormeta tag
FAQ
Why do you not just download the favicon files? The browser does not allow scripts to read the bytes of cross-origin resources. We can only see the link tags.
What does "source: pasted" mean? The report was generated from HTML you pasted in, not from a live fetch.
Are the proxy results accurate? Yes — but they may be cached for up to a minute by the proxy provider.