Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DURL VariantsActionwww/non-www, trailing slash, HTTP→HTTPSFIX
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
HTTP version does not redirect to HTTPS
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
CCrawlabilityActionrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.
Learn more ▾ ▴
Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.
Source: sitemaps.org / Google Search Central
An empty sitemap provides no value. Add <url> entries for your pages.
An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.
Learn more ▾ ▴
Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.
Source: Google Search Central / sitemaps.org
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
<html lang="ru"><head><title>sberbank.ru</title><meta charset="UTF-8"><script>document.addEventListener('DOMContentLoaded',function(){const eventData={serviceName:'waf',code:'user_blocked',details:{data:{error:{userAgent:navigator?.userAgent||'',referrer:document?.referrer||'', pageUrl: window.location.href }}}};fetch('https://www.sberbank.com/proxy/services/sberlogger/error',{method:'POST',headers:{'Content-Type':'application/json',},body:JSON.stringify(eventData),keepalive:true}).catch(function(error){console.error('Error sending analytics:',error);});});</script></head><body><p><i>Возникла проблема при открытии сайта Сбербанка в этом браузере.</i></p><p><i>Возможно у Вас не установлены сертификаты Национального УЦ Минцифры России.</i></p><p><i>Ознакомиться с инструкциями по установке можно на <a href="https://www.gosuslugi.ru/crt">https://www.gosuslugi.ru/crt</a></i></p><p><i>Либо попробуйте войти на сайт в другом браузере по ссылке <a href="https://www.sberbank.com/ru/certificates">https://www.sberbank.com/ru/certificates</a></i></p><p><i>Если ошибка повторится позвоните нам по номеру 900 или + 7495 500-55-50, если Вы за границей, и сообщите ваш Support ID</i><br><br>Support ID: <3124088932277399265><br><a href='javascript:history.back();'>[Назад]</body></html><br><br>
BTLS Certificate Expiry & Recommendations184 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- Enable DNSSEC on your domain for DNS spoofing protection
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
ADNS Records1 A records, 217 ms lookupPASS
| A | 84.252.149.206 |
| AAAA | — |
| CNAME | — |
| NS | ns1.sberbank.ru, ns2.gldn.net, ns3.gldn.net, ns4.sberbank.ru, nsq.sberbank.ru, tmp1.sberbank.ru, tmp2.sberbank.ru |
| MX | 50 email16.sberbank.ru 50 email14.sberbank.ru 50 email15.sberbank.ru 50 email13.sberbank.ru 80 email11.sberbank.ru 80 email12.sberbank.ru |
| TXT | 70WnQoZ/wCrnNB7duUtSO9waNMqvkcXk8HPtozezrsU= HARICA-GsxY3rMRf7jrnqvJqDl HARICA-qR3iQo6sn8BjtccPQbI MS=4D591CBAC7936116641E040C06C0004DCC3230BB MS=ms16274476 MS=ms62570499 MS=ms79102397 WumI3L9XqT0dIBdS08kG7igazLCU3hl3N32TScLEQH0= ZOOM_verify_aAYc5PKFS4K2edZoCEusFQ b0nbpfkr8fv6qrfjwzn1wpqnp42qfbg0 google-site-verification=1kkE-M1yXCbUhz-SAJl7-32uQlqDCy9FAhNo5XaYUTA google-site-verification=7LzD4FFH7jZt7pf0vQWcIztsre7htQonCP6HBk07eX4 google-site-verification=TwX2acHCKoj9mcWnef0kYUy70n237g8DKirwgR2zLPI google-site-verification=j-1-lVZQAsGA8AEZONwDTH60jaT4UWt4GfWpeGgZoL0 google-site-verification=u7SE9N6WWclPXKZUliCoX-NEibfD0Pvo04wtj5pf1o0 h3b9pjktksby6pnhbpwyffcggv99wwpb mailru-verification: 164c75b5422b21d6 mailru-verification: b1bb63ab33b1e83e miro-verification=ea103cc94da6554094da056ab5f85094e457d6c7 v=BIMI1; l=https://www.sberbank.ru/common/img/sber_icon.svg SPF v=spf1 ip4:84.252.146.118 ip4:194.54.15.231 ip4:182.66.115.64 -all |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
A+Redirect ChainNo redirects — direct accessPASS
https://sberbank.ru
526 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://sberbank.ru | 200 | 526 ms | HTTP/1.1 |
A+Domain Intelligencesberbank.ru — via RU-CENTER-RU, 17 years, 11 months old, hosted on SBERBANK, RUPASS
11 days
July 24, 2026
184 days
Issued by Hellenic Academic and Research Institutions CA
17 years, 11 months
Registered July 24, 2008
Status unknown
Protects against DNS spoofing
SBERBANK, RU
ASN AS35237
84.252.149.206
RU-CENTER-RU
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.
Learn more ▾ ▴
Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.
Source: ICANN / domain-security best practice