Hello! Some individuals do nothing and ... get real income. Without initial capital, starting from absolute zero. And everyone can repeat their experience, even you. This requires desire, luck and a little patience. I'll tell you about a profitable business built on pseudo-sites.
What are pseudo-sites?
A pseudo-site is nothing more than a well-made resource that has an automated credit card payment system. But unlike projects that regularly send goods after payment, a pseudo-resource completely inhumanly dynamites the buyer by placing credit card data in a separate database. With a serious approach to business, a pseudo-site can bring a carder mind-boggling income. This is because online stores (or porn galleries) are very popular among stupid but rich bourgeois people, for whom online shopping is the norm of life.
What should we build a website for?
To build a pseudo-site, you need to find the software engine for it. It consists of separate html pages (payment forms) and scripts that process the entered information. Engine authors use two methods to store the received data:
Conveniently, dcshop works under both UNIX and NT platforms. In addition to this, it is provided with a detailed manual and a bunch of default configs.
In order for the store to function, the hosting service requires:
Although dcshop does not use a database (writes to separate files), it is just right, since not every free hosting service provides access to the database (but there are pleasant exceptions, for example, www.spaceports.com).
Delivery and installation
The engine consists of three scripts: a store with shopping cart support, an admin area, and a script for requesting credit card information. Each script has its own configuration file.
First, set up the .setup config, where you need to change several variable values and directory paths. The main variable in the config is $cgidir, it points to the cgi-bin directory, where most of the engine scripts will be located. The best option is to create a subfolder in the scripts folder and define store scripts in it. For example, the value of $cgidir can be "/home/carder/web/cgi-bin/eshop".
Then there are the paths that depend on $cgidir. It is better not to change them, so that there is no confusion when uploading files to the server. The $order_database variable following them leads to the most interesting file, for which we install the dcshop project. This is a database of credit cards, or rather, this document will dump all information about bourgeois loans. The default value of the variable is "orders.txt", and this file is located at the path specified in the $order_dir variable. I recommend changing the paths to more complex ones, otherwise the database will be accessible via the web.
The $templatefile variable is responsible for the main html file that will be loaded after the dcshop.cgi script is executed. In this file, you can put your copyright, or convince the bourgeoisie of the legality of your commercial activities.
Then specify the path to the sendmail binary. It is usually located in the /usr/sbin directory, otherwise the location will be specified by the hosting administration. This variable is set so that after a successful order, the customer receives a payment acceptance email. At the same time, change the address of the smtp server, the address from which the message will be sent, and its subject (for example,smtp.spaceports.com).
In the next section of the config, absolute paths to the site are set. Let's say you were given a domain shop.hosting.net. Based on this, change the $cgiurl and $mainurl variables to the values for the html and cgi-bin directories, respectively, for example, http://shop.hosting.net/cgi-bin/eshop. In the same place, specify the path to the images (they will be located in the directory for html files).
The project implies the presence of an https server, but I strongly doubt that free hosting offers https. If yours is not an exception to the rule, then make the values of $secureurl and $secureimgurl equal to $cgiurl and $mainurl. At the end of the section, enter the project administrator's email address.
This, in fact, is the end of the default setting. Additionally, you can (strongly advise) redefine the paths to default scripts. Then, if bugs are found in the dcshop project, your resource will not be hacked (without knowing the new paths). So, change the values of $dcscript, $checkout_script, and $adminscript. Open the dcshop.cgi script and change the path to the config in the require line. And rename the config. If you encounter any problems, you can find out about this in the project's FAQ and in the readme file.
Honing the rest of the scripts
In addition to the main config, there are setup files for the checkout and admin scripts. In the checkout config, change the default html templates to something more beautiful (I personally didn't like the word "demo" in the text). And in dcshop_admin. setup, you will have to change the path to the directory where the administrator password is stored. I recommend that you block access to the directory with the specified file (which is why you need support).htaccess files), because a knowledgeable person will be able to see the contents of the directory, and therefore the file with the password.
Proper transportation
It's time to transfer the files to the FTP server. First, create a directory for html files, as well as a nested Images directory (pay attention to case). Then transfer all default images to this folder. Go to cgi-bin / eshop, fill in all configs and scripts in this directory. Caveat — you need to fill in ASCII mode, otherwise the scripts will not work. Just a little bit remains — put 777 rights on all directories, and on files .pl and .cgi-755.
It's time to test the result. Go to the main script of the store dcshop. cgi. If everything is correct, then the store will function without any side miscarriages. If it returns an error of 500, find out the reason why the script doesn't work. To do this, create a file .htaccess in the WWW root with the following content:
<Directory "/path/to/www">
ErrorLog «/path/to/www/error.log»
</Directory>
After that, access the script again and read the log contents in the html directory. Perhaps you just forgot to fill in a file or change the default path.
Now start with the admin script. So that no one will fuck you or steal a large database of new credit cards, go to the admin area and register under a new user with administrator rights. After that, click on the link "Change Configuration Setting" and prohibit the registration of new users. Drive to your health with your online store.
It makes sense to create a separate directory for the admin area and close it with additional authorization (out of harm's way). This is easily done using standard Apache tools. First you need to create one .htaccess file in the folder with the admin script. In it, write the following:
AuthType Basic
AuthName «Admin zone»
AuthUserFile «/path/to/.htpasswd»
Require valid-user
Then create it .htpasswd, which records the account as a login
assword pair. Acceptable password encryption algorithms: DES, MD5, SHA, and Plain text. The htpasswd utility included with Apache can encode passwords. The MD5 algorithm is supported by all versions of the web server and is the most reliable. The password is set with the htpasswd-bcm command. htpasswd admin myp4ssw0rd. The-bcm option means writing the MD5 password to a new one .htpasswd.
Rights to .htaccess and .set htpasswd to 600. This will only allow you to change them, and other vagrants will not have access to these important files.
Building a business
Now you need to change the default products. If you have nothing wrong with your imagination, you can easily come up with products that rich and stupid foreigners will want to buy. But first you need to understand the structure of the product database.
You can set several parameters in the product file (no matter which one). These are the ID (ID), Category( Category), product name (Name), Image (Image), description (Description), price (Price) and sales tax (Taxable). Additionally, there are some optional parameters, such as color and style. Read about them in the file readme.txt. You score data, and they are automatically placed in the Data folder relative to the cgi-bin / directory.
The installation script with brief information about this product category is also stored in the same directory. Conveniently, the engine includes four ready-made samples. So, just make a similar template for the product category and go ahead.
The database is still better
Writing your own engine with DB support is not so difficult. You need to know the principles of communication between the client (project script) and the server (MySQL database) that you will have access to. It is not necessary to write a separate engine, just make some changes to the dcshop code and teach it how to handle the database.
Using a special module DBI.pm you can work with MySQL (this is the database that rules on most hosting sites). You will need three things: the ability to connect to the database, insert and change data in it, and read information from the necessary tables in the database. To remake the file engine, all you need to do is replace the file request with a database request. You can download code snippets that implement proper work with MySQL (the code is provided with detailed comments) at http://kamensk.net.ru/forb/1/x/mysql-code.
The law is the law
Your resource will be closed sometime. This will most likely happen after the hosting support service receives a complaint from another inflated client. Therefore, you can use a few useful tips so that the consequences of closing the project do not affect your health:
You're a carder now
That's all. Pseudo-business is a very profitable business, because all the earned credit cards go only to you. Dozens or even hundreds of rich bourgeois people can visit such a resource every day (depending on the promotion). But there is a certain amount of risk involved in organizing such projects, otherwise everyone would have made online stores and lived off the bourgeoisie. Therefore, if you earn a decent amount of money and decided to create a pseudo-site just out of curiosity, think at your leisure whether you should spend your nerves and money on illegal activities.…
Resource promotion
Making a pseudo-site is half the battle, you also need to promote it. Otherwise, your resource will get dusty and will not bring any benefit. To attract visitors, of course, all means are good, but not all are effective. In a good way, if you plan to earn decent money on the resource, you will first have to spend money on promotion.
First of all, keep in mind that your main audience is foreigners. Therefore, the ad is designed for them. Most likely, the resource itself will have to be made in English, or in Russian and English at the same time. Next, you register the resource on search servers, and you are interested in both our search engines and foreign ones. Never bother searching for a complete list of search servers, just know one large one (for example, www.yandex.ru or www.rambler.ru), and you can find the rest directly through it.
The focus on redirecting traffic from other porn resources is often effective. In other words, a porn server is created, promoted alone, and then any other servers are promoted using this server. How exactly to do this is a matter of technique: redirect part of the visits, load them in parallel, or use trap links. At the same time, counters of rating systems are placed on the promoted resource, and it soars to the skies. And then it's like an avalanche. Further, the promoted resource, in turn, can be used to promote the next one.
Some craftsmen specifically create resources to offer others promotion for money. You can also find similar resources on a mutual promotion basis. That is, at first they promote you, and in the future you will exchange traffic, mutually increasing the number of real visits on your sites.
Banner ads are another effective way to attract potential buyers to your pseudo-resource. You don't have to set the banner system code.You can buy out impressions on the secondary market, which is sometimes very profitable. The secondary market for banner impressions is essentially traffic-generating resources registered in banner networks. They spend some of their impressions on their own promotion, and sell some of them on the so-called secondary banner display market. There is also an option to sell impressions directly to the banner network, but prices will be lower, plus not all banner networks buy back their impressions, or they buy back only on certain (most often unfavorable) terms.
To buy banner impressions on the secondary market, you will need a banner exchange, where you can determine the prices (average on the exchange) for certain banner networks and banner formats, plus buy the necessary impressions, if they are available. One of the most popular banner exchanges — www.banstock.com. There you will find an FAQ and statistics on the most popular (read — in-demand) banner networks and formats, and one day you will be able to sell banner impressions to other novice resources through it.
That's it! Successful robberies of the bourgeoisie! Buy ads!
- What are pseudo-sites?
- What should we build a website for?
- Delivery and installation
- Honing the rest of the scripts
- Proper transportation
- Building a business
- The database is still better
- The law is the law
- You're a carder now
- Resource promotion
What are pseudo-sites?
A pseudo-site is nothing more than a well-made resource that has an automated credit card payment system. But unlike projects that regularly send goods after payment, a pseudo-resource completely inhumanly dynamites the buyer by placing credit card data in a separate database. With a serious approach to business, a pseudo-site can bring a carder mind-boggling income. This is because online stores (or porn galleries) are very popular among stupid but rich bourgeois people, for whom online shopping is the norm of life.
What should we build a website for?
To build a pseudo-site, you need to find the software engine for it. It consists of separate html pages (payment forms) and scripts that process the entered information. Engine authors use two methods to store the received data:
- Through a database (DB). This method eliminates many problems that a user of the engine may encounter. To work successfully, you just need to create a database and a couple of tables. Then the scripts themselves will access the database and request/save data.
- Via files. All free engines are distributed with this algorithm. Here you will have to work hard, changing the default values of paths in the script configs. Do not forget about the access rights to the files to which the information will be recorded (set manually).
Conveniently, dcshop works under both UNIX and NT platforms. In addition to this, it is provided with a detailed manual and a bunch of default configs.
In order for the store to function, the hosting service requires:
- Access to the FTP server;
- WWW server with cgi scripting support;
- support for your own data is desirable .htaccess files;
- SSH access is desirable, which will allow you to install and change dcshop settings directly from the shell without any problems.
Although dcshop does not use a database (writes to separate files), it is just right, since not every free hosting service provides access to the database (but there are pleasant exceptions, for example, www.spaceports.com).
Delivery and installation
The engine consists of three scripts: a store with shopping cart support, an admin area, and a script for requesting credit card information. Each script has its own configuration file.
First, set up the .setup config, where you need to change several variable values and directory paths. The main variable in the config is $cgidir, it points to the cgi-bin directory, where most of the engine scripts will be located. The best option is to create a subfolder in the scripts folder and define store scripts in it. For example, the value of $cgidir can be "/home/carder/web/cgi-bin/eshop".
Then there are the paths that depend on $cgidir. It is better not to change them, so that there is no confusion when uploading files to the server. The $order_database variable following them leads to the most interesting file, for which we install the dcshop project. This is a database of credit cards, or rather, this document will dump all information about bourgeois loans. The default value of the variable is "orders.txt", and this file is located at the path specified in the $order_dir variable. I recommend changing the paths to more complex ones, otherwise the database will be accessible via the web.
The $templatefile variable is responsible for the main html file that will be loaded after the dcshop.cgi script is executed. In this file, you can put your copyright, or convince the bourgeoisie of the legality of your commercial activities.
Then specify the path to the sendmail binary. It is usually located in the /usr/sbin directory, otherwise the location will be specified by the hosting administration. This variable is set so that after a successful order, the customer receives a payment acceptance email. At the same time, change the address of the smtp server, the address from which the message will be sent, and its subject (for example,smtp.spaceports.com).
In the next section of the config, absolute paths to the site are set. Let's say you were given a domain shop.hosting.net. Based on this, change the $cgiurl and $mainurl variables to the values for the html and cgi-bin directories, respectively, for example, http://shop.hosting.net/cgi-bin/eshop. In the same place, specify the path to the images (they will be located in the directory for html files).
The project implies the presence of an https server, but I strongly doubt that free hosting offers https. If yours is not an exception to the rule, then make the values of $secureurl and $secureimgurl equal to $cgiurl and $mainurl. At the end of the section, enter the project administrator's email address.
This, in fact, is the end of the default setting. Additionally, you can (strongly advise) redefine the paths to default scripts. Then, if bugs are found in the dcshop project, your resource will not be hacked (without knowing the new paths). So, change the values of $dcscript, $checkout_script, and $adminscript. Open the dcshop.cgi script and change the path to the config in the require line. And rename the config. If you encounter any problems, you can find out about this in the project's FAQ and in the readme file.
Honing the rest of the scripts
In addition to the main config, there are setup files for the checkout and admin scripts. In the checkout config, change the default html templates to something more beautiful (I personally didn't like the word "demo" in the text). And in dcshop_admin. setup, you will have to change the path to the directory where the administrator password is stored. I recommend that you block access to the directory with the specified file (which is why you need support).htaccess files), because a knowledgeable person will be able to see the contents of the directory, and therefore the file with the password.
Proper transportation
It's time to transfer the files to the FTP server. First, create a directory for html files, as well as a nested Images directory (pay attention to case). Then transfer all default images to this folder. Go to cgi-bin / eshop, fill in all configs and scripts in this directory. Caveat — you need to fill in ASCII mode, otherwise the scripts will not work. Just a little bit remains — put 777 rights on all directories, and on files .pl and .cgi-755.
It's time to test the result. Go to the main script of the store dcshop. cgi. If everything is correct, then the store will function without any side miscarriages. If it returns an error of 500, find out the reason why the script doesn't work. To do this, create a file .htaccess in the WWW root with the following content:
<Directory "/path/to/www">
ErrorLog «/path/to/www/error.log»
</Directory>
After that, access the script again and read the log contents in the html directory. Perhaps you just forgot to fill in a file or change the default path.
Now start with the admin script. So that no one will fuck you or steal a large database of new credit cards, go to the admin area and register under a new user with administrator rights. After that, click on the link "Change Configuration Setting" and prohibit the registration of new users. Drive to your health with your online store.
It makes sense to create a separate directory for the admin area and close it with additional authorization (out of harm's way). This is easily done using standard Apache tools. First you need to create one .htaccess file in the folder with the admin script. In it, write the following:
AuthType Basic
AuthName «Admin zone»
AuthUserFile «/path/to/.htpasswd»
Require valid-user
Then create it .htpasswd, which records the account as a login
assword pair. Acceptable password encryption algorithms: DES, MD5, SHA, and Plain text. The htpasswd utility included with Apache can encode passwords. The MD5 algorithm is supported by all versions of the web server and is the most reliable. The password is set with the htpasswd-bcm command. htpasswd admin myp4ssw0rd. The-bcm option means writing the MD5 password to a new one .htpasswd.Rights to .htaccess and .set htpasswd to 600. This will only allow you to change them, and other vagrants will not have access to these important files.
Building a business
Now you need to change the default products. If you have nothing wrong with your imagination, you can easily come up with products that rich and stupid foreigners will want to buy. But first you need to understand the structure of the product database.
You can set several parameters in the product file (no matter which one). These are the ID (ID), Category( Category), product name (Name), Image (Image), description (Description), price (Price) and sales tax (Taxable). Additionally, there are some optional parameters, such as color and style. Read about them in the file readme.txt. You score data, and they are automatically placed in the Data folder relative to the cgi-bin / directory.
The installation script with brief information about this product category is also stored in the same directory. Conveniently, the engine includes four ready-made samples. So, just make a similar template for the product category and go ahead.
The database is still better
Writing your own engine with DB support is not so difficult. You need to know the principles of communication between the client (project script) and the server (MySQL database) that you will have access to. It is not necessary to write a separate engine, just make some changes to the dcshop code and teach it how to handle the database.
Using a special module DBI.pm you can work with MySQL (this is the database that rules on most hosting sites). You will need three things: the ability to connect to the database, insert and change data in it, and read information from the necessary tables in the database. To remake the file engine, all you need to do is replace the file request with a database request. You can download code snippets that implement proper work with MySQL (the code is provided with detailed comments) at http://kamensk.net.ru/forb/1/x/mysql-code.
The law is the law
Your resource will be closed sometime. This will most likely happen after the hosting support service receives a complaint from another inflated client. Therefore, you can use a few useful tips so that the consequences of closing the project do not affect your health:
- When organizing a mini-porn gallery, no one will demand any responsibility from you if you make a start page with a warning about the client's age of majority.
- If things are going well, register a second-level domain and get a normal hoster. When your resource is deleted, you can easily change the dns zones of your domain when moving to another hosting service.
- Try to leave as little information about yourself as possible on the resource pages. You'd rather say you're some rich Chinese guy selling Parker pens than a poor Russian student.
- When moving, you will have to face such a problem as backing up all your data. This must be done in time, when you feel that the case smells of kerosene. If there are no problems with the files, it is a subtle (though not difficult) task to back up the database skillfully. This requires the help of a small mysqldump utility that is included with mysqlclient. You go to the shell of your hosting and type the command:
$ mysqldump -u client -pclientpassword eshop > eshop.sql
Accordingly, the account to the database should look like client: clientpassword, and the database should be called eshop. The binary file will form a table structure, which should be archived and transported to another hosting service. Compress better with the bzip archiver:
$ tar jcf eshop.tar.bz2 eshop.sql
On the new hosting, you need to unpack it and create a copy of the database structure (using the eshop.sql file). At the same time, you don't need to worry about creating tables and databases, mysqldump will do everything:
$ tar jxf eshop.tar.bz2 $ mysql -u client -pclientpassword < eshop.sql
By overriding input, you allow the mysql binary to get commands directly from the file. In our case, from the eshop.sql backup. - To get away with it, delete all files from the old hosting (of course, after a backup) and drop the database. This can be done with the "drop database eshop;" command in the mysql client.
You're a carder now
That's all. Pseudo-business is a very profitable business, because all the earned credit cards go only to you. Dozens or even hundreds of rich bourgeois people can visit such a resource every day (depending on the promotion). But there is a certain amount of risk involved in organizing such projects, otherwise everyone would have made online stores and lived off the bourgeoisie. Therefore, if you earn a decent amount of money and decided to create a pseudo-site just out of curiosity, think at your leisure whether you should spend your nerves and money on illegal activities.…
Resource promotion
Making a pseudo-site is half the battle, you also need to promote it. Otherwise, your resource will get dusty and will not bring any benefit. To attract visitors, of course, all means are good, but not all are effective. In a good way, if you plan to earn decent money on the resource, you will first have to spend money on promotion.
First of all, keep in mind that your main audience is foreigners. Therefore, the ad is designed for them. Most likely, the resource itself will have to be made in English, or in Russian and English at the same time. Next, you register the resource on search servers, and you are interested in both our search engines and foreign ones. Never bother searching for a complete list of search servers, just know one large one (for example, www.yandex.ru or www.rambler.ru), and you can find the rest directly through it.
The focus on redirecting traffic from other porn resources is often effective. In other words, a porn server is created, promoted alone, and then any other servers are promoted using this server. How exactly to do this is a matter of technique: redirect part of the visits, load them in parallel, or use trap links. At the same time, counters of rating systems are placed on the promoted resource, and it soars to the skies. And then it's like an avalanche. Further, the promoted resource, in turn, can be used to promote the next one.
Some craftsmen specifically create resources to offer others promotion for money. You can also find similar resources on a mutual promotion basis. That is, at first they promote you, and in the future you will exchange traffic, mutually increasing the number of real visits on your sites.
Banner ads are another effective way to attract potential buyers to your pseudo-resource. You don't have to set the banner system code.You can buy out impressions on the secondary market, which is sometimes very profitable. The secondary market for banner impressions is essentially traffic-generating resources registered in banner networks. They spend some of their impressions on their own promotion, and sell some of them on the so-called secondary banner display market. There is also an option to sell impressions directly to the banner network, but prices will be lower, plus not all banner networks buy back their impressions, or they buy back only on certain (most often unfavorable) terms.
To buy banner impressions on the secondary market, you will need a banner exchange, where you can determine the prices (average on the exchange) for certain banner networks and banner formats, plus buy the necessary impressions, if they are available. One of the most popular banner exchanges — www.banstock.com. There you will find an FAQ and statistics on the most popular (read — in-demand) banner networks and formats, and one day you will be able to sell banner impressions to other novice resources through it.
That's it! Successful robberies of the bourgeoisie! Buy ads!
