TCP wrappers have been falling out of fashion. Webservers (Apache and others) might need to be compiled with support for TCP wrappers. Apache and Nginx have their own methods and modules which normally are used.
The Web server, Nginx, also does not support TCP wrappers, but there is a module to support them at this address: https://github.com/sjinks/ngx_tcpwrappers. This also requires compilation from source and has severe limitations.
It should be noted that TCP Wrappers have several peculiarities you
should know about:
the most disappointing thing is that libwrap (library implementing TCP
Wrappers functionality) is not a thread safe library. In other words,
if two threads try to simultaneously use libwrap, the results could be
weird. This is because libwrap uses non-reentrant functions like
strtok(), gethostbyname(), gethostbyaddr() etc. If nginx is built with
threading support (does it work yet?), use of libwrap can lead to
performance penalties (because access to libwrap functions will have
to be serialized). If nginx is configured without threading support
(this is the default for Linux), everything is OK.
configuration comes at a price: libwrap will read and parse
/etc/hosts.allow and /etc/hosts.deny on every request; this may be an
issue for high-loaded projects.
So in the end, using tcpwrappers is not feasible.