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





1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
pielmed.com
A
167.172.123.53
Santa Clara/California/United States (US) - DigitalOcean, LLC
No Hostname found
yes
1
0

AAAA
2604:a880:2:d1::1a4:8001
Santa Clara/California/United States (US) - DigitalOcean, LLC

yes



AAAA
2607:f1c0:100f:f000::2e0
Kansas City/Missouri/United States (US) - 1&1 Internet SE

yes


www.pielmed.com
A
167.172.123.53
Santa Clara/California/United States (US) - DigitalOcean, LLC
No Hostname found
yes
1
0

AAAA
2604:a880:2:d1::1a4:8001
Santa Clara/California/United States (US) - DigitalOcean, LLC

yes



AAAA
2607:f1c0:100f:f000::2e0
Kansas City/Missouri/United States (US) - 1&1 Internet SE

yes



2. DNSSEC

Zone (*)DNSSEC - Informations (beta)

Zone: (root)
(root)
1 DS RR published



Status: Valid because published



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 33853, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.02.2020, 00:00:00, Signature-Inception: 11.01.2020, 00:00:00, KeyTag 20326, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: com
com
1 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.01.2020, 05:00:00, Signature-Inception: 14.01.2020, 04:00:00, KeyTag 33853, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 33853 used to validate the DS RRSet in the parent zone



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 12163, Flags 256



Public Key with Algorithm 8, KeyTag 30909, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 56311, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 21.01.2020, 19:24:21, Signature-Inception: 06.01.2020, 19:19:21, KeyTag 30909, Signer-Name: com



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 21.01.2020, 19:24:21, Signature-Inception: 06.01.2020, 19:19:21, KeyTag 30909, Signer-Name: com



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 30909 used to validate the DNSKEY RRSet



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 30909 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest "4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: pielmed.com
pielmed.com
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed domain name between the hashed NSEC3-owner and the hashed NextOwner. So the parent zone confirmes the non-existence of a DS RR.



0 DNSKEY RR found





Zone: www.pielmed.com
www.pielmed.com
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.pielmed.com
  ns1059.ui-dns.org / dns-pub-de-fra-fra304.server.lan

pielmed.com
  ns1058.ui-dns.biz / dns-pub-de-fra-fra301.server.lan
217.160.81.58
Frankfurt am Main/Hesse/Germany (DE) - AS8560 anycast


 
2001:8d8:fe:53:0:d9a0:513a:100
Karlsruhe/Baden-Württemberg/Germany (DE) - AS8560 anycast


  ns1059.ui-dns.org / dns-pub-de-fra-fra304.server.lan
217.160.83.59
Frankfurt am Main/Hesse/Germany (DE) - AS8560 anycast


 
2001:8d8:fe:53:0:d9a0:533b:100
Karlsruhe/Baden-Württemberg/Germany (DE) - AS8560 anycast


  ns1067.ui-dns.com / dns-pub-de-fra-fra302.server.lan
217.160.82.67
Frankfurt am Main/Hesse/Germany (DE) - AS8560 anycast


 
2001:8d8:fe:53:0:d9a0:5243:100
Karlsruhe/Baden-Württemberg/Germany (DE) - AS8560 anycast


  ns1125.ui-dns.de / dns-pub-de-fra-fra304.server.lan
217.160.80.125
Frankfurt am Main/Hesse/Germany (DE) - AS8560 anycast


 
2001:8d8:fe:53:0:d9a0:507d:100
Karlsruhe/Baden-Württemberg/Germany (DE) - AS8560 anycast

com
  a.gtld-servers.net


  b.gtld-servers.net


  c.gtld-servers.net


  d.gtld-servers.net


  e.gtld-servers.net


  f.gtld-servers.net


  g.gtld-servers.net


  h.gtld-servers.net


  i.gtld-servers.net


  j.gtld-servers.net


  k.gtld-servers.net


  l.gtld-servers.net


  m.gtld-servers.net


4. SOA-Entries


Domain:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1578997168
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:9


Domain:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1578997183
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:4


Domain:pielmed.com
Primary:ns1059.ui-dns.org
Mail:hostmaster.1und1.com
Serial:2017060103
Refresh:28800
Retry:7200
Expire:604800
TTL:600
num Entries:8


