HTTP Strict Transport Security (HSTS) instructs browsers to use HTTPS for a hostname. If HSTS applies to the source hostname of an UltraDNS Web Forwarding record, that hostname must support HTTPS before the browser can receive the redirect.
UltraDNS supports HTTP and HTTPS Web Forwarding. HTTPS Web Forwarding requires the applicable certificate management feature to be enabled on your account and a certificate applied to the forward.
When to Use This Article
- The browser changes the source URL from
http://tohttps://before forwarding completes. - The browser displays a secure connection or certificate error instead of reaching the destination.
- You need to check whether HSTS preloading applies to the source hostname.
These symptoms alone do not confirm that HSTS caused the issue.
How HSTS Affects Web Forwarding
The source hostname is the address the visitor opens. The destination URL is the address configured in Redirects To.
When HSTS applies, the browser upgrades an HTTP URL for the source hostname to HTTPS before sending the request. The source must then establish a valid HTTPS connection before returning a redirect.
For example, if example.com forwards to https://www.example.net and HSTS applies to example.com, the browser must first connect securely to https://example.com. HTTPS at the destination does not provide HTTPS support for the source hostname.
Check HSTS Preload Status
An HSTS preload list is included in browsers so they can require HTTPS before a visitor first connects to a listed domain.
- Identify the exact source hostname configured for the forward.
- Open the HSTS preload checker.
- Enter the source hostname without a URL scheme or path, such as
www.example.com, and run the check. - Review the reported preload status and any coverage inherited from a parent domain or top-level domain.
HSTS can apply through a parent domain that includes subdomains. Entire top-level domains can also be preloaded, requiring HTTPS for domains beneath them.
A result showing that a hostname is not preloaded does not rule out HSTS. A browser can also store an HSTS policy received previously through the Strict-Transport-Security response header. Browser preload lists can differ by browser and version.
Check HTTPS Web Forwarding
- Check whether the source Web Forwarding record has
HTTPS Forwardenabled. - Confirm that a valid certificate covering the source hostname is applied to the forward.
- If HTTPS Web Forwarding is needed, use one of the supported certificate options:
- Upload and apply your own TLS/SSL certificate when Certificate Management is enabled.
- Select
Use an UltraDNS Managed Certificatewhen Automated Certificate Management is enabled.
- If the required certificate feature is unavailable, contact UltraDNS Technical Support to request enablement.
- Open the source URL explicitly with
https://and confirm that the browser reaches the configured destination without a certificate or secure connection error.
If Forwarding Still Fails
Provide UltraDNS Technical Support with the exact source URL, destination URL, browser name and version, error text, and HSTS checker result. Include the HTTPS Forward setting and the certificate option used.
Preload status identifies an HTTPS requirement. It does not, by itself, establish the cause of a forwarding failure.