EN
+7 903 755-33-76

DELUXE · 11 topics

Security and recovery

Short answers about what we do, how it works and where to start, in plain language.

Security and recovery

Website security

Vulnerability

A weakness in software, permissions or configuration that can allow unauthorised access or changes. An assessment identifies the cause and the update, code fix or setting needed to address it.

Why it helps

In a CMS, extensions, custom code, permissions and server configuration. A flaw may allow unauthorised reading, changes or actions.

Where to start. Describe the symptoms and site address. Access is shared separately with the specialist.

Website security

Website malware

Malicious code added to a compromised website, such as unwanted redirects, spam tools, miners or phishing pages. Visible symptoms vary, so a clean-looking page does not prove the site is safe.

Why it helps

Unexpected redirects, unfamiliar pages, spam or warnings from a browser or host can indicate infection. A lack of visible symptoms does not establish that a site is clean: malicious behaviour can target selected visitors.

Where to start. Describe the symptoms and site address. Access is shared separately with the specialist.

Website security

WAF

A web application firewall filters requests using rules that can block common attack patterns. It adds a layer of protection but does not replace secure code, updates or access controls.

Why it helps

It filters HTTP requests using rules, such as detecting common injection patterns or limiting repeated sign-in attempts. It can run on a server, proxy or CDN.

Where to start. Describe the symptoms and site address. Access is shared separately with the specialist.

Website security

Two-factor authentication

An additional identity check alongside a password. It reduces account-takeover risk; security keys and passkeys offer stronger resistance to phishing than codes entered manually.

Why it helps

A password is combined with another confirmation, such as an authenticator code or a hardware key. A stolen password alone is then insufficient for normal sign-in.

Where to start. Describe the symptoms and site address. Access is shared separately with the specialist.

SSL and HTTPS

SSL certificate

A certificate links a domain to the server’s public key and supports encrypted HTTPS connections using TLS. It protects data in transit, without guaranteeing the safety of the website’s code or content.

Why it helps

A TLS certificate links a domain to a public key and lets the browser verify the server. SSL remains a familiar name, while modern connections use TLS. Encryption protects transport; it does not prove that the site owner is trustworthy.

Where to start. Describe the symptoms and site address. Access is shared separately with the specialist.

SSL and HTTPS

HTTPS

HTTP secured with TLS to protect data between the browser and server. It is essential for forms, sign-in and payments; server-side data security remains a separate responsibility.

Why it helps

It protects the browser-to-server connection against reading and modification in transit. This is essential for forms, sign-in and payments. Protecting information inside the server is a separate responsibility.

Where to start. Describe the symptoms and site address. Access is shared separately with the specialist.

SSL and HTTPS

“Not secure”

A browser warning about an insecure connection or a certificate problem. The page address and exact error identify the cause. Avoid submitting passwords or payment details until it is checked.

Why it helps

Possible causes include HTTP, an expired certificate, a domain mismatch or an untrusted certificate chain. Mixed content can be blocked separately. Diagnosis needs the address and exact error message.

Where to start. Describe the symptoms and site address. Access is shared separately with the specialist.

SSL and HTTPS

Let’s Encrypt

A certificate authority that provides free domain-validated certificates. An ACME client automates issuance and renewal, but that automation still needs maintenance and expiry checks.

Why it helps

It is a certificate authority offering free certificates after domain-control validation. An ACME client on the server or hosting panel automates issuance and renewal.

Where to start. Describe the symptoms and site address. Access is shared separately with the specialist.

SSL and HTTPS

TLS 1.3

A version of the protocol that protects HTTPS connections. It reduces handshake overhead and removes obsolete cryptographic options. Certificate installation and protocol configuration are related but separate tasks.

Why it helps

It is a version of the protocol securing HTTPS connections. It shortens the connection handshake and removes several obsolete cryptographic options. Certificates and protocol versions are related but separate settings.

Where to start. Describe the symptoms and site address. Access is shared separately with the specialist.

Website emergency care

Website recovery

Restoring a site after an outage, access loss or damaged data.

Why it helps

We preserve a copy and diagnose the cause first. A specialist confirms availability and the quote.

Where to start. Describe the symptoms and site address. Access is shared separately with the specialist.

Website security

Security audit

An agreed review of code, configuration and access, with the owner’s permission.

Why it helps

The result is a prioritised list of risks and fixes, rather than a promise of absolute protection.

Where to start. Describe the symptoms and site address. Access is shared separately with the specialist.