City: Nizhniy Novgorod
Region: Nizhny Novgorod
Country: Russia
Internet Service Provider: +7Telecom
Hostname: unknown
Organization: unknown
Usage Type: unknown
% 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 '82.208.64.0 - 82.208.127.255'
% Abuse contact for '82.208.64.0 - 82.208.127.255' is 'abuse@rt.ru'
inetnum: 82.208.64.0 - 82.208.127.255
netname: RU-RTK-20030918
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: 2003-09-18T11:59:29Z
last-modified: 2024-06-05T10:28:31Z
source: RIPE # Filtered
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 '82.208.64.0/18AS12389'
route: 82.208.64.0/18
descr: Rostelecom networks
origin: AS12389
mnt-by: ROSTELECOM-MNT
created: 2018-10-01T06:46:21Z
last-modified: 2018-10-01T06:46:21Z
source: RIPE # Filtered
% This query was served by the RIPE Database Query Service version 1.121.2 (BUSA); <<>> DiG 9.10.3-P4-Ubuntu <<>> 82.208.110.101
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 8558
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;82.208.110.101. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026042301 1800 900 604800 86400
;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Apr 24 10:30:26 CST 2026
;; MSG SIZE rcvd: 107Host 101.110.208.82.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 101.110.208.82.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 195.14.118.63 | attackspam | firewall-block, port(s): 5984/tcp |
2019-10-16 18:48:15 |
| 200.158.198.184 | attackspam | Oct 16 11:09:50 vmanager6029 sshd\[2405\]: Invalid user ftpadmin from 200.158.198.184 port 57165 Oct 16 11:09:50 vmanager6029 sshd\[2405\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.158.198.184 Oct 16 11:09:52 vmanager6029 sshd\[2405\]: Failed password for invalid user ftpadmin from 200.158.198.184 port 57165 ssh2 |
2019-10-16 18:12:44 |
| 146.115.75.225 | attack | SSH-bruteforce attempts |
2019-10-16 18:19:54 |
| 95.213.177.124 | attackbots | 3389BruteforceFW21 |
2019-10-16 18:47:33 |
| 103.41.66.20 | attack | Port 1433 Scan |
2019-10-16 18:29:41 |
| 77.37.240.23 | attackbotsspam | T: f2b postfix aggressive 3x |
2019-10-16 18:28:35 |
| 79.137.75.5 | attackspambots | Failed password for invalid user 1234 from 79.137.75.5 port 38012 ssh2 Invalid user 1 from 79.137.75.5 port 46152 pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.137.75.5 Failed password for invalid user 1 from 79.137.75.5 port 46152 ssh2 Invalid user enough from 79.137.75.5 port 54226 |
2019-10-16 18:31:08 |
| 104.131.178.223 | attackbots | Oct 16 07:18:18 meumeu sshd[655]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.131.178.223 Oct 16 07:18:20 meumeu sshd[655]: Failed password for invalid user admin from 104.131.178.223 port 35059 ssh2 Oct 16 07:22:28 meumeu sshd[1332]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.131.178.223 ... |
2019-10-16 18:11:40 |
| 46.105.227.206 | attackspambots | Oct 16 11:40:50 vpn01 sshd[3533]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.105.227.206 Oct 16 11:40:52 vpn01 sshd[3533]: Failed password for invalid user administrator from 46.105.227.206 port 42702 ssh2 ... |
2019-10-16 18:22:49 |
| 178.128.246.123 | attackbots | Oct 15 20:21:47 auw2 sshd\[4714\]: Invalid user client from 178.128.246.123 Oct 15 20:21:47 auw2 sshd\[4714\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.246.123 Oct 15 20:21:49 auw2 sshd\[4714\]: Failed password for invalid user client from 178.128.246.123 port 57896 ssh2 Oct 15 20:25:49 auw2 sshd\[5055\]: Invalid user tecnici from 178.128.246.123 Oct 15 20:25:49 auw2 sshd\[5055\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.246.123 |
2019-10-16 18:18:37 |
| 188.165.211.181 | attack | port scan and connect, tcp 2121 (ccproxy-ftp) |
2019-10-16 18:39:52 |
| 179.127.175.202 | attackbotsspam | Unauthorized SSH login attempts |
2019-10-16 18:34:49 |
| 2600:380:9a77:2eef:484e:58c0:ea3c:7bd6 | attackbots | Emotionally unstable man hacks into my email |
2019-10-16 18:36:09 |
| 23.236.75.115 | attackbotsspam | Unauthorised access (Oct 16) SRC=23.236.75.115 LEN=40 TTL=240 ID=51577 TCP DPT=1433 WINDOW=1024 SYN |
2019-10-16 18:33:32 |
| 46.188.44.45 | attack | Oct 14 18:55:29 h1637304 sshd[12624]: reveeclipse mapping checking getaddrinfo for broadband-46-188-44-45.2com.net [46.188.44.45] failed - POSSIBLE BREAK-IN ATTEMPT! Oct 14 18:55:29 h1637304 sshd[12624]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.188.44.45 user=r.r Oct 14 18:55:30 h1637304 sshd[12624]: Failed password for r.r from 46.188.44.45 port 38124 ssh2 Oct 14 18:55:30 h1637304 sshd[12624]: Received disconnect from 46.188.44.45: 11: Bye Bye [preauth] Oct 14 19:03:34 h1637304 sshd[17222]: reveeclipse mapping checking getaddrinfo for broadband-46-188-44-45.2com.net [46.188.44.45] failed - POSSIBLE BREAK-IN ATTEMPT! Oct 14 19:03:34 h1637304 sshd[17222]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.188.44.45 user=www-data Oct 14 19:03:36 h1637304 sshd[17222]: Failed password for www-data from 46.188.44.45 port 47952 ssh2 Oct 14 19:03:36 h1637304 sshd[17222]: Received discon........ ------------------------------- |
2019-10-16 18:32:39 |