Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: Germany

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
IP Type Details Datetime
45.93.16.154 attack
Scan port
2023-09-26 16:42:07
45.93.16.154 attack
Scan port
2023-09-14 12:36:57
45.93.16.154 attack
Scan port
2023-09-14 12:35:56
45.93.16.214 attack
Scan port
2023-08-15 12:42:10
45.93.16.240 attack
Scan port
2023-08-02 12:48:29
45.93.16.48 attack
Scan port DDoS
2023-03-23 15:05:07
45.93.16.216 attack
Scan port DDoS
2023-03-23 15:04:54
45.93.16.216 attack
Scan port DDoS
2023-03-23 15:04:28
45.93.16.81 attack
Scan port DDoS
2023-03-23 15:04:05
45.93.16.32 attack
Port scan
2023-02-08 13:52:26
45.93.16.23 attack
Port scan
2023-01-23 13:54:04
45.93.16.100 attack
Port scan
2023-01-23 13:52:29
45.93.16.22 attack
DdoS
2023-01-23 13:50:44
45.93.16.189 attack
Brute-force
2023-01-23 13:48:42
45.93.16.24 attack
port scan
2023-01-20 13:43:49
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 45.93.16.124
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 47259
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;45.93.16.124.			IN	A

;; AUTHORITY SECTION:
.			579	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2022070400 1800 900 604800 86400

;; Query time: 69 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jul 04 17:44:56 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 124.16.93.45.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 124.16.93.45.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
188.131.228.31 attack
Nov 16 10:07:43 sachi sshd\[4613\]: Invalid user myrt from 188.131.228.31
Nov 16 10:07:43 sachi sshd\[4613\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.131.228.31
Nov 16 10:07:45 sachi sshd\[4613\]: Failed password for invalid user myrt from 188.131.228.31 port 34480 ssh2
Nov 16 10:11:44 sachi sshd\[5031\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.131.228.31  user=backup
Nov 16 10:11:46 sachi sshd\[5031\]: Failed password for backup from 188.131.228.31 port 42348 ssh2
2019-11-17 04:15:55
178.62.37.168 attackspam
Nov 16 22:29:08 sauna sshd[42131]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.62.37.168
Nov 16 22:29:09 sauna sshd[42131]: Failed password for invalid user quintanilha from 178.62.37.168 port 52731 ssh2
...
2019-11-17 04:35:59
42.6.26.40 attackspam
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/42.6.26.40/ 
 
 CN - 1H : (650)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : CN 
 NAME ASN : ASN4837 
 
 IP : 42.6.26.40 
 
 CIDR : 42.4.0.0/14 
 
 PREFIX COUNT : 1262 
 
 UNIQUE IP COUNT : 56665856 
 
 
 ATTACKS DETECTED ASN4837 :  
  1H - 9 
  3H - 18 
  6H - 41 
 12H - 130 
 24H - 245 
 
 DateTime : 2019-11-16 15:47:02 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-11-17 04:20:01
185.176.27.178 attackbotsspam
Nov 16 21:26:07 mc1 kernel: \[5222231.989412\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.178 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=59043 PROTO=TCP SPT=45871 DPT=27082 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov 16 21:27:48 mc1 kernel: \[5222332.912883\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.178 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=37609 PROTO=TCP SPT=45871 DPT=29524 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov 16 21:30:30 mc1 kernel: \[5222494.695074\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.178 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=19716 PROTO=TCP SPT=45871 DPT=24973 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2019-11-17 04:31:18
164.132.54.246 attackspam
Nov 16 16:49:16 * sshd[18027]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.54.246
Nov 16 16:49:18 * sshd[18027]: Failed password for invalid user surendran from 164.132.54.246 port 42083 ssh2
2019-11-17 04:35:32
180.76.188.189 attackspam
Nov 16 13:33:58 Tower sshd[29191]: Connection from 180.76.188.189 port 40926 on 192.168.10.220 port 22
Nov 16 13:33:59 Tower sshd[29191]: Invalid user mircte from 180.76.188.189 port 40926
Nov 16 13:33:59 Tower sshd[29191]: error: Could not get shadow information for NOUSER
Nov 16 13:33:59 Tower sshd[29191]: Failed password for invalid user mircte from 180.76.188.189 port 40926 ssh2
Nov 16 13:34:00 Tower sshd[29191]: Received disconnect from 180.76.188.189 port 40926:11: Bye Bye [preauth]
Nov 16 13:34:00 Tower sshd[29191]: Disconnected from invalid user mircte 180.76.188.189 port 40926 [preauth]
2019-11-17 04:45:53
177.9.18.21 attack
Unauthorised access (Nov 16) SRC=177.9.18.21 LEN=40 TOS=0x10 PREC=0x40 TTL=238 ID=44466 DF TCP DPT=8080 WINDOW=14600 SYN
2019-11-17 04:52:08
181.49.219.114 attackbots
SSH invalid-user multiple login attempts
2019-11-17 04:28:29
104.238.99.130 attackbots
Automatic report - Banned IP Access
2019-11-17 04:13:19
1.9.46.177 attack
Nov 16 17:00:24 ns381471 sshd[18784]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.9.46.177
Nov 16 17:00:27 ns381471 sshd[18784]: Failed password for invalid user nedda from 1.9.46.177 port 50810 ssh2
2019-11-17 04:25:56
58.213.128.106 attackspambots
Invalid user sterk from 58.213.128.106 port 44577
2019-11-17 04:15:09
128.134.30.40 attackbots
Nov 16 15:28:44 l02a sshd[4656]: Invalid user vq from 128.134.30.40
Nov 16 15:28:44 l02a sshd[4656]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.134.30.40 
Nov 16 15:28:44 l02a sshd[4656]: Invalid user vq from 128.134.30.40
Nov 16 15:28:45 l02a sshd[4656]: Failed password for invalid user vq from 128.134.30.40 port 25023 ssh2
2019-11-17 04:52:35
58.249.123.38 attack
Nov 16 18:06:35 vserver sshd\[3788\]: Invalid user musikbot from 58.249.123.38Nov 16 18:06:37 vserver sshd\[3788\]: Failed password for invalid user musikbot from 58.249.123.38 port 58382 ssh2Nov 16 18:11:14 vserver sshd\[3834\]: Invalid user deploy from 58.249.123.38Nov 16 18:11:15 vserver sshd\[3834\]: Failed password for invalid user deploy from 58.249.123.38 port 35746 ssh2
...
2019-11-17 04:46:50
185.143.223.80 attack
Nov 16 19:42:33   TCP Attack: SRC=185.143.223.80 DST=[Masked] LEN=40 TOS=0x08 PREC=0x20 TTL=243  PROTO=TCP SPT=8080 DPT=13873 WINDOW=1024 RES=0x00 SYN URGP=0
2019-11-17 04:39:16
164.132.170.91 attackspambots
RDP Bruteforce
2019-11-17 04:39:03

Recently Reported IPs

172.245.92.202 47.245.53.219 181.174.102.246 15.204.21.136
68.249.177.143 231.18.25.14 202.93.167.198 149.129.190.153
149.129.190.47 149.129.190.229 149.129.190.97 149.129.190.227
103.66.78.189 125.15.177.248 188.241.177.149 192.168.2.14
192.168.2.220 81.75.80.25 2.56.184.159 142.132.135.170