How many HTTPS encryption protocol ports are by default and whether port replacement access is supported

Lao Zuo saw that netizens in the group were discussing that some students' websites could not be accessed due to unclear reasons. His website does not use HTTPS, and it is impossible to access his HTTP directly. Through the ping test, we can see that the resolution address is messy, which should be the so-called DNS pollution. Some netizens mentioned to try using HTTPS encryption certificate. Because HTTP and HTTPS do not use the same port, some netizens have tested this before to alleviate this problem.

After the website is bound to HTTPS, it can be opened. It seems that port 80 of the website has a problem, while port 443 has no problem with HTTPS. However, there is another problem here. He cannot do 301 jump because most nodes' HTTP is polluted.

First, the HTTP and HTTPS ports

Generally, HTTP uses port 80, while HTTPS uses port 443. However, after binding the domain name, there is no port added behind the URL. We cannot see these two default ports, but they are already built-in. It belongs to the default protocol. If we use other ports, you will see that you must add a port after the URL or IP address to access.

Second, whether the HTTPS 443 port can be replaced

The student asked that he was worried that the HTTPS port would also be blocked. In fact, the port could be changed. But if we change to a port other than 443, we need to add a port after the URL or IP address. Is this a poor experience? Therefore, if the HTTPS of port 443 is also polluted and blocked, we'd better change the domain name, which is no fun.

In short, it is suggested that this student check the website for the problem of the polluted domain name. If necessary, you should put it on record at home. If there is a problem, someone will remind you. If there is bad content, you should try to remove it. After all, it is a long-term solution.