Trace where HTTP/2 terminates
A website may use HTTP/2 at a CDN or load balancer, then use HTTP/1.1 between the proxy and Apache. Another system may negotiate HTTP/2 directly with Apache. The host name alone does not tell you which component handles the protocol.
Map DNS, edge services, load balancers, reverse proxies and origin servers. Record where TLS terminates, whether HTTP/2 is enabled and which team controls each layer. This makes the scope of Apache mod_http2 advisories clear.
Confirm the module and package
Check whether mod_http2 is loaded and identify the exact Apache package build. For managed hosting or appliances, ask the supplier for its CVE status and patch level. A scanner that reports only a version banner may not know that a vendor backported a fix.
Include test and recovery environments. They may have older builds and can be reached through internal networks or deployment tools. Assign an owner to unknown servers rather than excluding them from the review.
Validate after the change
After applying the supported fix, confirm the running binary, module list and protocol negotiation. Test public pages, APIs, TLS certificates and upstream routes. Check server health and logs for errors during restart.
Keep the evidence with the asset record: package source, version, configuration reviewed, date and result. Repeat this check when the server or hosting provider changes.
