SSL/TLS Certificate Setup

Our company is engaged in the development, support and maintenance of sites of any complexity. From simple one-page sites to large-scale cluster systems built on micro services. Experience of developers is confirmed by certificates from vendors.
Development and maintenance of all types of websites:
Informational websites or web applications
Business card websites, landing pages, corporate websites, online catalogs, quizzes, promo websites, blogs, news resources, informational portals, forums, aggregators
E-commerce websites or web applications
Online stores, B2B portals, marketplaces, online exchanges, cashback websites, exchanges, dropshipping platforms, product parsers
Business process management web applications
CRM systems, ERP systems, corporate portals, production management systems, information parsers
Electronic service websites or web applications
Classified ads platforms, online schools, online cinemas, website builders, portals for electronic services, video hosting platforms, thematic portals

These are just some of the technical types of websites we work with, and each of them can have its own specific features and functionality, as well as be customized to meet the specific needs and goals of the client.

Our competencies:
Development stages
Latest works
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1161
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1041
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    822
  • image_crm_chasseurs_493_0.webp
    CRM development for Chasseurs
    847
  • image_website-sbh_0.png
    Website development for SBH Partners
    999
  • image_website-_0.png
    Website development for Red Pear
    451

SSL/TLS Certificate Setup

SSL/TLS certificate enables HTTPS: encrypts traffic between browser and server. Without it, browsers show "Insecure connection" warning, Google lowers rankings, modern APIs (PWA, Web Push, Geolocation) become unavailable.

Certificate Types

Type Verification When to Use
DV (Domain Validation) Domain only Most websites
OV (Organization Validation) Domain + organization Corporate websites
EV (Extended Validation) Extended verification Banks, payment systems
Wildcard *.example.ru All subdomains Multi-subdomain architecture
Multi-domain (SAN) Multiple domains Multiple websites

For most websites: Let's Encrypt DV (free) or paid DV from Comodo/Sectigo.

Nginx Setup

server {
    listen 443 ssl http2;
    server_name example.ru www.example.ru;

    ssl_certificate     /etc/letsencrypt/live/example.ru/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/example.ru/privkey.pem;

    # Recommended TLS settings
    ssl_protocols TLSv1.2 TLSv1.3;
    ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384;
    ssl_prefer_server_ciphers off;

    # HSTS — tell browser to use only HTTPS
    add_header Strict-Transport-Security "max-age=63072000; includeSubDomains; preload" always;

    # OCSP Stapling — speed up certificate verification
    ssl_stapling on;
    ssl_stapling_verify on;
    resolver 8.8.8.8 1.1.1.1 valid=300s;
    ssl_trusted_certificate /etc/letsencrypt/live/example.ru/chain.pem;

    # Session cache for faster handshake
    ssl_session_cache shared:SSL:10m;
    ssl_session_timeout 1d;
    ssl_session_tickets off;
}

# HTTP → HTTPS redirect
server {
    listen 80;
    server_name example.ru www.example.ru;
    return 301 https://example.ru$request_uri;
}

Paid Certificate Installation

# 1. Generate CSR (Certificate Signing Request)
openssl req -new -newkey rsa:2048 -nodes \
    -keyout example.ru.key \
    -out example.ru.csr \
    -subj "/C=RU/ST=Moscow/L=Moscow/O=Company Ltd/CN=example.ru"

# 2. Upload CSR to CA panel
# 3. Complete verification (DNS record or file)
# 4. Get certificate (fullchain.crt) and install

# Nginx: path to certificate
ssl_certificate /etc/ssl/example.ru/fullchain.crt;
ssl_certificate_key /etc/ssl/example.ru/example.ru.key;

Verification

  • SSL Labs — full TLS configuration analysis, target: A+ rating
  • openssl s_client -connect example.ru:443 — check in terminal
  • curl -vI https://example.ru — check headers and TLS

Timeline: few hours for Let's Encrypt; 1–3 days for paid OV/EV with verification.