Check DNS, Urls + Redirects, Certificates and Content of your Website


 

 

V

 

Connect failure - perhaps firewall

 

Checked:
10.01.2025 14:25:10

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
13.53.119.189
A
13.53.119.189
Stockholm/Sweden (SE) - Amazon Technologies Inc.
Hostname: ec2-13-53-119-189.eu-north-1.compute.amazonaws.com
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


:

:
DomainnameHttp-StatusredirectSec.G
• http://13.53.119.189/
13.53.119.189 gzip used - 14954 / 37297 - 59.91 %
200

Html is minified: 103.24 %
0.084
H
Server: nginx/1.18.0,(Ubuntu)
Date: Fri, 10 Jan 2025 13:25:14 GMT
Transfer-Encoding: chunked
Connection: keep-alive
Content-Security-Policy: default-src 'self' wss://*.zopim.com https://*.zendesk.com https://*.zdassets.com wss://*.enhancell.com ws://*.enhancell.com https://*.google-analytics.com https://maps.googleapis.com; font-src *;img-src * data: blob:; script-src 'unsafe-inline' 'unsafe-eval' *; style-src 'unsafe-inline' *;
X-Content-Type-Options: nosniff
Referrer-Policy: strict-origin
X-XSS-Protection: 1; mode=block
Strict-Transport-Security: max-age=31536000; includeSubdomains
X-Frame-Options: SAMEORIGIN
Cache-Control: no-cache
Pragma: no-cache
Content-Type: text/html; charset=UTF-8
Content-Encoding: gzip
Content-Length: 14954

• https://13.53.119.189/
13.53.119.189
-102


1.143
V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (13.53.119.189:443)

• http://13.53.119.189/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
13.53.119.189 gzip used - 13986 / 34739 - 59.74 %
Inline-JavaScript (∑/total): 3/31568 Inline-CSS (∑/total): 0/0
404

Html is minified: 102.62 %
Other inline scripts (∑/total): 0/0
0.080
A
Not Found
Visible Content:
Server: nginx/1.18.0,(Ubuntu)
Date: Fri, 10 Jan 2025 13:25:16 GMT
Transfer-Encoding: chunked
Connection: keep-alive
Content-Security-Policy: default-src 'self' wss://*.zopim.com https://*.zendesk.com https://*.zdassets.com wss://*.enhancell.com ws://*.enhancell.com https://*.google-analytics.com https://maps.googleapis.com; font-src *;img-src * data: blob:; script-src 'unsafe-inline' 'unsafe-eval' *; style-src 'unsafe-inline' *;
X-Content-Type-Options: nosniff
Referrer-Policy: strict-origin
X-XSS-Protection: 1; mode=block
Strict-Transport-Security: max-age=31536000; includeSubdomains
X-Frame-Options: SAMEORIGIN
Content-Type: text/html; charset=UTF-8
Content-Encoding: gzip
Content-Length: 13986

• https://13.53.119.189/
13.53.119.189
-102


1.137
V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (13.53.119.189:443)

 

7. Comments


1. General Results, most used to calculate the result

Aname "13.53.119.189" is ipv4 address, public suffix is not defined
AGood: All ip addresses are public addresses
AGood - only one version with Http-Status 200
AGood: No cookie sent via http.
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
HFatal error: No https - result with http-status 200, no encryption
HFatal 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.
Ihttp://13.53.119.189/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 13.53.119.189
404

Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Not used to calculate the result because it's a http - check. But listed so you should fix it.
Vhttps://13.53.119.189/ 13.53.119.189
-102

Connect failure - perhaps firewall
Vhttps://13.53.119.189/ 13.53.119.189
-102

Connect failure - perhaps firewall
BNo _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.13.53.119.189

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

AGood: 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.
http://13.53.119.189/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 13.53.119.189
404

Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 6 script elements without defer/async.
AGood: All CSS / JavaScript files are sent compressed (gzip, deflate, br checked). That reduces the content of the files. 3 external CSS / JavaScript files found
Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 18 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 3 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 21 complete.
AGood: All checked attribute values are enclosed in quotation marks (" or ').
AInfo: No img element found, no alt attribute checked
http://13.53.119.189/ 13.53.119.189
200

Warning: HSTS header sent via http has no effect
ADuration: 30970 milliseconds, 30.970 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

Summary


Subresource Integrity (SRI)
DomainnameHtmlElementrel/property∑ size∑ problems∑ int.∑ ext.∑ Origin poss.∑ SRI ParseErrors∑ SRI valid∑ SRI missing
http://13.53.119.189/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
13.53.119.189
a

1

0


0
0
0


link
stylesheet
15
2,441 Bytes
12
12
3
3
0
0
-3

link
other
1

1
1
0
0
0
0


meta
other
3

0


0
0
0


script

6

6
6
0
0
0
0

 

Details (currently limited to 500 rows - some problems with spam users)

Small Code Update - wait one minute

 

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=a5a8c605-7bec-42c0-8816-c3fae350ede8

 

Last Result: https://check-your-website.server-daten.de/?q=13.53.119.189 - 2025-01-10 14:25:10

 

Do you like this page? Support this tool, add a link on your page:

 

<a href="https://check-your-website.server-daten.de/?q=13.53.119.189" target="_blank">Check this Site: 13.53.119.189</a>

 

 

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro

 

QR-Code of this page - https://check-your-website.server-daten.de/?d=13.53.119.189