Domain:www.pielmed.com
Primary:ns1059.ui-dns.org
Mail:hostmaster.1und1.com
Serial:2017060103
Refresh:28800
Retry:7200
Expire:604800
TTL:600
num Entries:1


5. Screenshots (Beta)

Startaddress: https://pielmed.com, address used: https://pielmed.com/, Screenshot created 2020-01-14 11:21:53 +00:0

Mobil (412px x 732px)

302 milliseconds

Screenshot mobile - https://pielmed.com/
Screen (1280px x 1680px)

398 milliseconds

Screenshot Desktop - https://pielmed.com/
Mobil + Landscape (732px x 412px)

292 milliseconds

Screenshot mobile landscape - https://pielmed.com/

Mobile- and other Chrome-Checks

widthheight
visual Viewport412716
content Size560716

Fatal: Horizontal scrollbar detected. Content-size width is greater then visual Viewport width.

Chrome-Connection: secure. secure connection settings. The connection to this site is encrypted and authenticated using TLS 1.2, ECDHE_RSA with X25519, and AES_128_GCM.

Chrome-Resources : secure. all served securely. All resources on this page are served securely.

6. Url-Checks


:

:
Domainname Http-StatusredirectSec.G
• http://pielmed.com/
167.172.123.53
301
https://pielmed.com/
Html is minified: 109.03 %
0.360
A
Server: nginx/1.17.7
Date: Tue, 14 Jan 2020 10:20:23 GMT
Content-Type: text/html
Content-Length: 169
Connection: close
Location: https://pielmed.com/

• http://www.pielmed.com/
167.172.123.53
301
https://pielmed.com/
Html is minified: 109.03 %
0.357
E
Server: nginx/1.17.7
Date: Tue, 14 Jan 2020 10:20:24 GMT
Content-Type: text/html
Content-Length: 169
Connection: close
Location: https://pielmed.com/

• http://pielmed.com/
2604:a880:2:d1::1a4:8001
-14

10.014
T
Timeout - The operation has timed out

• http://pielmed.com/
2607:f1c0:100f:f000::2e0 GZip used - 197 / 229 - 13.97 %
200

Html is minified: 112.25 %
0.313
H
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Date: Tue, 14 Jan 2020 10:20:34 GMT
Server: Apache
Last-Modified: Wed, 03 Jul 2019 02:46:49 GMT
ETag: W/"e5-58cbddf7f17f5"
Content-Encoding: gzip

• http://www.pielmed.com/
2604:a880:2:d1::1a4:8001
-14

10.030
T
Timeout - The operation has timed out

• http://www.pielmed.com/
2607:f1c0:100f:f000::2e0 GZip used - 197 / 229 - 13.97 %
200

Html is minified: 112.25 %
0.297
H
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Date: Tue, 14 Jan 2020 10:20:44 GMT
Server: Apache
Last-Modified: Wed, 03 Jul 2019 02:46:49 GMT
ETag: W/"e5-58cbddf7f17f5"
Content-Encoding: gzip

• https://pielmed.com/
167.172.123.53 No GZip used - 500 / 613 - 81.57 % possible
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 1/120
200

Html is minified: 130.43 %
5.593
B
Server: nginx/1.17.7
Date: Tue, 14 Jan 2020 10:20:45 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 613
Connection: close
Last-Modified: Thu, 09 Jan 2020 16:30:16 GMT
ETag: "5e175518-265"
Accept-Ranges: bytes

• https://pielmed.com/
2604:a880:2:d1::1a4:8001
-14

10.030
T
Timeout - The operation has timed out

• https://pielmed.com/
2607:f1c0:100f:f000::2e0
-10

0.296
P
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

• https://www.pielmed.com/
167.172.123.53 No GZip used - 500 / 613 - 81.57 % possible
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 1/120
200

Html is minified: 130.43 %
5.576
N
Certificate error: RemoteCertificateNameMismatch
Server: nginx/1.17.7
Date: Tue, 14 Jan 2020 10:20:51 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 613
Connection: close
Last-Modified: Thu, 09 Jan 2020 16:30:16 GMT
ETag: "5e175518-265"
Accept-Ranges: bytes

