Contact Favicon.now

What to include

A short, complete report is the fastest path to a useful reply. You can copy the checklist below into your message. Never send a password, OAuth token, private key, unpublished artwork, or another person’s personal data.

1. 01

   Technical correction

   Provide the affected page, expected behavior, observed behavior, platform or browser version, public asset URL, and a primary source when one is relevant. For a favicon discovery problem, include the page URL, icon URL, response status, MIME type, and the exact HTML link element.

2. 02

   Tool or account problem

   Describe the route, input type, visible error, and approximate time. Say whether the problem happens before preview, during download, while signing in, or when opening a saved project. Do not email passwords, OAuth tokens, private artwork, or client secrets.

3. 03

   Editorial or partnership question

   Identify the guide, dataset, or workflow involved and explain the concrete value for readers. Favicon.now does not accept paid links, fabricated reviews, undisclosed advertorial copy, or unrelated guest posts.

4. 04

   Privacy or deletion request

   Use the email associated with the account when practical, name the request clearly, and avoid adding unnecessary personal information. Review the privacy policy first for the data categories and account controls already available.

Before reporting a missing favicon

Open the icon URL directly and confirm that it returns an image with a successful status. Next, run the page through the favicon checker. If the issue is an ICO container, use the ICO inspector. These results help separate an HTML discovery mistake from a file, redirect, cache, or server-header problem.