Is russianfood.com down or not working?

What happened to russianfood.com, why did the website go down and not work? Here you can see who else is having the same problem with russianfood.com, as well as possible solutions. According to our statistics, the following most often do not work: Website, Login, Account, Mobile App.

Current status: No failures

At the moment, according to our data, russianfood.com is working fine, but single failures are possible. If russianfood.com does not work for you, then report your problem and write a comment.
Add comment

What to do if the site russianfood.com is not available? Try our guide.

russianfood.com outage reports in the last 24 hours

russianfood.com - error and failure reports, troubleshooting methods

Leave your comment describing the failure and share with other users how to solve the problem.
  • No registration required.
  • Messages with obscene language and insults, as well as breaking the law, are not allowed to be published.
  • Active links in the text of the message are not published, but displayed in plain text.
  • It is forbidden to post your own and other people's personal data: addresses, phone numbers, emails, accounts in instant messengers, etc.

Technical information

Main page title:
�������: ������ � RussianFood.com! ���������� ������� � ����, ����� ������� ����
Main page description:
���������� ���� �� ����� 114 ����� ���������� �������� � ������� �������� ������, ������� ����� 100 ������ ������� ����, ����� �������� � ����, �����, ��������� ��������� �������������.
Main page keywords:
�������, ���������� �������, ������� � ����, ������� ����, ������� �������������, ��� �����������, ��� �����������, ������� �������, ������� ����, ������� �������, �������� �������, ������� �����, ���������
Protocol:
https
Status code:
200
Page size:
279.6 KB
Response time:
0.473sec.
IP:
139.162.182.69
Response headers:
server: nginx/1.16.1
date: Tue, 01 Oct 2024 13:58:21 GMT
content-type: text/html; charset=windows-1251
transfer-encoding: chunked
connection: close
set-cookie: PHPSESSID=haeedhuvgct3ughii1uaipnjqm; path=/,geo_ip_set=1727791101; expires=Tue, 19-Jan-2038 03:14:07 GMT; Max-Age=419692546; path=/,geo_last_ip=86853430; expires=Tue, 19-Jan-2038 03:14:07 GMT; Max-Age=419692546; path=/,geo_ip_country=NL; expires=Tue, 19-Jan-2038 03:14:07 GMT; Max-Age=419692546; path=/,geo_ip_city_id=0; expires=Tue, 19-Jan-2038 03:14:07 GMT; Max-Age=419692546; path=/,geo_ip_oblast_id=0; expires=Tue, 19-Jan-2038 03:14:07 GMT; Max-Age=419692546; path=/,geo_ip_okrug_id=0; expires=Tue, 19-Jan-2038 03:14:07 GMT; Max-Age=419692546; path=/,geo_ip_set=1727791101; expires=Tue, 19-Jan-2038 03:14:07 GMT; Max-Age=419692546; path=/; domain=russianfood.com,geo_last_ip=86853430; expires=Tue, 19-Jan-2038 03:14:07 GMT; Max-Age=419692546; path=/; domain=russianfood.com,geo_ip_country=NL; expires=Tue, 19-Jan-2038 03:14:07 GMT; Max-Age=419692546; path=/; domain=russianfood.com,geo_ip_city_id=0; expires=Tue, 19-Jan-2038 03:14:07 GMT; Max-Age=419692546; path=/; domain=russianfood.com,geo_ip_oblast_id=0; expires=Tue, 19-Jan-2038 03:14:07 GMT; Max-Age=419692546; path=/; domain=russianfood.com,geo_ip_okrug_id=0; expires=Tue, 19-Jan-2038 03:14:07 GMT; Max-Age=419692546; path=/; domain=russianfood.com,geo_ip_set=1727791101; expires=Tue, 19-Jan-2038 03:14:07 GMT; Max-Age=419692546; path=/; domain=.russianfood.com,geo_last_ip=86853430; expires=Tue, 19-Jan-2038 03:14:07 GMT; Max-Age=419692546; path=/; domain=.russianfood.com,geo_ip_country=NL; expires=Tue, 19-Jan-2038 03:14:07 GMT; Max-Age=419692546; path=/; domain=.russianfood.com,geo_ip_city_id=0; expires=Tue, 19-Jan-2038 03:14:07 GMT; Max-Age=419692546; path=/; domain=.russianfood.com,geo_ip_oblast_id=0; expires=Tue, 19-Jan-2038 03:14:07 GMT; Max-Age=419692546; path=/; domain=.russianfood.com,geo_ip_okrug_id=0; expires=Tue, 19-Jan-2038 03:14:07 GMT; Max-Age=419692546; path=/; domain=.russianfood.com
expires: Tue, 01 Oct 2024 00:00:00 GMT
last-modified: Tue, 01 Oct 2024 16:58:21 GMT
cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
pragma: no-cache
DNS records:
A address139.162.182.69
ttl300
MX exchangeASPMX2.GOOGLEMAIL.com
priority30
MX exchangeALT2.ASPMX.L.GOOGLE.com
priority20
MX exchangeALT1.ASPMX.L.GOOGLE.com
priority20
MX exchangeASPMX.L.GOOGLE.com
priority10
MX exchangeASPMX5.GOOGLEMAIL.com
priority30
MX exchangeASPMX4.GOOGLEMAIL.com
priority30
MX exchangeASPMX3.GOOGLEMAIL.com
priority30
NS valuens3.linode.com
NS valuens1.linode.com
NS valuens4.linode.com
NS valuens5.linode.com
NS valuens2.linode.com
TXT entriesahrefs-site-verification_69db4d9771001a64b5cfb06e1be73ca0462f4b6ab5fd328dcb4a2a9b7d96fdff
TXT entriesgoogle-site-verification=buNeBFauCD57gWA-JVi9pgYPh-dLUWN0LQPhSGfQVAg
TXT entriesv=spf1 include:_spf.google.com ~all
SOA nsnamens1.linode.com
hostmasterinformburo\.od.gmail.com
serial2021000030
refresh14400
retry14400
expire1209600
minttl86400

SEO headers

h1 ���������� ������� ������� �����. ������� � ���� � �����
h2 ����� ��������
h2 ����� ������� ����

How to solve problems with russianfood.com

Errors on the russianfood.com website can be either on the server side or on your side (client side). If there is practically nothing to be done about errors on the server side (it remains only to wait for the site to work again), then with errors on the client side it is possible to solve the problem with the availability of russianfood.com on your own.