DOMAIN COMMAND POSTMonitor. Manage. Discover. Protect.

Help Center / Logos, Favicons & Custom Images

Use the right image in the right place—and never show a broken icon.

Application branding, domain favicon priority, custom domain images, caching and edition boundaries.

Applies toWebsite and every Windows editionTypical time3–10 minutesGuide formatPrepare → Click → Verify → Recover

Application identity rules

LocationRequired asset
Sidebar, About, installer, splash and documentationFull Domain Command Post shield/logo with readable brand text where space permits.
EXE resource, taskbar, tray, title-bar small icon and compact controlsSimplified Domain Command Post icon designed to remain recognizable at small sizes.
Sidebar wordmarkTwo-line text: DOMAIN / COMMAND POST. The edition appears separately.

Domain favicon display order

  1. Use a successfully downloaded real site favicon and cache it locally.
  2. If no usable site favicon exists, use the custom domain logo assigned by the user.
  3. If neither exists, show the dedicated Favicon Missing icon.
  4. Never leave a broken browser-image symbol, blank unknown square or application logo pretending to be the site’s favicon.

Refresh a real favicon

Program path: My Domains → select domain → Website → Refresh favicon

  1. Select Refresh favicon.
  2. The program checks supported icon declarations and conventional locations, validates content type and decodes the image.
  3. A valid result replaces the cached favicon. A failed refresh keeps the last known valid cached icon and reports the failure time/reason.

Assign a custom domain logo

Program path: My Domains → select domain → Website → Assign custom icon

  1. Choose PNG, JPEG, WebP or ICO from a trusted local file.
  2. Crop or fit it in the preview without changing the original file.
  3. Save. The custom image is copied into Domain Command Post data and follows that domain record in approved backups.
  4. If a real favicon is later found, it takes display priority while the custom image remains stored as fallback.

Edition and publishing boundary

All editions may display real favicons and the missing-icon fallback. Custom domain images are enabled only where that edition’s feature manifest permits record customization. Public edition packages receive only approved brand assets. Internal-only seed images, customer sets, local publishing art and private build assets are excluded from public packages.

Website themes and backgrounds

Website visitors can use Command Blue, Dark Ops, Midnight Green, Slate Pro, Light Command and a browser-local Custom Theme. Uploaded website background images stay in that browser’s local storage and are not uploaded to the server. Application-only themes are not exposed by the website.

Still stuck?

Write down the edition, program version, the exact path you opened, the last successful step and the full visible error. Do not send product keys, passwords or provider secrets.

Contact support with those detailsBack to Help Center