Share! 366 Tool Online Answer Domain Name Blocked by Wechat What are the Reasons, Wechat Domain Name Blocking Scheme What are

Posted by totof06 on Mon, 27 May 2019 20:19:23 +0200

Recently, more and more website domain names have been blocked by Wechat's detection system, some of which are indeed illegal, and some of which have been misreported. When such a problem arises, the flow of products will be cleared in an instant, which is the same blow to all businesses. Is there any way that we can effectively prevent domain names from being blocked by micro-envelopes? It has been proved by the small edition research that there must be some. Of course, the most effective way to prevent blocking is to abide by the Wechat Regulation, without inducing sharing or wiping the edge ball. But now there are several products that can do this. If they can abide by the Regulation, I don't need to share this article.

Then why did Xiaobian study this aspect? In fact, in the recent process of Wechat marketing (registration, bargaining) for customers, I often met with the real and effective activities, but in the middle of the activities, the domain name was blocked, which made the company and users headache and fruitless, and so on. It was half a month later, the real grievance was solved. However, our competitors were able to promote it comfortably, which stimulated my exploratory desire, and then I was asked to know that they used it. 366TooL The anti-sealing technology will have such a good effect. Facts have proved that people's products have been on the right track to promote, and our products are still struggling in the application for unlocking domain names, so we realize the importance of domain name anti-blocking. I wrote this article to share some of my own research experience and experience in domain name blocking.

First of all, we need to know why your domain name is blocked by Wechat.

1. Wechat will have a systematic detection, as long as it detects that your domain name has the content of induced sharing, * x, edge ball (* x, false information, etc.), it will automatically intercept.
2. Peer or user report too many times, trigger the Wechat team to manually detect, and manually block your domain name.
3. Share and forward too much, trigger system automatic detection, when detected content violations, will be blocked.
4. Usually as long as Wechat background or manual detection of subject infringement, content infringement, violent content, promotion, marketing information, advertising content, false information content, harassment content, misleading content, will add your domain name to the blacklist, user access will prompt "the page has stopped visiting".


Then I'll share with you what we've developed. 366TooL The anti-sealing principle of the platform!

1. Detection of Wechat Domain Name and Switching of Domain Name

First, you need to have a Wechat domain name detection interface, configure your interface request procedures, prepare two sets of domain names A and B. The domain name we share is A, but when we click on it, we jump to B. The premise is to check whether B is sealed or not. Here, we need to prepare dozens or even hundreds of B. Using domain name detection interface, we can easily realize automatic switching between sealed and blocked domains.

2. Multilevel Matrix Encryption Jump
It should be noted here that the domain name of the landing page is as long as possible, and the last. html is made dynamic as possible. This way will still use the first detection + switching interface, and this anti-blocking effect is better and the stability will be higher. Share a passage we cracked 366TooL Code for your reference:

$url = "http://www.366tool.com";
$params = array(
'appkey' =>'appkey',//The APKEY you applied for
'url' =>'www.366tool.com',//Websites to be queried
);

$paramstring = http_build_query($params);
$content = go51wCurl($url, $paramstring);
$result = json_decode($content, true);
if($result) {
    var_dump($result);
}else {
    //Request exception
}


/**
    * Request interface returns content
    * @param    string $url [Request URL address]
    * @param    string $params [Request parameters]
    * @param    int $ipost [Is POST used or not?
    * @return    string
*/
function go51wCurl($url, $params = false, $ispost = 0)
{
    $httpInfo = array();
    $ch = curl_init();

    curl_setopt($ch, CURLOPT_HTTP_VERSION, CURL_HTTP_VERSION_1_1);
    curl_setopt($ch, CURLOPT_CONNECTTIMEOUT, 60);
    curl_setopt($ch, CURLOPT_TIMEOUT, 60);
    curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
    curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
    if ($ispost) {
        curl_setopt($ch, CURLOPT_POST, true);
        curl_setopt($ch, CURLOPT_POSTFIELDS, $params);
        curl_setopt($ch, CURLOPT_URL, $url);
    }else {
        if ($params) {
            curl_setopt($ch, CURLOPT_URL, $url.'?'.$params);
        } else {
            curl_setopt($ch, CURLOPT_URL, $url);
        }
    }

    $response = curl_exec($ch);
        if ($response === FALSE) {
        //echo "cURL Error: " . curl_error($ch);
        return false;
    }

    $httpCode = curl_getinfo($ch, CURLINFO_HTTP_CODE);
    $httpInfo = array_merge($httpInfo, curl_getinfo($ch));
    curl_close($ch);
    return $response;
}


Topics: curl