PUBLIC ICON TRACE / 02
Trace declared favicon paths from one public website URL
Enter a public HTTP or HTTPS website URL. The checker fetches the starting page, records a bounded set of declared icon links and a linked web manifest, then reports reachability, HTTP status, detected format, declared size, and selected image dimensions.
- 1 public HTTP(S) URL
- 8 declared icon links
- 8 manifest icon entries
Where the report looks for icon references
Discovery is intentionally narrow. It provides a review of the submitted page’s directly declared favicon material, not an assertion about every icon that might exist on the domain.
Root favicon.ico
The first check targets /favicon.ico on the starting URL’s origin.
HTML link elements
Up to eight <link> elements with a rel value containing icon are read from the starting document. data: sources are ignored.
Linked web manifest
When the page declares a manifest, the report reads up to eight valid non-data icon entries from that manifest.
A small, explicit trace—not a crawl of the website
The checker only follows the submitted public URL and favicon references it discovers within fixed limits. Data URLs are ignored, duplicate icon URLs are skipped, and the report reflects the response observed during that run.
1. Request the starting document
The submitted URL must be public HTTP or HTTPS. URLs with credentials, local names, and private network targets are rejected before fetching.
2. Inspect declared icon sources
The checker tests /favicon.ico, up to eight link elements whose rel includes icon, and a linked manifest when present.
3. Read the result rows
Each row can show found, missing, or error; reachable rows may include HTTP status, format, declared bytes, and detected dimensions.
Public URL and resource boundaries
Requests are routed through the public-URL checker. The limits below keep one run bounded and are shown here so the report can be interpreted in context.
- HTTP(S) — accepted starting URL protocols
- 03 — maximum redirect hops
- 10 s — starting document request timeout
- 05 s — icon and manifest request timeout
- 2 MB — maximum icon bytes inspected for dimensions
- 256 KB — maximum manifest bytes inspected
Read the report as observed evidence
- Compare the displayed URL with the reference used by your site
- Check format, dimensions, and HTTP status where the row provides them
- Re-run after a deployment or cache change, then test the installed site in its intended browser context
Ready to trace the visible icon references?
Open the tester, enter one public website URL, and review the returned rows alongside the installed site.
Trace declared favicon paths from one public website URL
Which URLs can be submitted?
The checker accepts public HTTP or HTTPS URLs. URLs containing credentials, local hostnames, and private network addresses are rejected before requests are made.
Does it inspect every favicon on a domain?
No. It checks the origin’s favicon.ico, up to eight declared HTML icon links, and up to eight valid icon entries from a linked manifest.
Why might dimensions be blank?
Dimensions are read only from bounded image responses that match the recognized PNG, JPEG, or ICO signatures. SVG rows can still show format and reachability without image dimensions.