• https://www.pielmed.com/
2604:a880:2:d1::1a4:8001
-14

10.047
T
Timeout - The operation has timed out

• https://www.pielmed.com/
2607:f1c0:100f:f000::2e0
-10

0.297
P
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

• http://pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
167.172.123.53
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
301
https://pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 109.03 %
0.360
A
Visible Content: 301 Moved Permanently nginx/1.17.7
Server: nginx/1.17.7
Date: Tue, 14 Jan 2020 10:21:21 GMT
Content-Type: text/html
Content-Length: 169
Connection: close
Location: https://pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• http://www.pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
167.172.123.53
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
301
https://pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 109.03 %
0.360
E
Visible Content: 301 Moved Permanently nginx/1.17.7
Server: nginx/1.17.7
Date: Tue, 14 Jan 2020 10:21:22 GMT
Content-Type: text/html
Content-Length: 169
Connection: close
Location: https://pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• http://pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2604:a880:2:d1::1a4:8001
-14

10.027
T
Timeout - The operation has timed out
Visible Content:

• http://pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2607:f1c0:100f:f000::2e0
204

0.640
A
Visible Content:
Connection: close
Server: nginx/1.10.3
Date: Tue, 14 Jan 2020 10:21:33 GMT
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: 0
X-Frame-Options: DENY

• http://www.pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2604:a880:2:d1::1a4:8001
-14

10.016
T
Timeout - The operation has timed out
Visible Content:

• http://www.pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2607:f1c0:100f:f000::2e0
204

0.657
A
Visible Content:
Connection: close
Server: nginx/1.10.3
Date: Tue, 14 Jan 2020 10:21:43 GMT
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: 0
X-Frame-Options: DENY

• https://pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

-10

0.290
P
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.
Visible Content:

7. Comments

Aname "pielmed.com" is domain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
Agood: All ip addresses are public addresses
Agood: No asked Authoritative Name Server had a timeout
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):2 complete Content-Type - header (4 urls)
http://pielmed.com/ 2607:f1c0:100f:f000::2e0


Url with incomplete Content-Type - header - missing charset
http://www.pielmed.com/ 2607:f1c0:100f:f000::2e0


Url with incomplete Content-Type - header - missing charset
Ahttp://pielmed.com/ 167.172.123.53
301
https://pielmed.com/
correct redirect http - https with the same domain name
Bhttps://pielmed.com/ 167.172.123.53
200

Missing HSTS-Header
Bhttps://www.pielmed.com/ 167.172.123.53
200

