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.142
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 894
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;45.134.144.142.			IN	A

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

;; Query time: 61 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Mar 01 13:56:51 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 142.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 142.144.134.45.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
34.91.145.90 attack
11211/udp
[2020-03-22]1pkt
2020-03-22 18:16:19
139.59.43.98 attackspambots
Mar 22 10:53:47 [host] sshd[1863]: Invalid user kr
Mar 22 10:53:47 [host] sshd[1863]: pam_unix(sshd:a
Mar 22 10:53:49 [host] sshd[1863]: Failed password
2020-03-22 18:28:40
194.182.75.170 attack
$f2bV_matches
2020-03-22 17:55:52
162.243.129.21 attack
" "
2020-03-22 18:18:04
51.91.9.225 attack
Mar 22 10:41:25  sshd[22861]: Failed password for invalid user ty from 51.91.9.225 port 59088 ssh2
2020-03-22 18:26:22
120.35.26.129 attackspam
(sshd) Failed SSH login from 120.35.26.129 (CN/China/-): 2 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Mar 22 10:52:29 ubnt-55d23 sshd[11996]: Invalid user manager from 120.35.26.129 port 11127
Mar 22 10:52:31 ubnt-55d23 sshd[11996]: Failed password for invalid user manager from 120.35.26.129 port 11127 ssh2
2020-03-22 18:13:42
163.172.223.107 attackspam
Scanning
2020-03-22 18:01:07
185.36.81.78 attackspam
Mar 22 10:25:39 srv01 postfix/smtpd\[32629\]: warning: unknown\[185.36.81.78\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar 22 10:30:49 srv01 postfix/smtpd\[3002\]: warning: unknown\[185.36.81.78\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar 22 10:32:23 srv01 postfix/smtpd\[5119\]: warning: unknown\[185.36.81.78\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar 22 10:32:56 srv01 postfix/smtpd\[5119\]: warning: unknown\[185.36.81.78\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar 22 10:35:43 srv01 postfix/smtpd\[3002\]: warning: unknown\[185.36.81.78\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-03-22 17:52:04
54.38.190.48 attack
(sshd) Failed SSH login from 54.38.190.48 (FR/France/48.ip-54-38-190.eu): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Mar 22 10:30:28 amsweb01 sshd[11289]: Invalid user ap from 54.38.190.48 port 55328
Mar 22 10:30:30 amsweb01 sshd[11289]: Failed password for invalid user ap from 54.38.190.48 port 55328 ssh2
Mar 22 10:38:11 amsweb01 sshd[12381]: Invalid user acme from 54.38.190.48 port 53202
Mar 22 10:38:13 amsweb01 sshd[12381]: Failed password for invalid user acme from 54.38.190.48 port 53202 ssh2
Mar 22 10:40:20 amsweb01 sshd[12664]: Invalid user fisnet from 54.38.190.48 port 33842
2020-03-22 18:07:09
111.231.75.83 attackbotsspam
Automatic report - Banned IP Access
2020-03-22 17:46:42
111.229.57.47 attackspam
Mar 22 10:30:10 minden010 sshd[15830]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.229.57.47
Mar 22 10:30:12 minden010 sshd[15830]: Failed password for invalid user shenyaou from 111.229.57.47 port 41246 ssh2
Mar 22 10:34:16 minden010 sshd[17432]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.229.57.47
...
2020-03-22 17:54:56
222.174.105.82 attack
RDPBruteGSL24
2020-03-22 18:06:26
178.46.214.247 attack
Unauthorised access (Mar 22) SRC=178.46.214.247 LEN=40 PREC=0x20 TTL=52 ID=55885 TCP DPT=23 WINDOW=48098 SYN
2020-03-22 18:27:47
52.224.163.35 attackbotsspam
Invalid user list from 52.224.163.35 port 37844
2020-03-22 18:15:30
180.95.186.12 attackbots
[portscan] Port scan
2020-03-22 18:03:34

Recently Reported IPs

91.133.138.216 205.221.230.21 90.97.197.234 124.37.33.70
212.45.146.17 172.29.120.4 144.28.243.163 157.140.184.20
38.76.197.82 182.196.198.50 221.43.254.128 13.155.113.214
1.0.237.44 1.13.16.26 1.163.154.14 1.12.236.69
1.116.69.14 1.116.222.32 1.163.52.182 1.164.189.160