City: unknown
Region: unknown
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 34.140.34.154
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 16549
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;34.140.34.154. IN A
;; AUTHORITY SECTION:
. 384 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022010502 1800 900 604800 86400
;; Query time: 51 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 06 11:18:37 CST 2022
;; MSG SIZE rcvd: 106
154.34.140.34.in-addr.arpa domain name pointer 154.34.140.34.bc.googleusercontent.com.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
154.34.140.34.in-addr.arpa name = 154.34.140.34.bc.googleusercontent.com.
Authoritative answers can be found from:
IP | Type | Details | Datetime |
---|---|---|---|
49.234.43.39 | attack | ssh brute force |
2020-04-03 13:29:24 |
18.212.153.220 | attack | Apr 3 04:50:20 www_kotimaassa_fi sshd[25842]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=18.212.153.220 Apr 3 04:50:23 www_kotimaassa_fi sshd[25842]: Failed password for invalid user xieweihao from 18.212.153.220 port 33156 ssh2 ... |
2020-04-03 13:21:09 |
123.30.237.63 | attack | " " |
2020-04-03 13:44:07 |
45.55.145.31 | attackspambots | 5x Failed Password |
2020-04-03 13:08:38 |
77.70.96.195 | attack | Apr 3 05:52:41 vpn01 sshd[3366]: Failed password for root from 77.70.96.195 port 33624 ssh2 Apr 3 05:55:36 vpn01 sshd[3394]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.70.96.195 ... |
2020-04-03 13:19:53 |
219.137.231.217 | attackspam | Apr 3 06:28:22 debian-2gb-nbg1-2 kernel: \[8147143.085874\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=219.137.231.217 DST=195.201.40.59 LEN=52 TOS=0x00 PREC=0x00 TTL=114 ID=22005 DF PROTO=TCP SPT=64750 DPT=1433 WINDOW=8192 RES=0x00 SYN URGP=0 |
2020-04-03 13:00:32 |
49.232.17.7 | attackbots | Apr 2 19:29:18 wbs sshd\[5332\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.17.7 user=root Apr 2 19:29:20 wbs sshd\[5332\]: Failed password for root from 49.232.17.7 port 51152 ssh2 Apr 2 19:33:52 wbs sshd\[5633\]: Invalid user liugang from 49.232.17.7 Apr 2 19:33:52 wbs sshd\[5633\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.17.7 Apr 2 19:33:54 wbs sshd\[5633\]: Failed password for invalid user liugang from 49.232.17.7 port 45496 ssh2 |
2020-04-03 13:45:02 |
162.243.129.100 | attackbotsspam | *Port Scan* detected from 162.243.129.100 (US/United States/California/San Francisco/zg-0312c-88.stretchoid.com). 4 hits in the last 231 seconds |
2020-04-03 13:42:22 |
40.73.97.99 | attack | 2020-04-03T04:09:50.543815shield sshd\[14147\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=40.73.97.99 user=root 2020-04-03T04:09:52.398444shield sshd\[14147\]: Failed password for root from 40.73.97.99 port 46378 ssh2 2020-04-03T04:14:36.305935shield sshd\[15391\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=40.73.97.99 user=root 2020-04-03T04:14:38.090366shield sshd\[15391\]: Failed password for root from 40.73.97.99 port 53826 ssh2 2020-04-03T04:19:19.098677shield sshd\[16600\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=40.73.97.99 user=root |
2020-04-03 13:16:34 |
2001:41d0:52:1100::47 | attackspambots | xmlrpc attack |
2020-04-03 13:33:23 |
23.94.151.60 | attack | (From janaholloway52@gmail.com) Hello! Have you seen how your website ranks in Google search results? After running some proprietary SEO software on your website, I discovered that your website is not ranking for important and profitable keywords related to your niche. Making sure that your site appears on the top of search results can increase not just your online visibility, but also the number of sales you get. If you'd like, I'll give you a free consultation to guide you in determining where your site currently stands, what needs to be done, and what to expect in terms of results if you're curious to know more. I deliver top-notch results at a cheap price. All the information I'll be giving you can benefit your business whether or not you want to avail of my services. Please let me know if you're interested so we can set up a call. I hope to speak with you soon. Thank you! Jana Holloway |
2020-04-03 13:29:41 |
45.125.65.35 | attackspambots | Apr 3 07:17:28 relay postfix/smtpd\[8161\]: warning: unknown\[45.125.65.35\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Apr 3 07:17:37 relay postfix/smtpd\[30973\]: warning: unknown\[45.125.65.35\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Apr 3 07:26:36 relay postfix/smtpd\[10109\]: warning: unknown\[45.125.65.35\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Apr 3 07:35:53 relay postfix/smtpd\[8161\]: warning: unknown\[45.125.65.35\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Apr 3 07:36:04 relay postfix/smtpd\[17732\]: warning: unknown\[45.125.65.35\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-04-03 13:48:14 |
120.41.156.149 | attack | Apr 1 04:07:38 svapp01 sshd[9290]: reveeclipse mapping checking getaddrinfo for 149.156.41.120.broad.xm.fj.dynamic.163data.com.cn [120.41.156.149] failed - POSSIBLE BREAK-IN ATTEMPT! Apr 1 04:07:38 svapp01 sshd[9290]: User r.r from 120.41.156.149 not allowed because not listed in AllowUsers Apr 1 04:07:38 svapp01 sshd[9290]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.41.156.149 user=r.r Apr 1 04:07:41 svapp01 sshd[9290]: Failed password for invalid user r.r from 120.41.156.149 port 9281 ssh2 Apr 1 04:07:41 svapp01 sshd[9290]: Received disconnect from 120.41.156.149: 11: Bye Bye [preauth] Apr 1 04:17:46 svapp01 sshd[12642]: reveeclipse mapping checking getaddrinfo for 149.156.41.120.broad.xm.fj.dynamic.163data.com.cn [120.41.156.149] failed - POSSIBLE BREAK-IN ATTEMPT! Apr 1 04:17:46 svapp01 sshd[12642]: User r.r from 120.41.156.149 not allowed because not listed in AllowUsers Apr 1 04:17:46 svapp01 sshd[12642]: p........ ------------------------------- |
2020-04-03 13:48:51 |
188.254.0.226 | attackbots | Invalid user stb from 188.254.0.226 port 48772 |
2020-04-03 13:31:58 |
122.165.146.202 | attack | SSH authentication failure x 6 reported by Fail2Ban ... |
2020-04-03 13:15:11 |