Missing HSTS-Header
CError - no preferred version www or non-www. Select one version as preferred version, then add a redirect https + not-preferred version to https + preferred version. Perhaps in your port 443 vHost something like "RewriteEngine on" + "RewriteCond %{SERVER_NAME} = example.com" + "ReWriteRule ^ https://www.example.com%{REQUEST_URI} [END,QSA,R=permanent]" (three rows, without the "). That should create a redirect https + example.com ⇒ https + www.example.com. Or switch both values to use the non-www version as your preferred version.
CError - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
Ehttp://www.pielmed.com/ 167.172.123.53
301
https://pielmed.com/
Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
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.
Khttp://pielmed.com/ 167.172.123.53, Status 301

http://pielmed.com/ 2604:a880:2:d1::1a4:8001, Status -14
configuration problem - different ip addresses with different status
Khttp://pielmed.com/ 167.172.123.53, Status 301

http://pielmed.com/ 2607:f1c0:100f:f000::2e0, Status 200
configuration problem - different ip addresses with different status
Khttp://www.pielmed.com/ 167.172.123.53, Status 301

http://www.pielmed.com/ 2604:a880:2:d1::1a4:8001, Status -14
configuration problem - different ip addresses with different status
Khttp://www.pielmed.com/ 167.172.123.53, Status 301

http://www.pielmed.com/ 2607:f1c0:100f:f000::2e0, Status 200
configuration problem - different ip addresses with different status
Khttp://pielmed.com/ 2604:a880:2:d1::1a4:8001, Status -14

http://pielmed.com/ 2607:f1c0:100f:f000::2e0, Status 200
configuration problem - different ip addresses with different status
Khttp://www.pielmed.com/ 2604:a880:2:d1::1a4:8001, Status -14

http://www.pielmed.com/ 2607:f1c0:100f:f000::2e0, Status 200
configuration problem - different ip addresses with different status
Khttps://pielmed.com/ 167.172.123.53, Status 200

https://pielmed.com/ 2604:a880:2:d1::1a4:8001, Status -14
configuration problem - different ip addresses with different status
Khttps://pielmed.com/ 167.172.123.53, Status 200

https://pielmed.com/ 2607:f1c0:100f:f000::2e0, Status -10
configuration problem - different ip addresses with different status
Khttps://www.pielmed.com/ 167.172.123.53, Status 200

https://www.pielmed.com/ 2604:a880:2:d1::1a4:8001, Status -14
configuration problem - different ip addresses with different status
Khttps://www.pielmed.com/ 167.172.123.53, Status 200

https://www.pielmed.com/ 2607:f1c0:100f:f000::2e0, Status -10
configuration problem - different ip addresses with different status
Khttps://pielmed.com/ 2604:a880:2:d1::1a4:8001, Status -14

https://pielmed.com/ 2607:f1c0:100f:f000::2e0, Status -10
configuration problem - different ip addresses with different status
Khttps://www.pielmed.com/ 2604:a880:2:d1::1a4:8001, Status -14

https://www.pielmed.com/ 2607:f1c0:100f:f000::2e0, Status -10
configuration problem - different ip addresses with different status
Khttp://pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 167.172.123.53, Status 301

http://pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2604:a880:2:d1::1a4:8001, Status -14
configuration problem - different ip addresses with different status
Khttp://pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 167.172.123.53, Status 301

http://pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2607:f1c0:100f:f000::2e0, Status 204
configuration problem - different ip addresses with different status
Khttp://www.pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 167.172.123.53, Status 301

http://www.pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2604:a880:2:d1::1a4:8001, Status -14
configuration problem - different ip addresses with different status
Khttp://www.pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 167.172.123.53, Status 301

http://www.pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2607:f1c0:100f:f000::2e0, Status 204
configuration problem - different ip addresses with different status
Khttp://pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2604:a880:2:d1::1a4:8001, Status -14

http://pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2607:f1c0:100f:f000::2e0, Status 204
configuration problem - different ip addresses with different status
Khttp://www.pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2604:a880:2:d1::1a4:8001, Status -14

http://www.pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2607:f1c0:100f:f000::2e0, Status 204
configuration problem - different ip addresses with different status
Nhttps://www.pielmed.com/ 167.172.123.53
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch
Phttps://pielmed.com/ 2607:f1c0:100f:f000::2e0
-10

Error creating a TLS-Connection: IANA TLS Alert No. 80, internal_error. An internal error unrelated to the peer or the correctness of the protocol (such as a memory allocation failure) makes it impossible to continue. SSL_ERROR_INTERNAL_ERROR_ALERT (Mozilla) / ERR_SSL_PROTOCOL_ERROR (Chrome)
Phttps://www.pielmed.com/ 2607:f1c0:100f:f000::2e0
-10

Error creating a TLS-Connection: IANA TLS Alert No. 80, internal_error. An internal error unrelated to the peer or the correctness of the protocol (such as a memory allocation failure) makes it impossible to continue. SSL_ERROR_INTERNAL_ERROR_ALERT (Mozilla) / ERR_SSL_PROTOCOL_ERROR (Chrome)
Phttps://pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
-10

Error creating a TLS-Connection: IANA TLS Alert No. 80, internal_error. An internal error unrelated to the peer or the correctness of the protocol (such as a memory allocation failure) makes it impossible to continue. SSL_ERROR_INTERNAL_ERROR_ALERT (Mozilla) / ERR_SSL_PROTOCOL_ERROR (Chrome)
AGood: Nameserver supports TCP connections: 8 good Nameserver
AGood: Nameserver supports Echo Capitalization: 8 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 good Nameserver
AGood: All SOA have the same Serial Number
AGood: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ns1058.ui-dns.biz,ns1059.ui-dns.org,ns1067.ui-dns.com,ns1125.ui-dns.de
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.
http://pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2604:a880:2:d1::1a4:8001
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. 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.
http://www.pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2604:a880:2:d1::1a4:8001
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. 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.
https://pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
-10

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.
http://pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2607:f1c0:100f:f000::2e0
204

Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 201, 202, 203 or 204. Creating a Letsencrypt certificate via http-01 challenge can't work. A http status 301-309 (Redirect to another domain or port 80 / 443) or a http status 404 - Not Found is expected, if the test file doesn't exist. Looks like the webserver isn't configured, perhaps it's an answer of your hoster. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2607:f1c0:100f:f000::2e0
204

Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 201, 202, 203 or 204. Creating a Letsencrypt certificate via http-01 challenge can't work. A http status 301-309 (Redirect to another domain or port 80 / 443) or a http status 404 - Not Found is expected, if the test file doesn't exist. Looks like the webserver isn't configured, perhaps it's an answer of your hoster. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2604:a880:2:d1::1a4:8001, Status -14

http://pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 167.172.123.53, Status 301
Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2607:f1c0:100f:f000::2e0, Status 204

http://pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 167.172.123.53, Status 301
Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2604:a880:2:d1::1a4:8001, Status -14

http://www.pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 167.172.123.53, Status 301
Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2607:f1c0:100f:f000::2e0, Status 204

http://www.pielmed.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 167.172.123.53, Status 301
Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
https://pielmed.com/ 167.172.123.53
200

Warning: https result with status 200 without GZip found. Add GZip support so the html content is compressed.
https://www.pielmed.com/ 167.172.123.53
200

Warning: https result with status 200 without GZip found. Add GZip support so the html content is compressed.
https://pielmed.com/ 167.172.123.53
200

Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
https://www.pielmed.com/ 167.172.123.53
200

Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
https://pielmed.com/ 167.172.123.53
200

Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
https://www.pielmed.com/ 167.172.123.53
200

Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
https://pielmed.com/ 167.172.123.53
200

Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
https://www.pielmed.com/ 167.172.123.53
200

Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
AInfo: Different Server-Headers found
ADuration: 131363 milliseconds, 131.363 seconds


8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
pielmed.com
167.172.123.53
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
pielmed.com
167.172.123.53
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN  Tls.1.2
Tls.1.1
Tls.1.0
no http/2 via ALPN Tls.1.2
Tls.1.1
Tls.1.0
Chain (complete)
1CN=pielmed.com

2CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US

www.pielmed.com
167.172.123.53
443
name does not match
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
www.pielmed.com
167.172.123.53
443
name does not match
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN  Tls.1.2
Tls.1.1
Tls.1.0
no http/2 via ALPN Tls.1.2
Tls.1.1
Tls.1.0
Chain (complete)
1CN=pielmed.com

2CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US


9. Certificates

1.
1.
CN=pielmed.com
09.01.2020
08.04.2020
expires in 78 days
pielmed.com - 1 entry
1.
1.
CN=pielmed.com
09.01.2020

08.04.2020
expires in 78 days
pielmed.com - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:03CE87B841A7036CB1DC56B442E8280200B5
Thumbprint:4DC0D13C2BC1224DAE90937B78760D81158AD2D2
SHA256 / Certificate:E8A1O/KL3EVfZ/8tAdJkIPRZ+Ub2fTusKEfmENwXbKA=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):bca50c614fa20ece6cd4d9ec960854643653f50e36e31c29829c0a12b523dd90
OCSP - Url:http://ocsp.int-x3.letsencrypt.org
OCSP - must staple:no
Certificate Transparency:yes


