City: Bishkek
Region: Bishkek
Country: Kyrgyzstan
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#
NetRange: 146.120.0.0 - 146.120.255.255
CIDR: 146.120.0.0/16
NetName: RIPE-ERX-146-120-0-0
NetHandle: NET-146-120-0-0-1
Parent: NET146 (NET-146-0-0-0-0)
NetType: Early Registrations, Transferred to RIPE NCC
OriginAS:
Organization: RIPE Network Coordination Centre (RIPE)
RegDate: 2010-11-03
Updated: 2025-02-10
Comment: These addresses have been further assigned to users in the RIPE NCC region. Please note that the organization and point of contact details listed below are those of the RIPE NCC not the current address holder. ** You can find user contact information for the current address holder in the RIPE database at http://www.ripe.net/whois.
Ref: https://rdap.arin.net/registry/ip/146.120.0.0
ResourceLink: https://apps.db.ripe.net/db-web-ui/query
ResourceLink: whois.ripe.net
OrgName: RIPE Network Coordination Centre
OrgId: RIPE
Address: P.O. Box 10096
City: Amsterdam
StateProv:
PostalCode: 1001EB
Country: NL
RegDate:
Updated: 2013-07-29
Ref: https://rdap.arin.net/registry/entity/RIPE
ReferralServer: whois.ripe.net
ResourceLink: https://apps.db.ripe.net/db-web-ui/query
OrgTechHandle: RNO29-ARIN
OrgTechName: RIPE NCC Operations
OrgTechPhone: +31 20 535 4444
OrgTechEmail: hostmaster@ripe.net
OrgTechRef: https://rdap.arin.net/registry/entity/RNO29-ARIN
OrgAbuseHandle: ABUSE3850-ARIN
OrgAbuseName: Abuse Contact
OrgAbusePhone: +31205354444
OrgAbuseEmail: abuse@ripe.net
OrgAbuseRef: https://rdap.arin.net/registry/entity/ABUSE3850-ARIN
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#; <<>> DiG 9.10.3-P4-Ubuntu <<>> 146.120.230.110
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62334
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;146.120.230.110. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026103101 1800 900 604800 86400
;; Query time: 31 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Nov 01 11:53:17 CST 2026
;; MSG SIZE rcvd: 108Host 110.230.120.146.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 110.230.120.146.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 189.89.13.196 | attackspam | Lines containing failures of 189.89.13.196 auth.log:Sep 24 14:35:12 omfg sshd[30123]: Connection from 189.89.13.196 port 7955 on 78.46.60.16 port 22 auth.log:Sep 24 14:35:12 omfg sshd[30123]: Did not receive identification string from 189.89.13.196 auth.log:Sep 24 14:35:14 omfg sshd[30252]: Connection from 189.89.13.196 port 6657 on 78.46.60.40 port 22 auth.log:Sep 24 14:35:14 omfg sshd[30255]: Connection from 189.89.13.196 port 7696 on 78.46.60.41 port 22 auth.log:Sep 24 14:35:14 omfg sshd[30258]: Connection from 189.89.13.196 port 6109 on 78.46.60.42 port 22 auth.log:Sep 24 14:35:14 omfg sshd[30252]: Did not receive identification string from 189.89.13.196 auth.log:Sep 24 14:35:14 omfg sshd[30255]: Did not receive identification string from 189.89.13.196 auth.log:Sep 24 14:35:14 omfg sshd[30258]: Did not receive identification string from 189.89.13.196 auth.log:Sep 24 14:35:14 omfg sshd[30270]: Connection from 189.89.13.196 port 6986 on 78.46.60.50 port 22 auth.log:Sep........ ------------------------------ |
2019-09-25 00:28:34 |
| 145.239.83.89 | attack | Sep 24 17:51:56 vps01 sshd[26825]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=145.239.83.89 Sep 24 17:51:58 vps01 sshd[26825]: Failed password for invalid user billie from 145.239.83.89 port 51646 ssh2 |
2019-09-25 00:23:46 |
| 198.27.90.106 | attackspam | Sep 24 16:53:19 v22019058497090703 sshd[24482]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.27.90.106 Sep 24 16:53:21 v22019058497090703 sshd[24482]: Failed password for invalid user 12345678 from 198.27.90.106 port 36998 ssh2 Sep 24 16:57:54 v22019058497090703 sshd[24865]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.27.90.106 ... |
2019-09-24 23:57:54 |
| 46.38.144.32 | attack | Sep 24 17:52:42 relay postfix/smtpd\[20537\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Sep 24 17:53:05 relay postfix/smtpd\[6694\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Sep 24 17:55:08 relay postfix/smtpd\[24766\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: VXNlcm5hbWU6 Sep 24 17:55:34 relay postfix/smtpd\[6694\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: VXNlcm5hbWU6 Sep 24 17:57:35 relay postfix/smtpd\[20537\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2019-09-25 00:00:43 |
| 139.99.148.4 | attackspam | Brute forcing Wordpress login |
2019-09-25 00:25:42 |
| 103.14.33.229 | attack | Sep 24 18:55:53 www sshd\[79500\]: Invalid user oracle from 103.14.33.229 Sep 24 18:55:53 www sshd\[79500\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.14.33.229 Sep 24 18:55:55 www sshd\[79500\]: Failed password for invalid user oracle from 103.14.33.229 port 44256 ssh2 ... |
2019-09-25 00:31:35 |
| 61.147.80.222 | attack | Sep 24 17:50:25 dedicated sshd[11186]: Invalid user ts from 61.147.80.222 port 45379 |
2019-09-25 00:33:04 |
| 223.166.186.114 | attackbotsspam | Sep 24 12:51:47 work-partkepr sshd\[31090\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.166.186.114 user=root Sep 24 12:51:49 work-partkepr sshd\[31090\]: Failed password for root from 223.166.186.114 port 51007 ssh2 ... |
2019-09-25 00:10:17 |
| 217.16.11.115 | attack | Sep 24 14:27:31 server2101 sshd[29292]: Invalid user elena from 217.16.11.115 port 43968 Sep 24 14:27:31 server2101 sshd[29292]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.16.11.115 Sep 24 14:27:32 server2101 sshd[29292]: Failed password for invalid user elena from 217.16.11.115 port 43968 ssh2 Sep 24 14:27:32 server2101 sshd[29292]: Received disconnect from 217.16.11.115 port 43968:11: Bye Bye [preauth] Sep 24 14:27:32 server2101 sshd[29292]: Disconnected from 217.16.11.115 port 43968 [preauth] Sep 24 14:36:51 server2101 sshd[29399]: Invalid user jira from 217.16.11.115 port 32461 Sep 24 14:36:51 server2101 sshd[29399]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.16.11.115 ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=217.16.11.115 |
2019-09-25 00:30:15 |
| 178.33.216.187 | attackbotsspam | Sep 24 10:04:34 ny01 sshd[18974]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.33.216.187 Sep 24 10:04:36 ny01 sshd[18974]: Failed password for invalid user uftp from 178.33.216.187 port 54344 ssh2 Sep 24 10:08:57 ny01 sshd[19752]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.33.216.187 |
2019-09-24 23:54:05 |
| 27.73.183.246 | attackbotsspam | ssh failed login |
2019-09-25 00:37:04 |
| 78.198.69.64 | attack | Sep 24 19:42:18 lcl-usvr-01 sshd[23169]: Invalid user pi from 78.198.69.64 Sep 24 19:42:19 lcl-usvr-01 sshd[23171]: Invalid user pi from 78.198.69.64 Sep 24 19:42:19 lcl-usvr-01 sshd[23169]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=78.198.69.64 Sep 24 19:42:18 lcl-usvr-01 sshd[23169]: Invalid user pi from 78.198.69.64 Sep 24 19:42:20 lcl-usvr-01 sshd[23169]: Failed password for invalid user pi from 78.198.69.64 port 33172 ssh2 Sep 24 19:42:19 lcl-usvr-01 sshd[23171]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=78.198.69.64 Sep 24 19:42:19 lcl-usvr-01 sshd[23171]: Invalid user pi from 78.198.69.64 Sep 24 19:42:20 lcl-usvr-01 sshd[23171]: Failed password for invalid user pi from 78.198.69.64 port 33174 ssh2 |
2019-09-25 00:15:35 |
| 192.42.116.17 | attackspambots | 2019-09-24T14:38:16.916459abusebot.cloudsearch.cf sshd\[6537\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=this-is-a-tor-exit-node-hviv117.hviv.nl user=root |
2019-09-25 00:04:16 |
| 121.151.153.108 | attackspambots | Sep 24 17:28:18 XXX sshd[24849]: Invalid user ofsaa from 121.151.153.108 port 36760 |
2019-09-25 00:13:24 |
| 103.9.159.59 | attackbotsspam | Sep 24 12:42:42 sshgateway sshd\[8795\]: Invalid user network3 from 103.9.159.59 Sep 24 12:42:42 sshgateway sshd\[8795\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.9.159.59 Sep 24 12:42:44 sshgateway sshd\[8795\]: Failed password for invalid user network3 from 103.9.159.59 port 45108 ssh2 |
2019-09-24 23:58:50 |