City: unknown
Region: unknown
Country: United States of America (the)
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 23.214.194.30
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 60831
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;23.214.194.30. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025020601 1800 900 604800 86400
;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 07 04:29:47 CST 2025
;; MSG SIZE rcvd: 10630.194.214.23.in-addr.arpa domain name pointer a23-214-194-30.deploy.static.akamaitechnologies.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
30.194.214.23.in-addr.arpa name = a23-214-194-30.deploy.static.akamaitechnologies.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 103.108.244.4 | attack | 2019-10-16 17:05:47,891 fail2ban.actions \[1778\]: NOTICE \[sshd\] Ban 103.108.244.4 2019-10-16 17:41:28,923 fail2ban.actions \[1778\]: NOTICE \[sshd\] Ban 103.108.244.4 2019-10-16 18:14:42,464 fail2ban.actions \[1778\]: NOTICE \[sshd\] Ban 103.108.244.4 2019-10-16 18:49:09,618 fail2ban.actions \[1778\]: NOTICE \[sshd\] Ban 103.108.244.4 2019-10-16 19:21:52,724 fail2ban.actions \[1778\]: NOTICE \[sshd\] Ban 103.108.244.4 ... |
2019-10-17 02:14:53 |
| 79.105.165.110 | attack | Forum spam |
2019-10-17 02:43:21 |
| 165.227.9.184 | attackbotsspam | Oct 16 14:02:59 server sshd\[9354\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.9.184 user=root Oct 16 14:03:00 server sshd\[9354\]: Failed password for root from 165.227.9.184 port 44940 ssh2 Oct 16 14:12:01 server sshd\[12318\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.9.184 user=root Oct 16 14:12:03 server sshd\[12318\]: Failed password for root from 165.227.9.184 port 59161 ssh2 Oct 16 14:15:42 server sshd\[13648\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.9.184 user=root Oct 16 14:15:44 server sshd\[13648\]: Failed password for root from 165.227.9.184 port 43928 ssh2 Oct 16 15:16:24 server sshd\[31829\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.9.184 user=root Oct 16 15:16:26 server sshd\[31829\]: Failed password for root from 165.227.9.184 port 21278 ... |
2019-10-17 02:27:37 |
| 198.108.67.39 | attackbots | MultiHost/MultiPort Probe, Scan, Hack - |
2019-10-17 02:17:14 |
| 36.89.93.233 | attack | Oct 16 13:08:33 server sshd\[24787\]: Failed password for root from 36.89.93.233 port 44198 ssh2 Oct 16 14:10:31 server sshd\[11934\]: Invalid user pASSWORD!@\#$%\^\&\* from 36.89.93.233 Oct 16 14:10:31 server sshd\[11934\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.89.93.233 Oct 16 14:10:33 server sshd\[11934\]: Failed password for invalid user pASSWORD!@\#$%\^\&\* from 36.89.93.233 port 53272 ssh2 Oct 16 14:15:41 server sshd\[13604\]: Invalid user Burger@2017 from 36.89.93.233 Oct 16 14:15:41 server sshd\[13604\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.89.93.233 Oct 16 14:15:43 server sshd\[13604\]: Failed password for invalid user Burger@2017 from 36.89.93.233 port 32832 ssh2 Oct 16 15:18:42 server sshd\[32264\]: Invalid user 19july87 from 36.89.93.233 Oct 16 15:18:42 server sshd\[32264\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rh ... |
2019-10-17 02:28:28 |
| 112.27.129.78 | attack | WP user enumerator |
2019-10-17 02:33:35 |
| 175.197.77.3 | attack | Oct 16 13:51:37 game-panel sshd[31179]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.197.77.3 Oct 16 13:51:39 game-panel sshd[31179]: Failed password for invalid user cdoran from 175.197.77.3 port 40859 ssh2 Oct 16 13:57:50 game-panel sshd[31356]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.197.77.3 |
2019-10-17 02:20:49 |
| 92.119.160.107 | attackspam | Oct 16 19:58:04 mc1 kernel: \[2535054.139217\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=92.119.160.107 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=24352 PROTO=TCP SPT=48828 DPT=11971 WINDOW=1024 RES=0x00 SYN URGP=0 Oct 16 19:58:23 mc1 kernel: \[2535073.930507\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=92.119.160.107 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=43636 PROTO=TCP SPT=48828 DPT=12380 WINDOW=1024 RES=0x00 SYN URGP=0 Oct 16 20:00:11 mc1 kernel: \[2535181.733039\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=92.119.160.107 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=35558 PROTO=TCP SPT=48828 DPT=12174 WINDOW=1024 RES=0x00 SYN URGP=0 ... |
2019-10-17 02:31:36 |
| 58.225.2.61 | attack | 58.225.2.61 - - [16/Oct/2019:13:40:21 +0200] "GET /wp-login.php HTTP/1.1" 200 1237 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 58.225.2.61 - - [16/Oct/2019:13:40:22 +0200] "POST /wp-login.php HTTP/1.1" 200 1632 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 58.225.2.61 - - [16/Oct/2019:13:40:24 +0200] "GET /wp-login.php HTTP/1.1" 200 1237 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 58.225.2.61 - - [16/Oct/2019:13:40:25 +0200] "POST /wp-login.php HTTP/1.1" 200 1607 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 58.225.2.61 - - [16/Oct/2019:13:40:26 +0200] "GET /wp-login.php HTTP/1.1" 200 1237 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 58.225.2.61 - - [16/Oct/2019:13:40:29 +0200] "POST /wp-login.php HTTP/1.1" 200 1608 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" ... |
2019-10-17 02:46:14 |
| 201.47.158.130 | attackspambots | Oct 16 17:02:38 unicornsoft sshd\[31213\]: User root from 201.47.158.130 not allowed because not listed in AllowUsers Oct 16 17:02:38 unicornsoft sshd\[31213\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.47.158.130 user=root Oct 16 17:02:40 unicornsoft sshd\[31213\]: Failed password for invalid user root from 201.47.158.130 port 39188 ssh2 |
2019-10-17 02:19:46 |
| 107.155.113.36 | attackbotsspam | from: datuilaralxenofeni@cox.net and jegrlaralenofeni@cox.net |
2019-10-17 02:11:04 |
| 62.83.197.11 | attack | Fail2Ban Ban Triggered |
2019-10-17 02:06:29 |
| 198.108.67.60 | attackbotsspam | MultiHost/MultiPort Probe, Scan, Hack - |
2019-10-17 02:43:46 |
| 201.116.194.210 | attack | Oct 16 19:46:28 MK-Soft-VM6 sshd[19109]: Failed password for invalid user +++ from 201.116.194.210 port 48403 ssh2 Oct 16 19:50:49 MK-Soft-VM6 sshd[19132]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.116.194.210 ... |
2019-10-17 02:16:48 |
| 210.133.240.218 | attackbots | Spam emails used this IP address for the URLs in their messages. This kind of spam had the following features.: - They passed the SPF authentication checks. - They used networks 210.133.240.0/22 (netname: BOOT-NET) for their SMTP servers. - They used the following domains for the email addresses and URLs.: anybodyamazed.jp, askappliance.jp, hamburgermotorboat.jp, holidayarchitectural.jp, 5dfis3r.com, 5iami22.com, d8hchg5.com, myp8tkm.com, wh422c8.com, wxzimgi.com, classificationclarity.com, swampcapsule.com, tagcorps.com, etc. - Those URLs used the following name sever pairs.: -- ns1.anyaltitude.jp and ns2 -- ns1.abandonedemigrate.com and ns2 -- ns1.greetincline.jp and ns2 -- ns1.himprotestant.jp and ns2 -- ns1.swampcapsule.com and ns2 -- ns1.yybuijezu.com and ns2 |
2019-10-17 02:16:24 |