This is your problem. Make sure Apache is listening on port 80, and there's no firewall (on your server, at your ISP, or anywhere else) blocking connections to port 80.
I turned off all firewalls up to my ISP connection and still have the same. my ISP says thy don't block anything because I have a Bisnes Internet with IPs.
You need to read that output more carefully--it's telling you you have DNSSEC issues (which letsdebug.net confirms: Let's Debug), and that connections to your site time out.
Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC covers the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC-Records, so DNSSEC works.
Again, this is incorrect. Your DNS hosting is being done by Network Solutions, who is also your domain registrar; you are not hosting that yourself. You could do that, but it isn't necessary, and I don't think I'd recommend it. So, you can ask Network Solutions how to fix their DNSSEC, or you can consider using a different DNS host. For the latter, I use Cloudflare. They're free for DNS service (they have other services which they charge for, but DNS is free), and they seem to work well.
No, you are not the registrar. Network Solutions is the registrar. You may be the registered owner (I can't see that, but I trust it's the case), but not the registrar.
sure, I buy and sell domain names and completely manage them in networksoultions and SRS. I just need what letsencrypt is looking for and an example of what to put in DNS like:
create a TXT record like "_acme-challenge.hosts.yourwebspace.com" and so on.
To check the DNS see the unboundtest.com site (link here). If you try looking up a CAA or AAAA record you will get a SERVFAIL. These are not required but the DNS server should return "not found" and not SERVFAIL. We recently had a similar problem with another person who was using Network Solutions. You will need to work with them on this problem.
I link it here only as reminder for other volunteers
Working DNS (including DNSSEC if you're using it) is essential for any validation method. You don't need to use DNSSEC, but if you're using it, it must be configured properly, and that looks like it's the most fundamental problem with your domain right now.
Second, if you're using HTTP validation, your server must respond on port 80. This is also a problem with your domain right now.
DNSSEC might be something you can add and remove records from your DNS zone control panel.
If the problem is "lower" than that, then only the DNS server admin [Network Solutions] can fix it.