Kit-34.ru Интернет-магазин «КИТ-Сервис»

Kit-34.ru Overview

Kit-34.ru belongs to JSC RTComm.RU. Check the list of other websites hosted by JSC RTComm.RU.

In terms of rank-to-traffic ratio, kit-34.ru has 2,409 unique users per day, viewing 4,865 pages. The rank based value of kit-34.ru is 3,629 USD. Every user makes 2.14 pageviews on average.

Kit-34.ru boasts a link base consisting of 306 referring domains and 330 external backlinks, as revealed by the data obtained from web network scanning.

Kit-34.ru top-level domain belongs to .RU domain zone. Check other webpages in .RU zone.

According the last verification test in March 13, 2023, kit-34.ru has an expired SSL certificate issued by GlobalSign nv-sa (expired on April 08, 2023). Click button “Update” SSL Information at the Safety Information section. Check the list of websites using SSL by GlobalSign nv-sa.

Based on data from Google Safe Browsing and Symantec kit-34.ru is a fairly safe domain.

According the Mobile-Friendly test by Google kit-34.ru is nice optimized for mobile devices and tablets, however the webpage speed could be improved.

Kit-34.ru Website Safety

logo
Overview
Last Updated: 12/27/2024
Unknown status.
We gather website safety and reputation data and compare it with available third-party sources so we calculate own safety and trustworthiness rate based on information that we get.
Norton connect safe logo
Norton Connect Safe
Last Updated: 05/08/2024
kit-34.ru is safe.
Norton ConnectSafe evaluates kit-34.ru for any unsafe and insecure content. The results are critical for families with young children.
Google logo
Google Safe Search
Last Updated: 12/27/2024
Not yet checked.
SafeSearch is used as a parental control tool to filter out any inappropriate for your children search results on your devices: phones, tablets or personal computers.
Google safe brwosing logo
Google Safe Browsing
Last Updated: 01/12/2019
kit-34.ru is safe.
Malware: not found.
Phishing: not detected.
Unwanted software: not found.
Harmfull applications: not found.
Google Safe Browsing notifies when websites are compromised by malicious actors. These protections work across Google products and provide a safer online experience.
McAfee logo
Site Advisor
Last Updated: 06/15/2020
kit-34.ru is safe.
McAfee assesses kit-34.ru for a meaningful set of security threats. Featured dangers from annoying pop-ups to hidden Trojans, that can steal your identity, will be revealed. McAfee does not analyze kit-34.ru for mature or inappropriate content, only security checks are evaluated.
Web of trust logo
Web of Trust
Last Updated: 12/27/2024
kit-34.ru child safety is unknown.
The WOT calculates reputation of the kit-34.ru. This reputation system receives ratings from users and information from third-party sources, assesses the kit-34.ru for safety features and confirms, whether kit-34.ru is suitable for children.

SSL Information
Domainwww.kit-34.ru
Issuer OrganizationGlobalSign nv-sa
IssuerAlphaSSL CA - SHA256 - G2
AlgorithmRSA-SHA256
Valid form03/07/2022
Expiration04/08/2023
SignedCertificate is not self signed
Additional Domains www.kit-34.ru
kit-34.ru

Kit-34.ru Rank History

Kit-34.ru Hosting Information

Server Location

ASN Information

ASN ID: 8342

ASN Title: JSC RTComm.RU

Last Update: 08/30/2024

% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf

% Note: this output has been filtered.
% To receive output for a database update, use the "-B" flag.

% Information related to 'AS8192 - AS8523'

as-block: AS8192 - AS8523
descr: RIPE NCC ASN block
remarks: These AS Numbers are assigned to network operators in the RIPE NCC service region.
mnt-by: RIPE-NCC-HM-MNT
created: 2010-05-11T11:44:46Z
last-modified: 2014-02-24T13:15:16Z
source: RIPE

% Information related to 'AS8342'

% Abuse contact for 'AS8342' is 'abuse@rtcomm.ru'

