[Bug Report]: agent-tars.com serves a certificate for netlify.app

Version

Current main at c2ad42e3eb9b27830db41a3e6f51ca7179d9b168; live deployment checked on 2026-08-22 UTC.

Issue Type

• Other: Agent TARS documentation website deployment

Model Provider

Not applicable.

Problem Description

The repository advertises https://agent-tars.com as its homepage and documentation site, but standard HTTPS clients currently reject the site's certificate because it does not contain agent-tars.com in its subject alternative names.

Reproduction on Windows with curl 8.x:

> curl.exe -I https://agent-tars.com
curl: (60) schannel: SNI or certificate check failed: SEC_E_WRONG_PRINCIPAL

A Node.js TLS inspection reports:

{
  "authorized": false,
  "authorizationError": "ERR_TLS_CERT_ALTNAME_INVALID",
  "subject": { "CN": "*.netlify.app" },
  "subjectaltname": "DNS:*.netlify.app, DNS:netlify.app"
}

Expected: the certificate presented for the custom domain includes agent-tars.com, allowing browsers and other standards-compliant clients to open the documentation normally.

Actual: Chrome reports ERR_CERT_COMMON_NAME_INVALID, and curl/Node reject the connection. Using curl's insecure -k option returns the Netlify-hosted page with HTTP 200, which confirms that the content origin is responding but does not make the public endpoint safe or usable for normal clients.

Impact: the repository homepage, documentation navigation, downloads and linked guides are blocked by the browser's certificate interstitial. HSTS is also enabled on the response, so users cannot treat bypassing certificate validation as a supported workaround.

I am filing this as issue-only because the certificate, custom-domain and DNS configuration is not present in the tracked repository and requires access to the project's Netlify/domain settings. There is no safe repository pull request that can repair or validate the deployment. Suggested validation after the configuration change: check apex and any supported www hostname over IPv4/IPv6, verify the full chain/SANs, and add an external expiry/hostname monitor.

Error Logs

curl: (60) SEC_E_WRONG_PRINCIPAL
Node.js: ERR_TLS_CERT_ALTNAME_INVALID
Presented SAN: DNS:*.netlify.app, DNS:netlify.app