per ticket<\/a> and send them to us so we can add them for you.<\/p>\nWant a secure WordPress?<\/h2>\n
We take effective measures to improve the security of your WordPress site. That's why every time we deploy a new WordPress we perform the following optimizations:<\/p>\n
SECURE LOGIN<\/h3>\n
We create for you a login and a secure password for your Admin account.<\/p>\n
URL LOGIN & WP ADMIN<\/h3>\n
We change the login and wp-admin URLs that are often used for Brute Force attacks.<\/p>\n
LIMIT LOGIN<\/h3>\n
We limit the number of login attempts to protect your Admin account.<\/p>\n
NO HOTLINK<\/h3>\n
We apply a direct restriction from our server to protect your site from hotlinking and preserve the bandwidth allocated to it.<\/p>\n
CONSTANT MONITORING<\/h3>\n
We carry out a permanent watch against malicious code on your site and protect you against DDOS attacks.<\/p>\n
PROTECTION<\/h3>\n
We protect your site's files and folders by blocking navigation in your WordPress folders. Access rights are adjusted accordingly.<\/p>\n
MASKED<\/h3>\n
We hide in the code the version of your WordPress, because it gives information to hackers to find possible security holes.<\/p>\n
PREFIX WP<\/h3>\n
We change the default prefix \"WP_\" of the tables in the MYSQL database. Indeed, this prefix \"_WP\" is known by all and can be vulnerable in case of injection.<\/p>\n
USER ID<\/h3>\n
We change the default User ID of the first user. Indeed, the ID 1 is known by everyone and is often searched\/attacked by hackers.<\/p>\n
CONNECTION ERRORS<\/h3>\n
We hide the connection errors because WordPress returns a message that is far too explicit in case of connection problems.<\/p>\n
FILE EDITOR<\/h3>\n
We disable the internal file editor of WordPress. To edit your files, you will just have to use your FTP software.<\/p>\n
SECURITY WATCH<\/h3>\n
We keep a daily watch on the main WordPress security flaws and inform you directly by newsletter of the most critical ones.<\/p>\n
AND THAT'S NOT ALL<\/h3>\n
Server-side measures are also in place, proactive file scanning with immediate quarantine of suspicious files, and a few others that we are keeping secret.<\/p>","protected":false},"excerpt":{"rendered":"
The use of an .htaccess file is not possible, because it is incompatible with our NGINX servers. .htaccess files (and more broadly, files beginning with a dot) are indeed used on Apache, LiteSpeed and other servers. But on a NGINX server, there are other alternatives. What is...<\/p>","protected":false},"author":52,"comment_status":"open","ping_status":"closed","template":"","format":"standard","meta":{"footnotes":""},"ht-kb-category":[1246],"ht-kb-tag":[],"class_list":["post-7706","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-hebergements-cloud-evolution"],"_links":{"self":[{"href":"https:\/\/assistance.groupemagiconline.com\/en\/wp-json\/wp\/v2\/ht-kb\/7706","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/assistance.groupemagiconline.com\/en\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/assistance.groupemagiconline.com\/en\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/assistance.groupemagiconline.com\/en\/wp-json\/wp\/v2\/users\/52"}],"replies":[{"embeddable":true,"href":"https:\/\/assistance.groupemagiconline.com\/en\/wp-json\/wp\/v2\/comments?post=7706"}],"version-history":[{"count":0,"href":"https:\/\/assistance.groupemagiconline.com\/en\/wp-json\/wp\/v2\/ht-kb\/7706\/revisions"}],"wp:attachment":[{"href":"https:\/\/assistance.groupemagiconline.com\/en\/wp-json\/wp\/v2\/media?parent=7706"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/assistance.groupemagiconline.com\/en\/wp-json\/wp\/v2\/ht-kb-category?post=7706"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/assistance.groupemagiconline.com\/en\/wp-json\/wp\/v2\/ht-kb-tag?post=7706"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}