Fix www not working in Namecheap: when this repair path applies
Add or correct the www CNAME/host record without disturbing the apex record. Use these steps when root works but www does not, but first run the embedded diagnostic so the TLS, certificate and HTTPS evidence supports this provider-specific path rather than a neighboring DNS, TLS, application or mail cause.
Find the authoritative setting before editing
Namecheap Advanced DNS and, when applicable, the nameserver provider currently authoritative for the domain. For Fix www not working in Namecheap, confirm the active nameservers and exact service owner before changing inspect www record. A DNS-looking screen at namecheap has no public effect when another provider is authoritative for the zone.
Evidence to save for Fix www not working in Namecheap
Record the current public state for inspect www record, point it to the intended target, confirm certificate coverage. This gives the repair a before/after comparison and prevents a cached answer or a separate working service from being confused with the configuration that produced the symptom.
- Inspect www record — Verify inspect www record from the public Internet and compare it with the value the responsible provider says should be live.
- Point it to the intended target — Verify point it to the intended target from the public Internet and compare it with the value the responsible provider says should be live.
- Confirm certificate coverage — Test the hostname actually requested, its certificate dates and SAN coverage, and the TLS handshake. Root and www can serve different certificates.
- Retest HTTPS — Record the public status, final URL and relevant response headers. A working DNS answer does not prove that the application is serving a genuine website response.
Repair steps in namecheap
Add or correct the www CNAME/host record without disturbing the apex record.
- 1. Inspect www record. After this step, check the public value tied to inspect www record before changing another unrelated setting.
- 2. Point it to the intended target. After this step, check the public value tied to point it to the intended target before changing another unrelated setting.
- 3. Confirm certificate coverage. After this step, check the public value tied to confirm certificate coverage before changing another unrelated setting.
- 4. Retest HTTPS. After this step, check the public value tied to retest https before changing another unrelated setting.
Why this order matters for namecheap
The sequence begins with the provider/authority decision, then moves through inspect www record, point it to the intended target, confirm certificate coverage. That keeps the change scoped to the failed TLS, certificate and HTTPS path and avoids replacing nameservers, mail authentication or another healthy service just to make a provider dashboard indicator change.
Verify Fix www not working in Namecheap
HTTPS should complete for the exact hostname, the certificate should be valid for that hostname, and root/www should follow the intended canonical redirect without a TLS error. Compare the same inspect www record and point it to the intended target evidence used before the change; a repair is complete when the public result agrees, not merely when the namecheap interface reports that a save succeeded.
If namecheap and the public result disagree
Check whether the edited zone is authoritative, whether the exact root/www/subdomain was changed, whether a proxy state alters the visible endpoint, and whether a prior TTL can still exist in recursive caches. Do not add a second conflicting inspect www record value to force validation.
Mistakes to avoid for this repair
Do not copy tenant-specific or region-specific values from another account, delete working email records during a website repair, change nameservers as a shortcut, or alter SSL/proxy modes without evidence from the origin. Fix www not working in Namecheap should change only the settings required by this diagnosis.
Technical references
These primary standards and provider documents are used to verify the behavior described on this page. Provider dashboards can change, so use the current official value for tenant-specific DNS records rather than copying an example from another account.