2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016
17.03.2021
expires in 421 days


2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016

17.03.2021
expires in 421 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0A0141420000015385736A0B85ECA708
Thumbprint:E6A3B45B062D509B3382282D196EFE97D5956CCB
SHA256 / Certificate:JYR9Zo608E/dQLErawdAxWfafQJDCOtsLJb+QdneIY0=
SHA256 hex / Cert (DANE * 0 1):25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d
SHA256 hex / PublicKey (DANE * 1 1):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
OCSP - Url:http://isrg.trustid.ocsp.identrust.com
OCSP - must staple:no
Certificate Transparency:no


3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000
30.09.2021
expires in 618 days


3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000

30.09.2021
expires in 618 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:44AFB080D6A327BA893039862EF8406B
Thumbprint:DAC9024F54D8F6DF94935FB1732638CA6AD77C13
SHA256 / Certificate:BocmAzGnJAPZCfEF5pvPDTLhvSST/8bZIG0RvNZ3Bzk=
SHA256 hex / Cert (DANE * 0 1):0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SHA256 hex / PublicKey (DANE * 1 1):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no



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 (Update 2020-01-11: Should now work again - code updated. Old message: currently no newer certificates - read Crt.sh has stopped - Letsencrypt-forum - may work next week again - 2019-12-02 - but I must check the code).

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0 /0 new
5
5
CN=Encryption Everywhere DV TLS CA - G2, OU=www.digicert.com, O=DigiCert Inc, C=US
0
0
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
2323859784
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-01-09 13:20:30
2020-04-08 12:20:30
pielmed.com
1 entries


