P
Tls-Protocol error
Checked: 31.10.2024 03:00:48
Older results
1. IP-Addresses Host Type IP-Address is auth. ∑ Queries ∑ Timeout 185.182.193.203 A 185.182.193.203 Naaldwijk/South Holland/The Netherlands (NL) - WorldStream B.V. Hostname: customer.worldstream.nl 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 show header :
show header :
Domainname Http-Status redirect Sec. G • http://185.182.193.203:25461/185.182.193.203
200 Html is minified: 100.00 % 0.064 H • https://185.182.193.203:25461/185.182.193.203
-103 0.060 P SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Cannot determine the frame size or a corrupted frame was received • http://185.182.193.203:25461/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de185.182.193.203
Inline-JavaScript (∑/total): 0/0
Inline-CSS (∑/total): 0/0 404 Html is minified: 109.46 %
Other inline scripts (∑/total): 0/0 0.060 A Not Found Visible Content: • https://185.182.193.203:25461/185.182.193.203
-103 0.057 P SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Cannot determine the frame size or a corrupted frame was received
7. Comments 1. General Results, most used to calculate the result A name "185.182.193.203" is ipv4 address, public suffix is not defined A Good: All ip addresses are public addresses A Good - only one version with Http-Status 200 A Good: No cookie sent via http. A Good: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):1 complete Content-Type - header (2 urls) http://185.182.193.203:25461/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.182.193.203 Url with incomplete Content-Type - header - missing charset H Fatal error: No https - result with http-status 200, no encryption H Fatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. 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.185.182.193.203 2. Header-Checks 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 A Good: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. A Info: No img element found, no alt attribute checked A Duration: 5803 milliseconds, 5.803 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.w3.org/nu/ 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=c2b3824f-898a-423c-a6d0-173ace7c6b88
Last Result:
https://check-your-website.server-daten.de/?q=185.182.193.203%3A25461 - 2025-06-21 11:09:44
Do you like this page? Support this tool, add a link on your page:
<a href="https://check-your-website.server-daten.de/?q=185.182.193.203%3A25461" target="_blank">Check this Site: 185.182.193.203%3A25461</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