And yet what shows on your homepage for
https://www.hamies.world is a foot banner for
ParkingCrew.com- without any advertising above it.
You have a redirect from one http domain to another http domain which would cause another DNS lookup.
You also have a wrong redirect - https to http - for
Never redirect https back to http and make your redirects for Port 80, but not for Port 443.
Cloudflare's Amsterdam and Frankfurt's servers are returning an error code of 520 on http requests to www.hamies.world. There's a problem between your original server and the cache on Cloudflare's servers.
You do have a Cloudflare certs for
hamies.world and a wildcard
*.hamies.worldthat's good until July, 2022. However, secure connections are being aborted. You have to have Cloudflare's IPs on your allowed list for your firewall. Why not use Cloudflare's certs which covers both your apex domain and the wildcard (*.hamies.world)?
A way to start overcoming your problem would be to
Decide on one domain to serve your content (either the www or apex (non-www);
Clean up your redirects;
Check that your domain (both the www and the apex) is reachable with a web browser. You'll have to wait a bit for the changes above to propagate; and
See if Cloudflare's cert is being served (https). (Cloudflare has supplied you with certs already.)
If everything is fine, you're back in business.
If you see the lock but it still it still shows as insecure, most likely there is content being served over http - most likely some ads being served by ParkingCrew. You can check for unsecure content by using this tool https://www.whynopadlock.com/ .
Please let us know how you make out.