List the public hosts and URL patterns to test
Choose a sample that catches protocol and hostname gaps.
Use this for: Sites being moved to HTTPS or checked for secure-delivery regressions.
List your preferred public hostname, alternate hostnames that visitors still use and important page templates. Include the homepage, a deep service or product page, a document and a URL with meaningful parameters if your site uses them. Use an existing crawl or CMS URL list when available.
For each entry point, identify the intended final HTTPS page. Include only domains you operate or are authorized to test. This planning task can pass when the sample and expected destinations are clear; it does not certify the site as secure.
Hypothetical example: A repair business tests the bare domain, its www alias, a service page and a booking landing page instead of checking only the homepage.
- List the public hostnames and representative URL patterns.
- Name the expected final HTTPS page for each.
- Keep the same samples for the routing and resource checks.
More help and optional notes
If it fails: Add the missing entry point or pattern before making site-wide conclusions.
Retest: Refresh the sample after domain, routing or template changes.
Not applicable: No URLs or implementation in this task’s scope.
Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.
Changing this result updates your checkmark and progress immediately. Notes are optional.