aut-num: AS8342
as-name: RTCOMM-AS
remarks: Moscow, Russia
remarks:
remarks: ----------------------------------------------------------------
remarks: IPv4 Routing Policy
remarks: ----------------------------------------------------------------
remarks:
remarks: ----------------------------------------------------------------
remarks: UPSTREAMS:
remarks: ----------------------------------------------------------------
remarks:
import: from AS8359 212.188.11.53 at 195.161.1.141 action pref=200; accept ANY
export: to AS8359 announce AS-RT
import: from AS8359 212.188.31.60 at 195.161.1.70 action pref=100; accept ANY
export: to AS8359 212.188.31.60 at 195.161.1.70 announce {195.161.120.0/22, 95.172.157.0/24}
import: from AS8920 212.16.222.225 at 195.161.1.41 action pref=100; accept ANY
export: to AS8920 announce {195.161.56.0/22}
import: from AS12389 188.254.22.221 at 195.161.1.30 action pref=200; accept ANY
import: from AS12389 188.254.22.225 at 195.161.1.30 action pref=200; accept ANY
import: from AS12389 213.24.114.169 at 195.161.1.45 action pref=200; accept ANY
export: to AS12389 announce AS-RT
import: from AS12389 188.128.97.233 at 195.161.1.14 action pref=200; accept ANY
export: to AS12389 188.128.97.233 at 195.161.1.14 announce AS-RT and {195.161.88.0/22}
import: from AS12389 188.128.97.165 at 195.161.1.15 action pref=200; accept ANY
export: to AS12389 188.128.97.165 at 195.161.1.15 announce AS-RT and {195.161.140.0/22}
import: from AS199728 185.48.113.21 at 195.161.1.13 accept ANY
export: to AS199728 announce AS-RT and {195.161.88.0/22}
remarks:
remarks: ----------------------------------------------------------------
remarks: RUSSIAN PEERING PARTNERS (MSK M9 & MSK-IX):
remarks: ----------------------------------------------------------------
remarks:
import: from AS3267 195.161.157.198 at 195.161.1.30 action pref=500; accept AS-RUNNET
export: to AS3267 announce AS-RT
import: from AS12389 195.161.4.138 at 195.161.1.30 action pref=500; accept AS-ROSTELECOM
import: from AS12389 213.59.5.110 at 195.161.1.30 action pref=500; accept AS-ROSTELECOM
import: from AS12389 188.254.8.153 at 195.161.1.27 action pref=500; accept AS-ROSTELECOM
export: to AS12389 announce AS-RT
import: from AS15169 193.232.244.232 at 195.161.1.30 action pref=500; accept AS-GOOGLE
export: to AS15169 announce AS-RT
import: from AS50952 178.18.224.100 at 195.161.1.141 action pref=500; accept AS-DATAIX
import: from AS50952 178.18.227.100 at 195.161.1.141 action pref=500; accept AS-DATAIX
export: to AS50952 announce AS-RT
remarks:
remarks: ----------------------------------------------------------------
remarks: CUSTOMERS:
remarks: ----------------------------------------------------------------
remarks:
import: from AS5473 195.161.157.230 at 195.161.1.3 action pref=1000; accept AS5473
export: to AS5473 announce {0.0.0.0/0}
import: from AS16083 217.106.31.130 at 195.161.1.19 action pref=1000; accept AS-STACK
export: to AS16083 announce ANY
import: from AS16176 195.161.157.6 at 195.161.1.193 action pref=1000; accept AS16176
export: to AS16176 announce ANY
import: from AS39182 81.177.26.105 at 195.161.1.140 action pref=1000; accept AS-I7
export: to AS39182 announce ANY
import: from AS44532 195.161.4.46 at 195.161.1.251 action pref=1000; from AS44532 195.161.4.146 at 195.161.1.251 action pref=1000; accept AS44532
export: to AS44532 announce ANY
import: from AS44913 195.161.4.102 at 195.161.1.14 action pref=1000; accept AS44913
export: to AS44913 announce ANY
import: from AS45027 81.177.22.106 at 195.161.1.140 action pref=1000; accept AS45027
export: to AS45027 announce ANY
import: from AS47761 195.161.4.98 at 195.161.1.140 action pref=1000; from AS47761 195.161.4.22 at 195.161.1.141 action pref=1000; accept AS47761
export: to AS47761 announce ANY
import: from AS48349 81.176.69.42 at 195.161.1.45 action pref=1000; from AS48349 81.176.69.43 at 195.161.1.45 action pref=1000; accept AS48349
export: to AS48349 announce ANY
import: from AS48488 195.161.2.174 at 195.161.1.45 action pref=1000; accept AS48488
export: to AS48488 announce ANY
import: from AS49002 195.161.40.12 at 195.161.1.27 action pref=1000; from AS49002 213.59.3.190 at 195.161.1.27 action pref=1000; accept AS49002
export: to AS49002 announce ANY
import: from AS49136 217.106.30.78 at 195.161.1.141 action pref=1000; accept AS-TELENET-NET
export: to AS49136 announce ANY
import: from AS49347 195.161.161.234 at 195.161.1.142 action pref=1000; accept AS49347
export: to AS49347 announce ANY
import: from AS52062 217.106.31.6 at 195.161.1.45 action pref=1000; accept AS52062
export: to AS52062 announce ANY
import: from AS56528 81.177.178.194 at 195.161.1.140 action pref=1000; accept AS56528
export: to AS56528 announce ANY
import: from AS56601 81.177.26.101 at 195.161.1.140 action pref=1000; accept AS-I7
export: to AS56601 announce ANY
import: from AS57494 81.176.239.132 at 195.161.1.140 action pref=1000; accept AS57494
export: to AS57494 announce ANY
import: from AS58097 195.161.2.102 at 195.161.1.28 action pref=1000; from AS58097 217.107.216.194 at 195.161.1.140 action pref=1000; accept AS58097
export: to AS58097 announce ANY
import: from AS58084 217.106.30.82 at 195.161.1.45 action pref=1000; accept AS58084
export: to AS58084 announce {0.0.0.0/0}
import: from AS60544 195.161.40.99 at 195.161.1.28 action pref=1000; accept AS60544
export: to AS60544 announce {0.0.0.0/0}
import: from AS201052 195.161.2.226 at 195.161.1.27 action pref=1000; accept AS201052
export: to AS201052 announce ANY
import: from AS206668 195.161.42.2 at 195.161.1.251 action pref=1000; accept AS206668
export: to AS206668 announce ANY
remarks:
remarks: ----------------------------------------------------------------
remarks: IPv6 Routing Policy
remarks: ----------------------------------------------------------------
remarks:
remarks: ----------------------------------------------------------------
remarks: UPSTREAMS:
remarks: ----------------------------------------------------------------
remarks:
mp-import: afi ipv6.unicast from AS8359 2A02:28:1:2::5F:15 at 195.161.1.141 accept ANY
mp-export: afi ipv6.unicast to AS8359 announce AS-RT-IPV6
mp-import: afi ipv6.unicast from AS12389 2a01:620:1:200f::1 at 195.161.1.30 action pref=200; accept ANY
mp-import: afi ipv6.unicast from AS12389 2a01:620:1:2019::1 at 195.161.1.30 action pref=200; accept ANY
mp-import: afi ipv6.unicast from AS12389 2a01:620:1:2031::1 at 195.161.1.45 action pref=200; accept ANY
mp-export: afi ipv6.unicast to AS12389 announce AS-RT-IPV6
remarks:
remarks: ----------------------------------------------------------------
remarks: RUSSIAN PEERING PARTNERS (MSK M9 & MSK-IX):
remarks: ----------------------------------------------------------------
remarks:
mp-import: afi ipv6.unicast from AS12389 2a01:620:1:200a::1 at 195.161.1.30 action pref=500; accept AS-ROSTELECOM
mp-import: afi ipv6.unicast from AS12389 2a01:620:1:200e::1 at 195.161.1.30 action pref=500; accept AS-ROSTELECOM
mp-import: afi ipv6.unicast from AS12389 2a01:620:1:201c::1 at 195.161.1.27 action pref=500; accept AS-ROSTELECOM
mp-export: afi ipv6.unicast to AS12389 announce AS-RT-IPV6
mp-import: afi ipv6.unicast from AS50952 2a03:5f80:4::224:100 at 195.161.1.141 action pref=500; accept AS-DATAIX6
mp-import: afi ipv6.unicast from AS50952 2a03:5f80:4::227:100 at 195.161.1.141 action pref=500; accept AS-DATAIX6
mp-export: afi ipv6.unicast to AS50952 announce AS-RT-IPV6
remarks:
remarks: ----------------------------------------------------------------
remarks: CUSTOMERS:
remarks: ----------------------------------------------------------------
remarks:
mp-import: afi ipv6.unicast from AS16083 2001:1bb0:e000:2::2 at 195.161.1.19 action pref=1000; accept AS-STACK6
mp-export: afi ipv6.unicast to AS16083 announce ANY
mp-import: afi ipv6.unicast from AS45027 2001:1bb0:e000:16::2 at 195.161.1.140 action pref=1000; accept AS45027
mp-export: afi ipv6.unicast to AS45027 announce {0::/0}
mp-import: afi ipv6.unicast from AS56601 2001:1bb0:e000:16::3 at 195.161.1.140 action pref=1000; accept AS56601
mp-export: afi ipv6.unicast to AS56601 announce {0::/0}
remarks:
remarks: +---------------------------------------------------------------
remarks: |
remarks: | External communities may be set by external peers when
remarks: | talking to AS8342.
remarks: |
remarks: | Community Meaning
remarks: |
remarks: | 8342:120x When advertising to any RUSSIAN peer...
remarks: | 8342:170x When advertising to any peer at Rostelecom...
remarks: | ...x=0 - do not advertise
remarks: | ...x=1,2,4 or 6 - prepend 8342 (1,2,4 or 6) times
remarks: | 8342:1900 BACKUP community. Local preference is set to 100,
remarks: | which is the lowest value used in the network.
remarks: | We DO NOT accept "no-export" community.
remarks: +---------------------------------------------------------------
remarks: | 8342:666 - blackhole (discard) traffic
remarks: +---------------------------------------------------------------
remarks: |
remarks: | All 12389:* communities are accept and pass out to Rostelecom
remarks: |
remarks: +---------------------------------------------------------------
remarks: | Any other communities are deleted.
remarks: |
remarks: | CUSTOMER - Peers routes are getting local preference of 1000.
remarks: | RUSSIAN - Peers routes are getting local preference of 500.
remarks: | INTERNATIONAL - Peers routes and UPLINKS
remarks: | are getting local preference in the range of 190-220
remarks: |
remarks: | We are using prefix-list filters that were built according
remarks: | to RIPE route-objects.
remarks: |
remarks: +---------------------------------------------------------------
remarks: | Routing policies are becoming so complex that a complete
remarks: | description is beyond the scope of this document.
remarks: +---------------------------------------------------------------
remarks: | NOTE - Filtering on /24 boundary is applied - we do not
remarks: | reannounce any route more specific than a /24.
remarks: +---------------------------------------------------------------
org: ORG-RA25-RIPE
admin-c: RT-RU
tech-c: RT-RU
status: ASSIGNED
mnt-by: RIPE-NCC-END-MNT
mnt-by: AS8342-MNT
created: 2002-09-10T13:35:14Z
last-modified: 2018-06-06T06:52:36Z
source: RIPE # Filtered

