213.59.253.7 - IPInfo

Basic Info

City: unknown

Region: unknown

Country: Russia

Internet Service Provider: +7Telecom

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:

Make a comment on this IP

No discussion about this IP yet. Click above link to make one.

Comments on same subnet:

No discussion about this subnet yet..

Whois info:

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

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

% Information related to '213.59.192.0 - 213.59.255.255'

% Abuse contact for '213.59.192.0 - 213.59.255.255' is 'abuse@rt.ru'

inetnum:        213.59.192.0 - 213.59.255.255
netname:        RU-RTK-20000224
country:        RU
org:            ORG-JR8-RIPE
admin-c:        PRTT1-RIPE
tech-c:         RTNC-RIPE
status:         ALLOCATED PA
mnt-by:         RIPE-NCC-HM-MNT
mnt-by:         ROSTELECOM-MNT
mnt-lower:      ROSTELECOM-MNT
mnt-routes:     ROSTELECOM-MNT
created:        2014-10-10T12:32:29Z
last-modified:  2024-06-05T06:43:39Z
source:         RIPE

organisation:   ORG-JR8-RIPE
org-name:       PJSC Rostelecom
country:        RU
org-type:       LIR
address:        14 A, Sinopskaya nabereznaya
address:        191167
address:        S.Peterburg
address:        RUSSIAN FEDERATION
phone:          +7 499 999-82-83
fax-no:         +74999953619
admin-c:        PRTT1-RIPE
admin-c:        IE1277-RIPE
admin-c:        NM7547-RIPE
admin-c:        AA728-RIPE
abuse-c:        RTNC-RIPE
mnt-ref:        RIPE-NCC-HM-MNT
mnt-ref:        ROSTELECOM-MNT
mnt-ref:        ROSNIIROS-MNT
mnt-by:         RIPE-NCC-HM-MNT
mnt-by:         ROSTELECOM-MNT
created:        2005-03-22T11:11:20Z
last-modified:  2025-08-12T04:03:18Z
source:         RIPE # Filtered

role:           PJSC Rostelecom Technical Team
address:        PJSC Rostelecom Russian Federation
nic-hdl:        PRTT1-RIPE
mnt-by:         ROSTELECOM-MNT
created:        2024-05-20T01:54:00Z
last-modified:  2024-05-20T01:54:00Z
source:         RIPE # Filtered

role:           PJSC Rostelecom Technical Team
address:        PJSC Rostelecom
address:        Russian Federation
abuse-mailbox:  abuse@rt.ru
admin-c:        IE1277-RIPE
tech-c:         IE1277-RIPE
remarks:        trouble: ---------------------------------------------------------------
remarks:        trouble: Rostelecom NOC is available 24 x 7
remarks:        trouble: e-mail cuss-ip@rt.ru
remarks:        trouble: ---------------------------------------------------------------
remarks:        ------------------------------------------------------------------------
remarks:        peering requests: peering@rt.ru
remarks:        ------------------------------------------------------------------------
remarks:        http://www.rostelecom.ru/, looking-glass http://lg.ip.rt.ru/
remarks:        ------------------------------------------------------------------------
nic-hdl:        RTNC-RIPE
mnt-by:         ROSTELECOM-MNT
created:        2007-11-27T13:28:11Z
last-modified:  2022-12-12T07:46:18Z
source:         RIPE # Filtered

% Information related to '213.59.252.0/22AS12389'

route:          213.59.252.0/22
descr:          ROSTELECOM NETS
origin:         AS12389
mnt-by:         ROSTELECOM-MNT
created:        2017-04-18T07:39:06Z
last-modified:  2017-04-18T07:39:06Z
source:         RIPE

% This query was served by the RIPE Database Query Service version 1.121.2 (SHETLAND)

Dig info:

; <<>> DiG 9.10.3-P4-Ubuntu <<>> 213.59.253.7
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 63953
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;213.59.253.7.			IN	A

;; AUTHORITY SECTION:
.			30	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2026041100 1800 900 604800 86400

;; Query time: 6 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Apr 11 23:51:03 CST 2026
;; MSG SIZE  rcvd: 105

Host info

Host 7.253.59.213.in-addr.arpa. not found: 3(NXDOMAIN)

Nslookup info:

Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 7.253.59.213.in-addr.arpa: NXDOMAIN

Related IP info:

Related comments:

