HTTPS, HSTS and embedded resources create neither certificate errors nor mixed content.

Expectations and evidence

Required inputs (protocol identifiers)

http, tls, render, configuration, intent

When it applies

Hosts and resources of a public web service.

How to check

Test certificates on public hosts, follow HTTP/HTTPS variants, record Strict-Transport-Security and find HTTP subresources.

Expectation

Certificates and redirects are valid for tested hosts; mixed content is reviewed; the HSTS decision and scope are documented without requiring preload.

Evidence to retain

Archived certificates and HTTP chains, reviewed mixed resources, explicit HSTS decision and documented scope.

Non-applicability

No relevant public HTTP service.

Limitations

HSTS strengthens transport after the policy is received; it fixes neither an invalid certificate nor a poor URL architecture.

Outcome clarification

C requires all expectations across the declared scope. NC requires evidenced contradiction; otherwise NT. NA requires evidence of non-applicability.

Reference scope

Technical reference; the TSEP acceptance rule remains an editorial proposal.