organisation: ORG-RA25-RIPE
org-name: JSC RTComm.RU
org-type: LIR
address: 22'km of Kiyevskoe sh., Moskovskiy pos. 6, building 1
address: 108811
address: Moscow
address: RUSSIAN FEDERATION
phone: +74959887778
fax-no: +74959887776
admin-c: AT9798-RIPE
admin-c: NR3542-RIPE
admin-c: NK2352-RIPE
abuse-c: RTC-RU
mnt-ref: RIPE-NCC-HM-MNT
mnt-ref: AS8342-MNT
mnt-by: RIPE-NCC-HM-MNT
mnt-by: AS8342-MNT
created: 2004-04-17T11:57:36Z
last-modified: 2017-10-30T14:41:29Z
source: RIPE # Filtered

role: RTComm.RU Internet Center
address: JSC RTComm.RU
address: 22'km of Kiyevskoe sh., Moskovskiy pos. 6, building 1
address: 108811, Moscow
address: Russia
phone: +7 495 988-77-78
fax-no: +7 495 988-77-76
remarks: trouble: ---------------------------------------------------------
remarks: trouble: RTComm.RU Internet Center is available 24 x 7
remarks: trouble: ---------------------------------------------------------
remarks: trouble: Points of contact for RTComm.RU Network Operations
remarks: trouble: ---------------------------------------------------------
remarks: trouble: Network Operations Center vsat-noc@rtcomm.ru
remarks: trouble: SPAM and Network security issues: abuse@rtcomm.ru
remarks: trouble: Routing policies: rtc-cs@rtcomm.ru
remarks: trouble: Peering requests: peering@rtcomm.ru
remarks: trouble: ---------------------------------------------------------
remarks: trouble:
remarks: trouble: ___________________A T T E N T I O N!____________________
remarks: trouble:
remarks: trouble: Please use abuse@rtcomm.ru e-mail address for complaints.
remarks: trouble: All messages to any other our address, relative to SPAM
remarks: trouble: or security issues, will not be concerned.
remarks: trouble:
remarks: trouble: ---------------------------------------------------------
admin-c: NK2352-RIPE
admin-c: AT9798-RIPE
admin-c: NR3542-RIPE
admin-c: AOR16-RIPE
tech-c: NK2352-RIPE
tech-c: AT9798-RIPE
tech-c: NR3542-RIPE
tech-c: AOR16-RIPE
nic-hdl: RT-RU
mnt-by: AS8342-MNT
abuse-mailbox: abuse@rtcomm.ru
created: 2002-12-25T12:11:11Z
last-modified: 2017-03-29T13:20:23Z
source: RIPE # Filtered

