City: unknown
Region: unknown
Country: Brazil
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 40.102.8.253
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 83
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;40.102.8.253. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025020500 1800 900 604800 86400
;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 05 17:46:28 CST 2025
;; MSG SIZE rcvd: 105Host 253.8.102.40.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 253.8.102.40.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 95.49.8.247 | attackspambots | k+ssh-bruteforce |
2020-04-09 01:14:20 |
| 92.118.38.82 | attackspam | Apr 8 18:44:45 relay postfix/smtpd\[4442\]: warning: unknown\[92.118.38.82\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Apr 8 18:44:55 relay postfix/smtpd\[13829\]: warning: unknown\[92.118.38.82\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Apr 8 18:45:19 relay postfix/smtpd\[4547\]: warning: unknown\[92.118.38.82\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Apr 8 18:45:29 relay postfix/smtpd\[18407\]: warning: unknown\[92.118.38.82\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Apr 8 18:45:53 relay postfix/smtpd\[4442\]: warning: unknown\[92.118.38.82\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-04-09 00:52:55 |
| 192.99.212.132 | attackbots | Apr 8 14:36:06 srv01 sshd[2870]: Invalid user deploy from 192.99.212.132 port 33322 Apr 8 14:36:06 srv01 sshd[2870]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.99.212.132 Apr 8 14:36:06 srv01 sshd[2870]: Invalid user deploy from 192.99.212.132 port 33322 Apr 8 14:36:08 srv01 sshd[2870]: Failed password for invalid user deploy from 192.99.212.132 port 33322 ssh2 Apr 8 14:40:14 srv01 sshd[3198]: Invalid user ftp-user from 192.99.212.132 port 37892 ... |
2020-04-09 00:40:48 |
| 222.186.30.76 | attackbots | sshd brute force attempt |
2020-04-09 01:06:38 |
| 106.75.7.111 | attack | Lines containing failures of 106.75.7.111 Apr 8 12:50:08 ticdesk sshd[14401]: Did not receive identification string from 106.75.7.111 port 58622 Apr 8 13:50:08 commu-intern sshd[25451]: Did not receive identification string from 106.75.7.111 port 39640 Apr 8 13:50:08 cloud sshd[14491]: Did not receive identification string from 106.75.7.111 port 56502 Apr 8 13:50:08 www sshd[23880]: Did not receive identification string from 106.75.7.111 port 59392 Apr 8 13:50:08 commu sshd[19873]: Did not receive identification string from 106.75.7.111 port 41664 Apr 8 13:50:09 desktop sshd[6182]: Did not receive identification string from 106.75.7.111 port 47634 Apr 8 13:50:09 meet sshd[10984]: Did not receive identification string from 106.75.7.111 port 58630 Apr 8 13:55:48 edughostname sshd[739294]: Unable to negotiate whostnameh 106.75.7.111 port 41560: no matching key exchange method found. Their offer: diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-h........ ------------------------------ |
2020-04-09 00:49:52 |
| 218.92.0.168 | attackbots | Apr 8 21:39:14 gw1 sshd[1080]: Failed password for root from 218.92.0.168 port 56619 ssh2 Apr 8 21:39:30 gw1 sshd[1080]: error: maximum authentication attempts exceeded for root from 218.92.0.168 port 56619 ssh2 [preauth] ... |
2020-04-09 00:40:25 |
| 106.12.131.161 | attackbotsspam | Apr 8 14:32:00 xeon sshd[36691]: Failed password for invalid user user from 106.12.131.161 port 42381 ssh2 |
2020-04-09 00:58:37 |
| 198.98.61.24 | attackspambots | Apr 8 17:25:28 debian-2gb-nbg1-2 kernel: \[8618544.845211\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=198.98.61.24 DST=195.201.40.59 LEN=44 TOS=0x08 PREC=0x00 TTL=240 ID=54321 PROTO=TCP SPT=44385 DPT=8080 WINDOW=65535 RES=0x00 SYN URGP=0 |
2020-04-09 00:35:04 |
| 106.12.23.223 | attack | SSH brute force attempt @ 2020-04-08 14:08:32 |
2020-04-09 00:54:18 |
| 120.132.11.186 | attack | Apr 8 17:55:11 odroid64 sshd\[12521\]: User root from 120.132.11.186 not allowed because not listed in AllowUsers Apr 8 17:55:11 odroid64 sshd\[12521\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.132.11.186 user=root ... |
2020-04-09 01:30:15 |
| 49.234.236.174 | attackspam | SSH bruteforce |
2020-04-09 01:03:49 |
| 212.47.232.66 | attackbotsspam | Too many connections or unauthorized access detected from Arctic banned ip |
2020-04-09 01:19:22 |
| 110.144.66.156 | attackspambots | Automatic report - SSH Brute-Force Attack |
2020-04-09 01:30:47 |
| 92.222.36.74 | attackbotsspam | (sshd) Failed SSH login from 92.222.36.74 (FR/France/74.ip-92-222-36.eu): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr 8 17:56:48 srv sshd[26107]: Invalid user alfresco from 92.222.36.74 port 42890 Apr 8 17:56:50 srv sshd[26107]: Failed password for invalid user alfresco from 92.222.36.74 port 42890 ssh2 Apr 8 18:01:51 srv sshd[26223]: Invalid user ubuntu from 92.222.36.74 port 34582 Apr 8 18:01:53 srv sshd[26223]: Failed password for invalid user ubuntu from 92.222.36.74 port 34582 ssh2 Apr 8 18:06:12 srv sshd[26279]: Invalid user user from 92.222.36.74 port 45622 |
2020-04-09 01:09:17 |
| 101.231.146.36 | attackbotsspam | SSH bruteforce |
2020-04-09 01:08:17 |