IP	Type	Details	Datetime
189.241.100.160	attackbots	Jul 23 20:28:10 vtv3 sshd\[22350\]: Invalid user otrs from 189.241.100.160 port 43958 Jul 23 20:28:10 vtv3 sshd\[22350\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.241.100.160 Jul 23 20:28:12 vtv3 sshd\[22350\]: Failed password for invalid user otrs from 189.241.100.160 port 43958 ssh2 Jul 23 20:34:38 vtv3 sshd\[25747\]: Invalid user rohit from 189.241.100.160 port 55134 Jul 23 20:34:38 vtv3 sshd\[25747\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.241.100.160 Jul 23 20:49:10 vtv3 sshd\[347\]: Invalid user sale from 189.241.100.160 port 41802 Jul 23 20:49:10 vtv3 sshd\[347\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.241.100.160 Jul 23 20:49:12 vtv3 sshd\[347\]: Failed password for invalid user sale from 189.241.100.160 port 41802 ssh2 Jul 23 20:54:02 vtv3 sshd\[2803\]: Invalid user oleg from 189.241.100.160 port 37370 Jul 23 20:54:02 vtv3 sshd\[2803\]:	2019-07-24 06:51:04
158.69.212.227	attackbots	Jul 24 01:35:02 server sshd\[2330\]: Invalid user eddie from 158.69.212.227 port 38762 Jul 24 01:35:02 server sshd\[2330\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=158.69.212.227 Jul 24 01:35:04 server sshd\[2330\]: Failed password for invalid user eddie from 158.69.212.227 port 38762 ssh2 Jul 24 01:40:38 server sshd\[16120\]: Invalid user osmc from 158.69.212.227 port 53950 Jul 24 01:40:38 server sshd\[16120\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=158.69.212.227	2019-07-24 06:56:10
77.195.187.117	attack	Jul 23 16:19:30 localhost kernel: [15157364.004631] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:a8:41:08:00 SRC=77.195.187.117 DST=[mungedIP2] LEN=40 TOS=0x08 PREC=0x20 TTL=54 ID=33859 PROTO=TCP SPT=35149 DPT=23 WINDOW=32837 RES=0x00 SYN URGP=0 Jul 23 16:19:30 localhost kernel: [15157364.004659] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:a8:41:08:00 SRC=77.195.187.117 DST=[mungedIP2] LEN=40 TOS=0x08 PREC=0x20 TTL=54 ID=33859 PROTO=TCP SPT=35149 DPT=23 SEQ=758669438 ACK=0 WINDOW=32837 RES=0x00 SYN URGP=0 Jul 23 16:19:30 localhost kernel: [15157364.023515] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:a8:41:08:00 SRC=77.195.187.117 DST=[mungedIP2] LEN=40 TOS=0x08 PREC=0x20 TTL=54 ID=33859 PROTO=TCP SPT=35149 DPT=23 WINDOW=32837 RES=0x00 SYN URGP=0 Jul 23 16:19:30 localhost kernel: [15157364.023533] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:a8:41:08:00 SRC=77.195.187.117 DST=[mungedIP2] LEN=40 TOS=0x08 PRE	2019-07-24 06:39:19
78.44.243.210	attackspambots	Honeypot attack, port: 23, PTR: static-78-44-243-210.net.upcbroadband.cz.	2019-07-24 07:11:50
88.148.21.129	attackspam	Automatic report - Port Scan Attack	2019-07-24 06:48:05
141.98.80.61	attackspam	Jul 23 23:35:03 mail postfix/smtpd\[28873\]: warning: unknown\[141.98.80.61\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\ Jul 23 23:35:17 mail postfix/smtpd\[1290\]: warning: unknown\[141.98.80.61\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\ Jul 24 00:21:50 mail postfix/smtpd\[4183\]: warning: unknown\[141.98.80.61\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\ Jul 24 00:22:05 mail postfix/smtpd\[31692\]: warning: unknown\[141.98.80.61\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\	2019-07-24 06:50:40
202.53.165.218	attackbots	2019-07-23 15:19:46 H=(liveus.it) [202.53.165.218]:46016 I=[192.147.25.65]:25 F= rejected RCPT : RBL: found in thrukfz5b56tq6xao6odgdyjrq.zen.dq.spamhaus.net (127.0.0.4, 127.0.0.3) (https://www.spamhaus.org/query/ip/202.53.165.218) 2019-07-23 15:19:46 H=(liveus.it) [202.53.165.218]:46016 I=[192.147.25.65]:25 F= rejected RCPT : RBL: found in thrukfz5b56tq6xao6odgdyjrq.zen.dq.spamhaus.net (127.0.0.4, 127.0.0.3) (https://www.spamhaus.org/query/ip/202.53.165.218) 2019-07-23 15:19:47 H=(liveus.it) [202.53.165.218]:46016 I=[192.147.25.65]:25 F= rejected RCPT : RBL: found in thrukfz5b56tq6xao6odgdyjrq.zen.dq.spamhaus.net (127.0.0.4, 127.0.0.3) (https://www.spamhaus.org/sbl/query/SBLCSS) ...	2019-07-24 06:32:00
94.39.248.202	attackspambots	Jul 23 23:43:22 * sshd[8730]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.39.248.202 Jul 23 23:43:25 * sshd[8730]: Failed password for invalid user test1 from 94.39.248.202 port 63566 ssh2	2019-07-24 06:48:31
41.41.77.154	attackbots	Automatic report - Port Scan Attack	2019-07-24 06:50:25
94.242.57.136	attackspambots	WordPress XMLRPC scan :: 94.242.57.136 0.180 BYPASS [24/Jul/2019:06:19:16 1000] www.[censored_1] "POST /xmlrpc.php HTTP/1.1" 200 382 "https://www.[censored_1]/" "PHP/5.2.06"	2019-07-24 06:44:59
89.217.42.114	attackspambots	Jul 24 00:26:53 * sshd[16574]: Failed password for git from 89.217.42.114 port 48826 ssh2 Jul 24 00:31:12 * sshd[17385]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.217.42.114	2019-07-24 06:45:33
103.101.18.43	attackspambots	2019-07-23T20:18:36.327121abusebot.cloudsearch.cf sshd\[1071\]: Invalid user user1 from 103.101.18.43 port 63153	2019-07-24 06:59:39
106.12.125.139	attackspam	Jul 23 18:23:28 vps200512 sshd\[10634\]: Invalid user yp from 106.12.125.139 Jul 23 18:23:28 vps200512 sshd\[10634\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.125.139 Jul 23 18:23:30 vps200512 sshd\[10634\]: Failed password for invalid user yp from 106.12.125.139 port 60538 ssh2 Jul 23 18:25:30 vps200512 sshd\[10680\]: Invalid user dev from 106.12.125.139 Jul 23 18:25:30 vps200512 sshd\[10680\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.125.139	2019-07-24 06:33:45
62.210.151.21	attackbots	\[2019-07-23 18:59:58\] SECURITY\[20812\] res_security_log.c: SecurityEvent="FailedACL",EventTV="2019-07-23T18:59:58.939-0400",Severity="Error",Service="SIP",EventVersion="1",AccountID="00441204918031",SessionID="0x7f06f88cc728",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/62.210.151.21/54618",ACLName="no_extension_match" \[2019-07-23 19:00:06\] SECURITY\[20812\] res_security_log.c: SecurityEvent="FailedACL",EventTV="2019-07-23T19:00:06.536-0400",Severity="Error",Service="SIP",EventVersion="1",AccountID="900441204918031",SessionID="0x7f06f823f758",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/62.210.151.21/61401",ACLName="no_extension_match" \[2019-07-23 19:00:22\] SECURITY\[20812\] res_security_log.c: SecurityEvent="FailedACL",EventTV="2019-07-23T19:00:22.360-0400",Severity="Error",Service="SIP",EventVersion="1",AccountID="9441204918031",SessionID="0x7f06f804c2c8",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/62.210.151.21/58342",ACLName="no_ext	2019-07-24 07:01:20
92.118.160.1	attack	Honeypot attack, port: 139, PTR: 92.118.160.1.netsystemsresearch.com.	2019-07-24 07:08:37

Recently Reported IPs

20.220.11.224	161.115.235.204	121.230.89.213	2606:4700:10::6816:1031
2606:4700:10::ac43:1807	2606:4700:10::ac43:1436	231.67.84.99	54.226.22.115
109.106.255.79	102.229.43.141	23.27.116.214	87.240.137.164
180.98.38.7	177.112.194.114	2606:4700:10::6814:4516	2606:4700:10::6816:2735
2606:4700:10::6814:9080	2606:4700:10::6814:4426	2606:4700:10::6814:6196	2606:4700:10::6816:2597