2323818919
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-01-09 13:01:40
2020-04-08 12:01:40
pielmed.com
1 entries


2323809602
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-01-09 12:52:12
2020-04-08 11:52:12
pielmed.com
1 entries


2323460377
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-01-09 09:21:40
2020-04-08 08:21:40
pielmed.com
1 entries


2323456959
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-01-09 09:20:20
2020-04-08 08:20:20
pielmed.com
1 entries


749939541
leaf cert
CN=Encryption Everywhere DV TLS CA - G2, OU=www.digicert.com, O=DigiCert Inc, C=US
2018-08-19 22:00:00
2019-08-20 10:00:00
pielmed.com, www.pielmed.com
2 entries



11. Html-Content - Entries

Summary

Subresource Integrity (SRI)
DomainnameHtmlElementrel/property∑ size∑ problems∑ int.∑ ext.∑ Origin poss.∑ SRI ParseErrors∑ SRI valid∑ SRI missing
https://pielmed.com/
167.172.123.53
a

2

0






https://www.pielmed.com/
167.172.123.53
a

2

0






Details

DomainnameHtml-Elementname/equiv/ property/relhref/src/contentHttpStatusmsgStatus
https://pielmed.com/
167.172.123.53
a

http://nginx.com/


1
ok








a

http://nginx.org/


1
ok







https://www.pielmed.com/
167.172.123.53
a

http://nginx.com/


1
ok








a

http://nginx.org/


1
ok








12. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.pielmed.com
0

no CAA entry found
1
0
pielmed.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


13. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
pielmed.com

ok
1
0
www.pielmed.com

ok
1
0
_acme-challenge.pielmed.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.pielmed.com

Name Error - The domain name does not exist
1
0
_acme-challenge.pielmed.com.pielmed.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.pielmed.com.pielmed.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.pielmed.com.www.pielmed.com

Name Error - The domain name does not exist
1
0


14. Portchecks

Domain or IPPortDescriptionResultAnswer
pielmed.com
21
FTP



pielmed.com
21
FTP



pielmed.com
22
SSH
open
SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3

pielmed.com
22
SSH
open
SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3

pielmed.com
25
SMTP



pielmed.com
25
SMTP



pielmed.com
53
DNS



pielmed.com
53
DNS



pielmed.com
110
POP3



pielmed.com
110
POP3



pielmed.com
143
IMAP



pielmed.com
143
IMAP



pielmed.com
465
SMTP (encrypted)



pielmed.com
465
SMTP (encrypted)



pielmed.com
587
SMTP (encrypted, submission)



pielmed.com
587
SMTP (encrypted, submission)



pielmed.com
993
IMAP (encrypted)



pielmed.com
993
IMAP (encrypted)



pielmed.com
995
POP3 (encrypted)



pielmed.com
995
POP3 (encrypted)



pielmed.com
1433
MS SQL



pielmed.com
1433
MS SQL



pielmed.com
2082
cPanel (http)



pielmed.com
2082
cPanel (http)



pielmed.com
2083
cPanel (https)



pielmed.com
2083
cPanel (https)



pielmed.com
2086
WHM (http)



pielmed.com
2086
WHM (http)



pielmed.com
2087
WHM (https)



pielmed.com
2087
WHM (https)



pielmed.com
2089
cPanel Licensing



