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.134.144.249 attack
Scan port
2023-08-17 12:49:52
45.134.144.249 attack
Scan port
2023-08-02 12:45:59
45.134.144.238 attack
Scan port
2023-08-02 12:43:51
45.134.144.77 botsattack
Scan port VoiP
2023-06-13 21:56:49
45.134.144.77 attack
Scan port
2023-06-13 21:26:32
45.134.144.4 attack
Scan port
2023-03-14 13:42:08
45.134.144.4 attack
Scan port
2023-03-09 13:49:08
45.134.144.138 attack
Port scan
2023-01-25 13:54:15
45.134.144.132 attack
Scan port
2022-12-29 13:47:07
45.134.144.101 attack
Brute scan
2022-11-29 13:40:26
45.134.144.101 attack
Scan port
2022-11-07 13:47:19
45.134.144.131 attackbots
Apr 21 07:29:10 hosting sshd[31798]: Invalid user oracle2 from 45.134.144.131 port 52782
...
2020-04-21 12:40:53
45.134.144.131 attackbotsspam
$f2bV_matches
2020-04-21 05:26:17
45.134.144.131 attack
SSH Brute-Force Attack
2020-04-21 01:01:49
45.134.144.131 attack
Feb 28 09:18:40 localhost sshd\[23112\]: Invalid user nagios from 45.134.144.131 port 55986
Feb 28 09:18:40 localhost sshd\[23112\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.134.144.131
Feb 28 09:18:42 localhost sshd\[23112\]: Failed password for invalid user nagios from 45.134.144.131 port 55986 ssh2
2020-02-28 16:45:28
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 45.134.144.94
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 46171
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;45.134.144.94.			IN	A

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

;; Query time: 49 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jan 12 00:48:31 CST 2020
;; MSG SIZE  rcvd: 117
Host info
Host 94.144.134.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 94.144.134.45.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
111.204.160.118 attackspam
Aug 11 09:33:19 mail sshd\[24162\]: Failed password for invalid user kmysclub from 111.204.160.118 port 46570 ssh2
Aug 11 09:55:40 mail sshd\[24526\]: Invalid user mwang from 111.204.160.118 port 22535
...
2019-08-11 17:08:59
88.35.102.54 attackspambots
Aug 11 10:56:57 OPSO sshd\[21988\]: Invalid user teamspeak from 88.35.102.54 port 51468
Aug 11 10:56:57 OPSO sshd\[21988\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=88.35.102.54
Aug 11 10:56:59 OPSO sshd\[21988\]: Failed password for invalid user teamspeak from 88.35.102.54 port 51468 ssh2
Aug 11 11:00:53 OPSO sshd\[22716\]: Invalid user bonaka from 88.35.102.54 port 40180
Aug 11 11:00:53 OPSO sshd\[22716\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=88.35.102.54
2019-08-11 17:02:42
188.165.200.217 attackbots
Automatic report - Banned IP Access
2019-08-11 17:00:53
164.160.33.31 attackbotsspam
Aug 11 09:58:44 h2177944 kernel: \[3834107.832095\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=164.160.33.31 DST=85.214.117.9 LEN=60 TOS=0x00 PREC=0x00 TTL=52 ID=49409 DF PROTO=TCP SPT=35361 DPT=1433 WINDOW=28200 RES=0x00 SYN URGP=0 
Aug 11 09:58:45 h2177944 kernel: \[3834108.852222\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=164.160.33.31 DST=85.214.117.9 LEN=60 TOS=0x00 PREC=0x00 TTL=52 ID=49410 DF PROTO=TCP SPT=35361 DPT=1433 WINDOW=28200 RES=0x00 SYN URGP=0 
Aug 11 09:58:45 h2177944 kernel: \[3834109.503389\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=164.160.33.31 DST=85.214.117.9 LEN=60 TOS=0x00 PREC=0x00 TTL=52 ID=42058 DF PROTO=TCP SPT=51206 DPT=6379 WINDOW=28200 RES=0x00 SYN URGP=0 
Aug 11 09:58:46 h2177944 kernel: \[3834110.495307\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=164.160.33.31 DST=85.214.117.9 LEN=60 TOS=0x00 PREC=0x00 TTL=52 ID=42059 DF PROTO=TCP SPT=51206 DPT=6379 WINDOW=28200 RES=0x00 SYN URGP=0 
Aug 11 09:58:47 h2177944 kernel: \[3834110.764575\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=164.160.33.31 DST=
2019-08-11 16:40:42
222.186.52.124 attackspam
Aug 11 15:56:21 webhost01 sshd[26576]: Failed password for root from 222.186.52.124 port 61654 ssh2
...
2019-08-11 17:22:51
116.196.81.5 attackbots
SSH Brute-Force reported by Fail2Ban
2019-08-11 17:05:49
188.187.189.90 attackspambots
[portscan] Port scan
2019-08-11 17:14:53
180.180.108.91 attack
Aug 11 09:57:34 ubuntu-2gb-nbg1-dc3-1 sshd[14819]: Failed password for root from 180.180.108.91 port 35451 ssh2
Aug 11 09:57:39 ubuntu-2gb-nbg1-dc3-1 sshd[14819]: error: maximum authentication attempts exceeded for root from 180.180.108.91 port 35451 ssh2 [preauth]
...
2019-08-11 17:13:14
194.181.104.248 attackbotsspam
Aug 11 11:31:32 www5 sshd\[62817\]: Invalid user ftpuser from 194.181.104.248
Aug 11 11:31:32 www5 sshd\[62817\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=194.181.104.248
Aug 11 11:31:34 www5 sshd\[62817\]: Failed password for invalid user ftpuser from 194.181.104.248 port 50808 ssh2
...
2019-08-11 16:38:25
132.232.23.12 attack
FTP Brute-Force reported by Fail2Ban
2019-08-11 17:10:46
128.14.136.158 attack
Aug 11 09:58:32 fr01 sshd[19760]: Invalid user vagrant from 128.14.136.158
Aug 11 09:58:32 fr01 sshd[19760]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.14.136.158
Aug 11 09:58:32 fr01 sshd[19760]: Invalid user vagrant from 128.14.136.158
Aug 11 09:58:34 fr01 sshd[19760]: Failed password for invalid user vagrant from 128.14.136.158 port 39052 ssh2
Aug 11 09:58:40 fr01 sshd[19802]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.14.136.158  user=root
Aug 11 09:58:42 fr01 sshd[19802]: Failed password for root from 128.14.136.158 port 39580 ssh2
...
2019-08-11 16:43:19
106.12.208.202 attack
Aug 11 10:46:46 dedicated sshd[18721]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.208.202  user=root
Aug 11 10:46:47 dedicated sshd[18721]: Failed password for root from 106.12.208.202 port 36812 ssh2
2019-08-11 16:57:46
52.82.16.104 attackbots
19/8/11@03:57:21: FAIL: Alarm-SSH address from=52.82.16.104
...
2019-08-11 17:20:56
84.120.41.118 attackbots
2019-08-11T08:31:06.309070abusebot-7.cloudsearch.cf sshd\[22684\]: Invalid user test10 from 84.120.41.118 port 44545
2019-08-11 16:56:50
118.25.177.241 attack
Aug 11 02:55:02 dallas01 sshd[904]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.25.177.241
Aug 11 02:55:04 dallas01 sshd[904]: Failed password for invalid user fhem from 118.25.177.241 port 46702 ssh2
Aug 11 02:58:20 dallas01 sshd[1548]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.25.177.241
2019-08-11 16:47:13

Recently Reported IPs

79.133.6.141 185.30.166.34 134.175.167.203 134.175.137.179
159.192.157.216 198.100.146.94 47.101.130.134 39.96.170.250
132.232.158.137 37.29.15.90 114.225.66.57 81.218.175.37
77.42.125.229 131.155.21.199 131.0.120.103 13.78.49.127
171.232.1.79 168.90.208.147 13.233.184.202 13.125.8.27