V
Connect failure - perhaps firewall
Checked: 29.11.2024 23:15:51
Older results
No older results found
1. IP-Addresses Host Type IP-Address is auth. ∑ Queries ∑ Timeout 82.114.162.154 A 82.114.162.154 Sanaa/Amanat Alasimah/Yemen (YE) - Public Telecommunication Corporation No Hostname found yes
2. DNSSEC
No DNSSEC - Informations found
3. Name Servers
No Nameserver entries found
4. SOA-Entries
No SOA entries found
5. Screenshots
No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.
6. Url-Checks Domainname Http-Status redirect Sec. G • http://82.114.162.154/82.114.162.154
-102 1.346 V ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (82.114.162.154:80) • https://82.114.162.154/82.114.162.154
-102 1.340 V ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (82.114.162.154:443) • http://82.114.162.154/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de82.114.162.154
-102 1.340 V ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (82.114.162.154:80) Visible Content: • https://82.114.162.154/82.114.162.154
-102 1.340 V ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (82.114.162.154:443)
7. Comments 1. General Results, most used to calculate the result A name "82.114.162.154" is ipv4 address, public suffix is not defined A Good: All ip addresses are public addresses V http://82.114.162.154/ 82.114.162.154 Connect failure - perhaps firewall V https://82.114.162.154/ 82.114.162.154 Connect failure - perhaps firewall V http://82.114.162.154/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 82.114.162.154 Connect failure - perhaps firewall V https://82.114.162.154/ 82.114.162.154 Connect failure - perhaps firewall B No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.82.114.162.154 2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05) U No https result with http status 2** or 4** (standard-check) found, no header checked. 3. DNS- and NameServer - Checks 4. Content- and Performance-critical Checks http://82.114.162.154/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 82.114.162.154 Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. A Info: No img element found, no alt attribute checked A Duration: 12510 milliseconds, 12.510 seconds
8. Connections
No connection informations found. Perhaps only http - connections.
9. Certificates
No certificate informations found. Perhaps only http - connections.
10. Last Certificates - Certificate Transparency Log Check 1. Source CertSpotter - active certificates (one check per day)
No CertSpotter - CT-Log entries found
2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months are listed
No CRT - CT-Log entries found
11. Html-Content - Entries
No Html-Content entries found. Only checked if https + status 200/401/403/404
12. Html-Parsing via https://validator.nu/ / https://validator.w3.org/nu/ (started 2024-09-28, 09:00, alpha)
Unfortunately, there are differences between the first used validator.nu and validator.w3.org/nu/ - switched to validator.w3.org/nu/. Looks like some error messages (link - fetchpriority attribute) of validator.nu are obsolete, not seen in the w3.org-version and not found in the current specification: link may have a fetchpriority attribute.
No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check
13. Nameserver - IP-Adresses
Required Root-climbing DNS-Queries to find ip addresses of all Name Servers:
No NameServer - IP address - Informations found
14. CAA - Entries
No CAA entries found
15. TXT - Entries
No TXT entries found
16. DomainService - Entries
No DomainServiceEntries entries found
17. Cipher Suites No results
18. Portchecks
No open Ports <> 80 / 443 found, so no additional Ports checked.
Permalink:
https://check-your-website.server-daten.de/?i=c2bb10bc-0c3f-4507-bd9f-c4d094b96a69
Last Result:
https://check-your-website.server-daten.de/?q=82.114.162.154 - 2024-11-29 23:15:51
Do you like this page? Support this tool, add a link on your page:
<a href="https://check-your-website.server-daten.de/?q=82.114.162.154" target="_blank">Check this Site: 82.114.162.154</a>
Copy to Clipboard
Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro