Unable to connect... but the reason is because you are trying to serve up a secure page (https) via port 443... For just normal stuff, you only really need port 80 (http). You can pay $$$ to get a signed certificate, but it is only good for the domain name, so if you eventually change to gunnyworld.com, then you have to pay $$$ to get another certificate... and gunnyworld.com and
www.gunnyworld.com require 2 separate certificates, since they are 2 separate domains. You can invest in a wildcard certificate (*.gunnyworld.com), but they are higher priced, and not guaranteed to work with everything like regular certificates are.
You can do a google search for SSL certificates, and there should be several tutorials, as well as several companies who are willing to take your money for one. If you aren't doing e-commerce, and really just want to serve up some pages (similar to meow), then you don't need an https address, and can host certificate-error-free by browsing to http instead of https. https doesn't protect your server per se, it protects your client from having their data intercepted by someone not authorized to receive it...
Windows, Firefox, Opera, etc all have their "whitelists", so you want to find a registrar that is compatible with most of the browsers out there. Comodo used to be a good trusted company, but they have been the target of some massive scams lately, so it may be beneficial to do your research, and possibly go with another company until they can get things straightened out... Verisign is trusted basically everywhere, but you pay and arm and a leg for it. GoDaddy offers some pretty reasonable ones, so that might be an option, especially if you have your hostname registered through them. Bluehost and other hosting companies also offer them for additional fees.
I have used XAMPP on Windows XP, but it has been a long while ago. Anyways, you should be able to configure your certificate in the apache config files (once you have a valid one), or just redirect the https visitors to your http page...