I think you’re right - that it is stuck in our internal caches. However, it’s super hard for me to tell since you don’t have a valid SSL certificate for browsers to connect to (you instead use the cloudflare origin certificate, which is totally not required but causes problems like this for our debugging), for your custom hostname.
Could you change Cloudflare to connect to cranky-mcnulty-01683e.netlify.app instead of wolstenhol.me/www, please? Then you’ll route around this cache AND our staff will be better able to help you debug going forward.
This kind of situation is why we in general do not provide tech support for people proxying to us from Cloudflare: [Support Guide] What problems could occur when using Cloudflare in front of Netlify?