City: unknown
Region: unknown
Country: None
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.121.158.2
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30059
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;104.121.158.2. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021901 1800 900 604800 86400
;; Query time: 32 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 02:07:49 CST 2025
;; MSG SIZE rcvd: 106
2.158.121.104.in-addr.arpa domain name pointer a104-121-158-2.deploy.static.akamaitechnologies.com.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
2.158.121.104.in-addr.arpa name = a104-121-158-2.deploy.static.akamaitechnologies.com.
Authoritative answers can be found from:
| IP | Type | Details | Datetime |
|---|---|---|---|
| 175.24.106.77 | attackbots | ... |
2020-04-16 19:19:05 |
| 45.119.84.254 | attack | SSH authentication failure x 6 reported by Fail2Ban ... |
2020-04-16 19:54:50 |
| 106.87.96.6 | attack | Apr 16 12:08:48 prod4 vsftpd\[32109\]: \[anonymous\] FAIL LOGIN: Client "106.87.96.6" Apr 16 12:08:54 prod4 vsftpd\[32112\]: \[www\] FAIL LOGIN: Client "106.87.96.6" Apr 16 12:08:56 prod4 vsftpd\[32124\]: \[www\] FAIL LOGIN: Client "106.87.96.6" Apr 16 12:08:59 prod4 vsftpd\[32128\]: \[www\] FAIL LOGIN: Client "106.87.96.6" Apr 16 12:09:01 prod4 vsftpd\[32130\]: \[www\] FAIL LOGIN: Client "106.87.96.6" ... |
2020-04-16 19:20:50 |
| 203.110.166.51 | attackbots | Apr 16 12:55:09 cloud sshd[1540]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.110.166.51 Apr 16 12:55:11 cloud sshd[1540]: Failed password for invalid user vbox from 203.110.166.51 port 7208 ssh2 |
2020-04-16 19:17:20 |
| 79.44.247.190 | attackbots | Unauthorized connection attempt detected from IP address 79.44.247.190 to port 8080 |
2020-04-16 19:26:52 |
| 182.75.33.14 | attackspam | Apr 16 09:33:21 docs sshd\[13320\]: Invalid user lockdown from 182.75.33.14Apr 16 09:33:24 docs sshd\[13320\]: Failed password for invalid user lockdown from 182.75.33.14 port 32047 ssh2Apr 16 09:37:35 docs sshd\[13489\]: Invalid user informix from 182.75.33.14Apr 16 09:37:37 docs sshd\[13489\]: Failed password for invalid user informix from 182.75.33.14 port 18962 ssh2Apr 16 09:41:56 docs sshd\[13660\]: Invalid user lsfadmin from 182.75.33.14Apr 16 09:41:57 docs sshd\[13660\]: Failed password for invalid user lsfadmin from 182.75.33.14 port 11705 ssh2 ... |
2020-04-16 19:35:45 |
| 119.42.121.70 | attackspambots | Unauthorized connection attempt from IP address 119.42.121.70 on Port 445(SMB) |
2020-04-16 19:55:45 |
| 92.63.194.22 | attackspam | detected by Fail2Ban |
2020-04-16 19:31:40 |
| 64.215.5.229 | attackbots | Unauthorized connection attempt from IP address 64.215.5.229 on Port 445(SMB) |
2020-04-16 19:47:56 |
| 211.157.2.92 | attackspambots | Apr 16 12:44:40 ns382633 sshd\[5979\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.157.2.92 user=root Apr 16 12:44:42 ns382633 sshd\[5979\]: Failed password for root from 211.157.2.92 port 25708 ssh2 Apr 16 12:46:43 ns382633 sshd\[6760\]: Invalid user yp from 211.157.2.92 port 36841 Apr 16 12:46:43 ns382633 sshd\[6760\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.157.2.92 Apr 16 12:46:46 ns382633 sshd\[6760\]: Failed password for invalid user yp from 211.157.2.92 port 36841 ssh2 |
2020-04-16 19:29:12 |
| 114.67.66.199 | attackbotsspam | Apr 16 11:28:10 h2829583 sshd[11937]: Failed password for root from 114.67.66.199 port 39142 ssh2 |
2020-04-16 19:13:12 |
| 110.78.181.115 | attack | 20/4/15@23:47:01: FAIL: Alarm-Network address from=110.78.181.115 ... |
2020-04-16 19:27:22 |
| 171.99.156.114 | attack | bruteforce detected |
2020-04-16 19:41:36 |
| 203.113.25.21 | attack | Unauthorized connection attempt from IP address 203.113.25.21 on Port 445(SMB) |
2020-04-16 19:57:52 |
| 64.227.35.138 | attack | firewall-block, port(s): 22224/tcp |
2020-04-16 19:34:33 |