Because http://porsche-club-hildesheim.de/ (and http://www.porsche-club-hildesheim.de/ for that matter) are redirecting to http://cms.porsche-clubs.com/PorscheClubs/pc_hildesheim/pc_main.nsf, which is an entirely different hostname and also with an entirely different IP address.
Also:
Please note that if you want to include the www subdomain in your certificate, you need to specify it in the command also. You can repeat multiple -d options for multiple hostnames if required.
Also also:
Please note that while the Certbot standalone plugin can listen on different ports, like you've instructed it to do here, the Let's Encrypt validation server will ALWAYS connect to port 80 using HTTP. (When using the http-01 challenge, which is the case when using the standalone authenticator plugin. Any other value of --preferred-challenges would not change that..) The Certbot option does NOT influence the Let's Encrypt validation challenge in any way.
Is there a specific reason for the usage of the standalone plugin?