pielmed.com
2089
cPanel Licensing



pielmed.com
2095
cPanel Webmail (http)



pielmed.com
2095
cPanel Webmail (http)



pielmed.com
2096
cPanel Webmail (https)



pielmed.com
2096
cPanel Webmail (https)



pielmed.com
2222
DirectAdmin (http)



pielmed.com
2222
DirectAdmin (http)



pielmed.com
2222
DirectAdmin (https)



pielmed.com
2222
DirectAdmin (https)



pielmed.com
3306
mySql



pielmed.com
3306
mySql



pielmed.com
5224
Plesk Licensing



pielmed.com
5224
Plesk Licensing



pielmed.com
5432
PostgreSQL
open


pielmed.com
5432
PostgreSQL
open


pielmed.com
8080
Ookla Speedtest (http)



pielmed.com
8080
Ookla Speedtest (http)



pielmed.com
8080
Ookla Speedtest (https)



pielmed.com
8080
Ookla Speedtest (https)



pielmed.com
8083
VestaCP http



pielmed.com
8083
VestaCP http



pielmed.com
8083
VestaCP https



pielmed.com
8083
VestaCP https



pielmed.com
8443
Plesk Administration (https)



pielmed.com
8443
Plesk Administration (https)



pielmed.com
8447
Plesk Installer + Updates



pielmed.com
8447
Plesk Installer + Updates



pielmed.com
8880
Plesk Administration (http)



pielmed.com
8880
Plesk Administration (http)



pielmed.com
10000
Webmin (http)



pielmed.com
10000
Webmin (http)



pielmed.com
10000
Webmin (https)



pielmed.com
10000
Webmin (https)



www.pielmed.com
21
FTP



www.pielmed.com
21
FTP



www.pielmed.com
22
SSH
open
SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3

www.pielmed.com
22
SSH
open
SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3

www.pielmed.com
25
SMTP



www.pielmed.com
25
SMTP



www.pielmed.com
53
DNS



www.pielmed.com
53
DNS



www.pielmed.com
110
POP3



www.pielmed.com
110
POP3



www.pielmed.com
143
IMAP



www.pielmed.com
143
IMAP



www.pielmed.com
465
SMTP (encrypted)



www.pielmed.com
465
SMTP (encrypted)



www.pielmed.com
587
SMTP (encrypted, submission)



www.pielmed.com
587
SMTP (encrypted, submission)



www.pielmed.com
993
IMAP (encrypted)



www.pielmed.com
993
IMAP (encrypted)



www.pielmed.com
995
POP3 (encrypted)



www.pielmed.com
995
POP3 (encrypted)



www.pielmed.com
1433
MS SQL



www.pielmed.com
1433
MS SQL



www.pielmed.com
2082
cPanel (http)



www.pielmed.com
2082
cPanel (http)



www.pielmed.com
2083
cPanel (https)



www.pielmed.com
2083
cPanel (https)



www.pielmed.com
2086
WHM (http)



www.pielmed.com
2086
WHM (http)



www.pielmed.com
2087
WHM (https)



www.pielmed.com
2087
WHM (https)



www.pielmed.com
2089
cPanel Licensing



www.pielmed.com
2089
cPanel Licensing



www.pielmed.com
2095
cPanel Webmail (http)



www.pielmed.com
2095
cPanel Webmail (http)



www.pielmed.com
2096
cPanel Webmail (https)



www.pielmed.com
2096
cPanel Webmail (https)



www.pielmed.com
2222
DirectAdmin (http)



www.pielmed.com
2222
DirectAdmin (http)



www.pielmed.com
2222
DirectAdmin (https)



www.pielmed.com
2222
DirectAdmin (https)



www.pielmed.com
3306
mySql



www.pielmed.com
3306
mySql



www.pielmed.com
5224
Plesk Licensing



www.pielmed.com
5224
Plesk Licensing



www.pielmed.com
5432
PostgreSQL
open


www.pielmed.com
5432
PostgreSQL
open


www.pielmed.com
8080
Ookla Speedtest (http)



www.pielmed.com
8080
Ookla Speedtest (http)



www.pielmed.com
8080
Ookla Speedtest (https)



