City: unknown
Region: unknown
Country: None
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 199.66.30.2
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 43243
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;199.66.30.2. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025012102 1800 900 604800 86400
;; Query time: 35 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 22 08:02:07 CST 2025
;; MSG SIZE rcvd: 104Host 2.30.66.199.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 2.30.66.199.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 78.30.198.41 | attackbotsspam | [portscan] Port scan |
2019-10-08 16:23:26 |
| 195.68.206.250 | attackbotsspam | 10/08/2019-09:04:35.058611 195.68.206.250 Protocol: 6 ET CHAT IRC PING command |
2019-10-08 16:34:56 |
| 184.13.240.142 | attackspambots | (sshd) Failed SSH login from 184.13.240.142 (US/United States/-): 3 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Oct 8 08:36:58 andromeda sshd[22356]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=184.13.240.142 user=root Oct 8 08:37:00 andromeda sshd[22356]: Failed password for root from 184.13.240.142 port 57282 ssh2 Oct 8 08:46:03 andromeda sshd[23392]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=184.13.240.142 user=root |
2019-10-08 16:47:07 |
| 142.4.19.163 | attack | WordPress wp-login brute force :: 142.4.19.163 0.052 BYPASS [08/Oct/2019:14:54:26 1100] [censored_2] "POST /wp-login.php HTTP/1.1" 200 4630 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" |
2019-10-08 16:19:54 |
| 141.98.81.111 | attackbotsspam | Oct 8 10:06:15 mc1 kernel: \[1808373.709173\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=141.98.81.111 DST=159.69.205.51 LEN=60 TOS=0x00 PREC=0x00 TTL=55 ID=10019 DF PROTO=TCP SPT=53640 DPT=22 WINDOW=29200 RES=0x00 SYN URGP=0 Oct 8 10:06:16 mc1 kernel: \[1808374.702571\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=141.98.81.111 DST=159.69.205.51 LEN=60 TOS=0x00 PREC=0x00 TTL=55 ID=10020 DF PROTO=TCP SPT=53640 DPT=22 WINDOW=29200 RES=0x00 SYN URGP=0 Oct 8 10:06:18 mc1 kernel: \[1808376.698385\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=141.98.81.111 DST=159.69.205.51 LEN=60 TOS=0x00 PREC=0x00 TTL=55 ID=10021 DF PROTO=TCP SPT=53640 DPT=22 WINDOW=29200 RES=0x00 SYN URGP=0 ... |
2019-10-08 16:10:52 |
| 192.162.68.244 | attack | Unauthorized SSH login attempts |
2019-10-08 16:45:49 |
| 49.88.112.70 | attackspam | 2019-10-08T03:51:52.537191shield sshd\[3525\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.70 user=root 2019-10-08T03:51:54.429458shield sshd\[3525\]: Failed password for root from 49.88.112.70 port 45211 ssh2 2019-10-08T03:51:56.496558shield sshd\[3525\]: Failed password for root from 49.88.112.70 port 45211 ssh2 2019-10-08T03:51:58.839507shield sshd\[3525\]: Failed password for root from 49.88.112.70 port 45211 ssh2 2019-10-08T03:53:48.238054shield sshd\[4039\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.70 user=root |
2019-10-08 16:44:40 |
| 88.247.250.200 | attack | 2019-10-08T11:26:17.247310tmaserv sshd\[24282\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=88.247.250.200 user=root 2019-10-08T11:26:18.831868tmaserv sshd\[24282\]: Failed password for root from 88.247.250.200 port 60632 ssh2 2019-10-08T11:30:49.198559tmaserv sshd\[24492\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=88.247.250.200 user=root 2019-10-08T11:30:51.124242tmaserv sshd\[24492\]: Failed password for root from 88.247.250.200 port 23246 ssh2 2019-10-08T11:35:14.600868tmaserv sshd\[27204\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=88.247.250.200 user=root 2019-10-08T11:35:16.571851tmaserv sshd\[27204\]: Failed password for root from 88.247.250.200 port 42367 ssh2 ... |
2019-10-08 16:38:22 |
| 159.65.146.141 | attackbotsspam | Oct 8 10:20:59 core sshd[23130]: Invalid user M0tdepasse-123 from 159.65.146.141 port 48314 Oct 8 10:21:00 core sshd[23130]: Failed password for invalid user M0tdepasse-123 from 159.65.146.141 port 48314 ssh2 ... |
2019-10-08 16:27:42 |
| 185.197.30.74 | attackspambots | Oct 7 21:56:26 web9 sshd\[18442\]: Invalid user Jelszo3@1 from 185.197.30.74 Oct 7 21:56:26 web9 sshd\[18442\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.197.30.74 Oct 7 21:56:28 web9 sshd\[18442\]: Failed password for invalid user Jelszo3@1 from 185.197.30.74 port 52696 ssh2 Oct 7 22:00:41 web9 sshd\[19002\]: Invalid user Sydney123 from 185.197.30.74 Oct 7 22:00:41 web9 sshd\[19002\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.197.30.74 |
2019-10-08 16:12:18 |
| 111.231.63.14 | attackbotsspam | Apr 17 16:35:42 ubuntu sshd[28432]: Failed password for invalid user gy from 111.231.63.14 port 43650 ssh2 Apr 17 16:37:54 ubuntu sshd[28768]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.231.63.14 Apr 17 16:37:57 ubuntu sshd[28768]: Failed password for invalid user christian from 111.231.63.14 port 36962 ssh2 Apr 17 16:40:16 ubuntu sshd[29068]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.231.63.14 |
2019-10-08 16:49:50 |
| 111.231.83.112 | attackspambots | Apr 19 15:40:13 ubuntu sshd[13080]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.231.83.112 Apr 19 15:40:15 ubuntu sshd[13080]: Failed password for invalid user effectivecool from 111.231.83.112 port 39182 ssh2 Apr 19 15:42:34 ubuntu sshd[13138]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.231.83.112 Apr 19 15:42:36 ubuntu sshd[13138]: Failed password for invalid user rick from 111.231.83.112 port 33672 ssh2 |
2019-10-08 16:37:43 |
| 103.76.252.6 | attackbotsspam | (sshd) Failed SSH login from 103.76.252.6 (IN/India/252-76-103-khetanisp.net): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Oct 8 09:35:39 server2 sshd[11571]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.76.252.6 user=root Oct 8 09:35:41 server2 sshd[11571]: Failed password for root from 103.76.252.6 port 56865 ssh2 Oct 8 09:45:52 server2 sshd[11878]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.76.252.6 user=root Oct 8 09:45:55 server2 sshd[11878]: Failed password for root from 103.76.252.6 port 20930 ssh2 Oct 8 09:49:54 server2 sshd[11981]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.76.252.6 user=root |
2019-10-08 16:23:54 |
| 190.228.16.101 | attackbots | Oct 8 10:23:35 meumeu sshd[19269]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.228.16.101 Oct 8 10:23:36 meumeu sshd[19269]: Failed password for invalid user Cream2017 from 190.228.16.101 port 44296 ssh2 Oct 8 10:28:27 meumeu sshd[19858]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.228.16.101 ... |
2019-10-08 16:36:29 |
| 180.101.225.122 | attack | IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/180.101.225.122/ CN - 1H : (520) Protection Against DDoS WordPress plugin : "odzyskiwanie danych help-dysk" IP Address Ranges by Country : CN NAME ASN : ASN4134 IP : 180.101.225.122 CIDR : 180.101.224.0/20 PREFIX COUNT : 5430 UNIQUE IP COUNT : 106919680 WYKRYTE ATAKI Z ASN4134 : 1H - 11 3H - 33 6H - 60 12H - 116 24H - 224 DateTime : 2019-10-08 05:54:05 INFO : Port MAX SCAN Scan Detected and Blocked by ADMIN - data recovery |
2019-10-08 16:32:00 |