Digital exposure report
vtb.ru
Good shape, with a few gaps worth closing this quarter.
Scanned: 2026-11-20 07:34 UTC
Partial coverage: the score is based on 47% of applicable check weight. 9 unverified check(s) are excluded, not counted as failures.
What to do first
- 1.
Turn on DNS signing for your domain
Signing helps resolvers detect forged answers about your domain.
Who can fix it: Your domain registrar or DNS provider
How to verify after the fix
dig +short DS vtb.ru
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- vtb.ru
- Website request
- GET https://vtb.ru/
- Scan time
- 2026-11-20 07:34:38 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- DKIM — digital signature on email · Not detected (common selectors only)
- HTTPS available · Unverified
- SSL/TLS certificate validity · Unverified
- HSTS — enforce encryption in the browser · Unverified
- CSP — protection from script injection · Unverified
- Clickjacking protection · Unverified
- X-Content-Type-Options · Unverified
- Referrer-Policy · Unverified
- Permissions-Policy · Unverified
This is a snapshot of the public configuration checks listed in this report. It does not verify the site's owner, business legitimacy, application security, or absence of vulnerabilities. It is not a security certification.
Score by category
| Email security | 25/25 | Spoofing email from this domain is hard. |
| Encryption & certificate | 7/7 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | — | Nothing in this category could be verified from public data. |
| DNS infrastructure | 8/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.MediumDNSSEC — signed DNS records · Hardening gap+15
To verify
Couldn't be confirmed from public data, so excluded from the score. Checking them clarifies your posture; it doesn't guarantee a score change.
- HTTPS available
- SSL/TLS certificate validity
- CSP — protection from script injection
- HSTS — enforce encryption in the browser
- Clickjacking protection
- DKIM — digital signature on email
- X-Content-Type-Options
- Referrer-Policy
- Permissions-Policy
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 10/10An authorized sender list is defined and mail from other servers is rejected.
Valid SPF record with -all. 0 of the 10 allowed DNS lookups.
v=spf1 ip4:195.242.82.163 ip4:195.242.82.164 ip4:195.242.83.132 ip4:195.242.83.133 ip4:195.242.82.131 ip4:195.242.82.132 ip4:195.242.83.145 ip4:195.242.83.146 ip4:195.242.83.147 ip4:195.242.83.148 ip4:195.242.82.133 ip4:195.242.82.134 ip4:122.185.221.197 -all
$ dig +short TXT vtb.ru
DMARC — anti-spoofing policy
Passed · Severity: OK · 15/15Forged email in the company's name is blocked by mail servers.
Policy p=reject.
v=DMARC1; p=reject; sp=reject; pct=100; rua=mailto:dmarc@vtb.com; ruf=mailto:dmarc@vtb.com; fo=1; adkim=s; aspf=s
$ dig +short TXT _dmarc.vtb.ru
DKIM — digital signature on email
Not detected (common selectors only) · Severity: OK · Not scoredNo DKIM key was found under the common selectors we probed. That doesn't mean DKIM is missing — selectors can't be listed from public DNS. Not scored.
A missing name for a probed selector (NXDOMAIN/NODATA) only means that selector isn't published. DKIM is marked unverified and excluded from the score. Check a sent message's Authentication-Results for dkim=pass and its s= selector.
Selectors checked: google, selector1, selector2, default, k1, s1, s2, dkim, mail, smtp — no key found google._domainkey: nxdomain selector1._domainkey: nxdomain selector2._domainkey: nxdomain default._domainkey: nxdomain k1._domainkey: nxdomain s1._domainkey: nxdomain s2._domainkey: nxdomain dkim._domainkey: nxdomain mail._domainkey: nxdomain smtp._domainkey: nxdomain
$ dig +short TXT google._domainkey.vtb.ru
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
8 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
10 mx2003.vtb.ru 10 mx2004.vtb.ru 10 mx2005.vtb.ru 10 mx2006.vtb.ru 10 mx5003.vtb.ru 10 mx5004.vtb.ru 10 mx5005.vtb.ru 10 mx5006.vtb.ru
$ dig +short MX vtb.ru
HTTPS available
Unverified · Severity: OK · Not scoredHTTPS couldn't be confirmed: the request timed out or the connection failed. This isn't treated as a security failure.
Requesting https://vtb.ru/ didn't complete (HTTP 526). Timeouts and transport errors may be transient; the check is excluded from the score.
HTTP 526
$ curl -svI https://vtb.ru/ 2>&1 | grep -E "SSL|HTTP|expire"
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 302 → https://xn--90ab2c.xn--p1ai/
HTTP 302 Location: https://xn--90ab2c.xn--p1ai/
$ curl -sI http://vtb.ru/ | grep -iE "^(HTTP|location)"
SSL/TLS certificate validity
Unverified · Severity: OK · Not scoredThe certificate couldn't be checked live because the HTTPS connection didn't complete. CT log data alone isn't used to score validity or expiry.
No live TLS evidence was obtained. CT entries are shown as context only. Not scored.
CT logs (context only, not scored): Issuer: TrustAsia Technologies Valid from: 2026-07-17 Valid until: 2027-02-01 Names: *.vtb.ru, vtb.ru Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect vtb.ru:443 -servername vtb.ru 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Unverified · Severity: OK · Not scoredCouldn't be checked — no usable HTTPS response was obtained. Not scored.
No response with headers was received, so this header wasn't evaluated and is excluded from the score.
No HTTPS response received
$ curl -sIL https://vtb.ru/
CSP — protection from script injection
Unverified · Severity: OK · Not scoredCouldn't be checked — no usable HTTPS response was obtained. Not scored.
No response with headers was received, so this header wasn't evaluated and is excluded from the score.
No HTTPS response received
$ curl -sIL https://vtb.ru/
Clickjacking protection
Unverified · Severity: OK · Not scoredCouldn't be checked — no usable HTTPS response was obtained. Not scored.
No response with headers was received, so this header wasn't evaluated and is excluded from the score.
No HTTPS response received
$ curl -sIL https://vtb.ru/
X-Content-Type-Options
Unverified · Severity: OK · Not scoredCouldn't be checked — no usable HTTPS response was obtained. Not scored.
No response with headers was received, so this header wasn't evaluated and is excluded from the score.
No HTTPS response received
$ curl -sIL https://vtb.ru/
Referrer-Policy
Unverified · Severity: OK · Not scoredCouldn't be checked — no usable HTTPS response was obtained. Not scored.
No response with headers was received, so this header wasn't evaluated and is excluded from the score.
No HTTPS response received
$ curl -sIL https://vtb.ru/
Permissions-Policy
Unverified · Severity: OK · Not scoredCouldn't be checked — no usable HTTPS response was obtained. Not scored.
No response with headers was received, so this header wasn't evaluated and is excluded from the score.
No HTTPS response received
$ curl -sIL https://vtb.ru/
DNSSEC — signed DNS records
Needs attention · Severity: Medium · Hardening gap · 0/7The domain's records aren't signed, so in some scenarios users could be redirected to a forged server.
No DS record is published at the parent zone, so there's no DNSSEC chain of trust for this zone.
AD = false DS vtb.ru: NODATA
$ dig +short DS vtb.ru
- Enable DNSSEC at your DNS provider (one click at most providers).
- Copy the DS record your provider generates to your domain registrar.
- Wait for propagation and verify with DNSViz.
dig +dnssec vtb.ru SOA delv vtb.ru
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. A wrong DS record at the registrar will make the domain stop resolving — copy it exactly from the provider.
CAA — who may issue certificates
Passed · Severity: OK · 5/5Only authorized certificate authorities can issue certificates for the domain.
CAA records: 0 issue "certainly.com" | 0 issue "trustasia.com" | 0 issuewild "certainly.com" | 0 issuewild "trustasia.com"
0 issue "certainly.com" 0 issue "trustasia.com" 0 issuewild "certainly.com" 0 issuewild "trustasia.com"
$ dig +short CAA vtb.ru
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
6 NS servers.
ns1.vtb.ru ns2.vtb.ru ns3.vtb.ru ns4.vtb.ru ns5.vtb.ru ns6.vtb.ru
$ dig +short NS vtb.ru
Indicative alignment
Best-practice mapping of public findings to common frameworks. Passive scanning tests public configuration only; it doesn't prove compliance or a violation.
- Google & Yahoo sender rules1 unverified
- PCI DSS v4.05 unverified
- NIS2 / vendor due diligence1 observed gaps · 3 unverified
- SOC 2 / ISO 27001 baseline6 unverified
Indicative alignment only, based on public configuration. It doesn't establish whether a framework applies to you, and it isn't legal advice, an audit or a certification.
Public DNS records
| A | vtb.ru | 195.242.82.13 | 195.242.83.13 |
| AAAA | vtb.ru | — |
| MX | vtb.ru | 10 mx2003.vtb.ru | 10 mx2004.vtb.ru | 10 mx2005.vtb.ru | 10 mx2006.vtb.ru | 10 mx5003.vtb.ru | 10 mx5004.vtb.ru | 10 mx5005.vtb.ru | 10 mx5006.vtb.ru |
| NS | vtb.ru | ns1.vtb.ru | ns2.vtb.ru | ns3.vtb.ru | ns4.vtb.ru | ns5.vtb.ru | ns6.vtb.ru |
| TXT | vtb.ru | v=spf1 ip4:195.242.82.163 ip4:195.242.82.164 ip4:195.242.83.132 ip4:195.242.83.133 ip4:195.242.82.131 ip4:195.242.82.132 ip4:195.242.83.145 ip4:195.242.83.146 ip4:195.242.83.147 ip4:195.242.83.148 ip4:195.242.82.133 ip4:195.242.82.134 ip4:122.185.221.197 -all |
| TXT | _dmarc.vtb.ru | v=DMARC1; p=reject; sp=reject; pct=100; rua=mailto:dmarc@vtb.com; ruf=mailto:dmarc@vtb.com; fo=1; adkim=s; aspf=s |
| CAA | vtb.ru | 0 issue "certainly.com" | 0 issue "trustasia.com" | 0 issuewild "certainly.com" | 0 issuewild "trustasia.com" |
| DS | vtb.ru | — |