www.pielmed.com
8080
Ookla Speedtest (https)



www.pielmed.com
8083
VestaCP http



www.pielmed.com
8083
VestaCP http



www.pielmed.com
8083
VestaCP https



www.pielmed.com
8083
VestaCP https



www.pielmed.com
8443
Plesk Administration (https)



www.pielmed.com
8443
Plesk Administration (https)



www.pielmed.com
8447
Plesk Installer + Updates



www.pielmed.com
8447
Plesk Installer + Updates



www.pielmed.com
8880
Plesk Administration (http)



www.pielmed.com
8880
Plesk Administration (http)



www.pielmed.com
10000
Webmin (http)



www.pielmed.com
10000
Webmin (http)



www.pielmed.com
10000
Webmin (https)



www.pielmed.com
10000
Webmin (https)



167.172.123.53
21
FTP



167.172.123.53
21
FTP



167.172.123.53
22
SSH
open
SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3

167.172.123.53
22
SSH
open
SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3

167.172.123.53
25
SMTP



167.172.123.53
25
SMTP



167.172.123.53
53
DNS



167.172.123.53
53
DNS



167.172.123.53
110
POP3



167.172.123.53
110
POP3



167.172.123.53
143
IMAP



167.172.123.53
143
IMAP



167.172.123.53
465
SMTP (encrypted)



167.172.123.53
465
SMTP (encrypted)



167.172.123.53
587
SMTP (encrypted, submission)



167.172.123.53
587
SMTP (encrypted, submission)



167.172.123.53
993
IMAP (encrypted)



167.172.123.53
993
IMAP (encrypted)



167.172.123.53
995
POP3 (encrypted)



167.172.123.53
995
POP3 (encrypted)



167.172.123.53
1433
MS SQL



167.172.123.53
1433
MS SQL



167.172.123.53
2082
cPanel (http)



167.172.123.53
2082
cPanel (http)



167.172.123.53
2083
cPanel (https)



167.172.123.53
2083
cPanel (https)



167.172.123.53
2086
WHM (http)



167.172.123.53
2086
WHM (http)



167.172.123.53
2087
WHM (https)



167.172.123.53
2087
WHM (https)



167.172.123.53
2089
cPanel Licensing



167.172.123.53
2089
cPanel Licensing



167.172.123.53
2095
cPanel Webmail (http)



167.172.123.53
2095
cPanel Webmail (http)



167.172.123.53
2096
cPanel Webmail (https)



167.172.123.53
2096
cPanel Webmail (https)



167.172.123.53
2222
DirectAdmin (http)



167.172.123.53
2222
DirectAdmin (http)



167.172.123.53
2222
DirectAdmin (https)



167.172.123.53
2222
DirectAdmin (https)



167.172.123.53
3306
mySql



167.172.123.53
3306
mySql



167.172.123.53
5224
Plesk Licensing



167.172.123.53
5224
Plesk Licensing



167.172.123.53
5432
PostgreSQL
open


167.172.123.53
5432
PostgreSQL
open


167.172.123.53
8080
Ookla Speedtest (http)



167.172.123.53
8080
Ookla Speedtest (http)



167.172.123.53
8080
Ookla Speedtest (https)



167.172.123.53
8080
Ookla Speedtest (https)



167.172.123.53
8083
VestaCP http



167.172.123.53
8083
VestaCP http



167.172.123.53
8083
VestaCP https



167.172.123.53
8083
VestaCP https



167.172.123.53
8443
Plesk Administration (https)



167.172.123.53
8443
Plesk Administration (https)



167.172.123.53
8447
Plesk Installer + Updates



167.172.123.53
8447
Plesk Installer + Updates



167.172.123.53
8880
Plesk Administration (http)



167.172.123.53
8880
Plesk Administration (http)



167.172.123.53
10000
Webmin (http)



167.172.123.53
10000
Webmin (http)



167.172.123.53
10000
Webmin (https)



167.172.123.53
10000
Webmin (https)





Permalink: https://check-your-website.server-daten.de/?i=237a150d-24e1-4ce5-a404-85b3a1580687


Last Result: https://check-your-website.server-daten.de/?q=pielmed.com - 2020-01-14 11:19:46


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

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