An HTTP 401 or 403 is evidence that an HTTP service answered along the tested path. It is not evidence of a closed port, and a proxy can be the responder.
For Bitcoin Core RPC, keep listener addresses, allowed clients, authentication, permitted operations, and network routes separate. A result for IPv4 does not settle IPv6.
My source review includes an eight-case worksheet and the fixed Core v31.1 source files behind it, alongside Docker documentation. No running node or firewall was tested; every case remains not_tested.


CypherpunkGuide
Bitcoin Core RPC Exposure: What a Firewall Check Cannot Prove
Review Bitcoin Core RPC exposure through listener settings, source restrictions, authentication, Docker routes, and IPv4/IPv6 evidence, with an eig...