% This query was served by the RIPE Database Query Service version 1.91.2 (BLAARKOP)

Kit-34.ru Domain Registration and Settings

WHOIS

% By submitting a query to RIPN's Whois Service
% you agree to abide by the following terms of use:
% http://www.ripn.net/about/servpol.html#3.2 (in Russian)
% http://www.ripn.net/about/en/servpol.html#3.2 (in English).

domain: KIT-34.RU
nserver: ns1.jino.ru.
nserver: ns2.jino.ru.
nserver: ns3.jino.ru.
nserver: ns4.jino.ru.
state: REGISTERED, DELEGATED, VERIFIED
org: OOO "Orsinus"
registrar: R01-RU
admin-contact: https://partner.r01.ru/contact_admin.khtml
created: 2013-10-13T20:13:10Z
paid-till: 2022-10-13T21:13:10Z
free-date: 2022-11-14
source: TCI

Last updated on 2022-01-25T06:26:31Z


DNS Records
HostA RecordTTL
HostMX RecordPriorityTTL
HostNS RecordTTL
HostTXT RecordTTL

Kit-34.ru HTML Check

Kit-34.ru Desktop Performance

Last tested: 09/07/2018

Speedometer image
Desktop Speed
30%

Desktop Resource Breakdown
Total Resources59
Number of Hosts5
Static Resources49
JavaScript Resources15
CSS Resources7

