sberbank.com

Checked 22 October 2026, 10:34 UTC · via 8.8.8.8
✗Problems found
15 passed 4 warnings 1 failed 3 info

Registration

info

.com generic · Regional Network Information Center, JSC dba RU-CENTER · expires 2026-12-01

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Regional Network Information Center, JSC dba RU-CENTER
Registered
2 December 1998
Last changed
30 November 2025
Expires
1 December 2026
Status
client transfer prohibited
Registry nameservers
ns1.sberbank.ru, ns4.sberbank.ru, tmp1.sberbank.ru, tmp2.sberbank.ru
RDAP server
https://rdap.verisign.com/com/v1/

Checks

  • i
    .com is a generic TLD (gTLD)
    Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2026-12-01 #3
    The registration is valid until 2026-12-01 (39 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns1.sberbank.ru, ns4.sberbank.ru, tmp1.sberbank.ru, tmp2.sberbank.ru

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.sberbank.ru, ns4.sberbank.ru, tmp1.sberbank.ru, tmp2.sberbank.ru
NS in the zone
ns1.sberbank.ru, ns4.sberbank.ru, tmp1.sberbank.ru, tmp2.sberbank.ru
NameserverAddressesNetwork (AS)Glue
ns1.sberbank.ru84.252.149.157AS35237 Sberbank - Sberbank of Russia PJSC, RU-
ns4.sberbank.ru84.252.149.158AS35237 Sberbank - Sberbank of Russia PJSC, RU-
tmp1.sberbank.ru84.252.149.157AS35237 Sberbank - Sberbank of Russia PJSC, RU-
tmp2.sberbank.ru84.252.149.158AS35237 Sberbank - Sberbank of Russia PJSC, RU-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1.sberbank.ru, ns4.sberbank.ru, tmp1.sberbank.ru, tmp2.sberbank.ru.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • !
    Nameservers in one network
    all IPv4 addresses are in 84.252.149.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS35237 (Sberbank - Sberbank of Russia PJSC, RU): 4 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • i
    All nameserver names under .ru
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

fail

0 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.sberbank.ru 84.252.149.157NOERROR, 51 ms, NOT authoritativenoyes / yesrefusedPowerDNS Recursor 4.8.9
ns4.sberbank.ru 84.252.149.158NOERROR, 50 ms, NOT authoritativenoyes / yesrefusedPowerDNS Recursor 4.8.9
tmp1.sberbank.ru 84.252.149.157NOERROR, 50 ms, NOT authoritativenoyes / yesrefusedPowerDNS Recursor 4.8.9
tmp2.sberbank.ru 84.252.149.158NOERROR, 51 ms, NOT authoritativenoyes / yesrefusedPowerDNS Recursor 4.8.9

Checks

  • ✓ All respond #14
    All 4 nameserver addresses answered.
  • ✗
    Lame delegation
    These nameservers don't answer authoritatively for the zone, so resolvers ignore them: ns1.sberbank.ru (84.252.149.157): NOERROR, authoritative=false; ns4.sberbank.ru (84.252.149.158): NOERROR, authoritative=false; tmp1.sberbank.ru (84.252.149.157): NOERROR, authoritative=false; tmp2.sberbank.ru (84.252.149.158): NOERROR, authoritative=false.
    #15
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.sberbank.ru: "PowerDNS Recursor 4.8.9"; ns4.sberbank.ru: "PowerDNS Recursor 4.8.9"; tmp1.sberbank.ru: "PowerDNS Recursor 4.8.9"; tmp2.sberbank.ru: "PowerDNS Recursor 4.8.9". Hide or replace the version string.
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

No SOA record

Found

Serial per nameserver

NameserverSerial
ns1.sberbank.ru (84.252.149.157)2025101021
ns4.sberbank.ru (84.252.149.158)2025101021
tmp1.sberbank.ru (84.252.149.157)2025101021
tmp2.sberbank.ru (84.252.149.158)2025101021

Checks

  • ✓ Serial 2025101021 everywhere #22
    All nameservers serve the same version of the zone.

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27