Kit-34.ru Mobile Insights

Last tested: 09/07/2018

Speedometer image
Mobile Usability
71%
Speedometer image
Mobile Speed
28%

Mobile Resource Breakdown
Total Resources59
Number of Hosts5
Static Resources49
JavaScript Resources15
CSS Resources7

Kit-34.ru Common Typos

www.kit-34.com
www.kit-34.net
www.kit-34.org
www.kit-34.info
www.kit-34.biz
www.kit-34.us
www.kit-34.mobi
www.it-34.ru
www.kit-34.ru
www.jit-34.ru
www.kjit-34.ru
www.jkit-34.ru
www.iit-34.ru
www.kiit-34.ru
www.ikit-34.ru
www.mit-34.ru
www.kmit-34.ru
www.mkit-34.ru
www.lit-34.ru
www.klit-34.ru
www.lkit-34.ru
www.oit-34.ru
www.koit-34.ru
www.okit-34.ru
www.kt-34.ru
www.kut-34.ru
www.kiut-34.ru
www.kuit-34.ru
www.kjt-34.ru
www.kijt-34.ru
www.kkt-34.ru
www.kikt-34.ru
www.kkit-34.ru
www.kot-34.ru
www.kiot-34.ru
www.ki-34.ru
www.kir-34.ru
www.kitr-34.ru
www.kirt-34.ru
www.kif-34.ru
www.kitf-34.ru
www.kift-34.ru
www.kig-34.ru
www.kitg-34.ru
www.kigt-34.ru
www.kiy-34.ru
www.kity-34.ru
www.kiyt-34.ru
www.kit34.ru
www.kit-4.ru
www.kit-3.ru