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.95.55.58 attackspambots
Brute force SMTP login attempted.
...
2020-03-24 04:24:15
45.95.55.58 attack
Telnet/23 MH Probe, Scan, BF, Hack -
2020-03-21 04:45:12
45.95.55.58 attackspam
Mar 19 13:28:35 archiv sshd[2013]: Address 45.95.55.58 maps to 45.95.55.58.linkways.de, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Mar 19 13:28:35 archiv sshd[2013]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.95.55.58  user=r.r
Mar 19 13:28:37 archiv sshd[2013]: Failed password for r.r from 45.95.55.58 port 42482 ssh2
Mar 19 13:28:37 archiv sshd[2013]: Received disconnect from 45.95.55.58 port 42482:11: Bye Bye [preauth]
Mar 19 13:28:37 archiv sshd[2013]: Disconnected from 45.95.55.58 port 42482 [preauth]
Mar 19 13:28:37 archiv sshd[2018]: Address 45.95.55.58 maps to 45.95.55.58.linkways.de, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Mar 19 13:28:37 archiv sshd[2018]: Invalid user admin from 45.95.55.58 port 45066
Mar 19 13:28:37 archiv sshd[2018]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.95.55.58
Mar 19 13:28:39 archi........
-------------------------------
2020-03-20 00:59:45
45.95.55.69 attackbotsspam
Unauthorised access (Mar  8) SRC=45.95.55.69 LEN=40 PREC=0x20 TTL=56 ID=50708 TCP DPT=23 WINDOW=11789 SYN
2020-03-08 09:14:25
45.95.55.45 attack
2020-02-26T02:49:30.855276vps751288.ovh.net sshd\[30510\]: Invalid user yuanshishi from 45.95.55.45 port 53672
2020-02-26T02:49:30.868517vps751288.ovh.net sshd\[30510\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.95.55.45
2020-02-26T02:49:33.176183vps751288.ovh.net sshd\[30510\]: Failed password for invalid user yuanshishi from 45.95.55.45 port 53672 ssh2
2020-02-26T02:50:13.933187vps751288.ovh.net sshd\[30512\]: Invalid user budget from 45.95.55.45 port 32808
2020-02-26T02:50:13.940916vps751288.ovh.net sshd\[30512\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.95.55.45
2020-02-26 10:48:25
45.95.55.97 attackspam
Feb 12 23:17:50 legacy sshd[31371]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.95.55.97
Feb 12 23:17:52 legacy sshd[31371]: Failed password for invalid user abramowitz from 45.95.55.97 port 51165 ssh2
Feb 12 23:21:00 legacy sshd[31591]: Failed password for root from 45.95.55.97 port 37929 ssh2
...
2020-02-13 06:28:31
45.95.55.97 attackbotsspam
Jan 23 21:41:29 server sshd\[10553\]: Invalid user chandru from 45.95.55.97
Jan 23 21:41:29 server sshd\[10553\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.95.55.97 
Jan 23 21:41:30 server sshd\[10553\]: Failed password for invalid user chandru from 45.95.55.97 port 40080 ssh2
Jan 24 01:23:03 server sshd\[30610\]: Invalid user btest from 45.95.55.97
Jan 24 01:23:03 server sshd\[30610\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.95.55.97 
...
2020-01-24 06:29:14
45.95.55.169 attackspambots
Dec 11 13:44:17 MK-Soft-VM5 sshd[23900]: Failed password for root from 45.95.55.169 port 34454 ssh2
Dec 11 13:49:25 MK-Soft-VM5 sshd[23976]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.95.55.169 
...
2019-12-11 21:07:22
45.95.55.121 attackspam
Port 22 Scan, PTR: None
2019-12-03 16:57:13
45.95.55.12 attackspambots
Dec  1 08:41:44 mout sshd[18270]: Invalid user user2 from 45.95.55.12 port 48376
2019-12-01 16:03:05
45.95.55.12 attackbots
Nov 30 06:53:58 venus sshd\[1373\]: Invalid user chaales from 45.95.55.12 port 45416
Nov 30 06:53:58 venus sshd\[1373\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.95.55.12
Nov 30 06:54:00 venus sshd\[1373\]: Failed password for invalid user chaales from 45.95.55.12 port 45416 ssh2
...
2019-11-30 15:52:48
45.95.55.12 attackbots
2019-11-29 09:14:36,184 fail2ban.actions: WARNING [ssh] Ban 45.95.55.12
2019-11-29 18:56:11
45.95.55.12 attack
Nov 24 17:59:46 microserver sshd[50855]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.95.55.12  user=www-data
Nov 24 17:59:48 microserver sshd[50855]: Failed password for www-data from 45.95.55.12 port 40270 ssh2
Nov 24 18:05:54 microserver sshd[52007]: Invalid user burcew from 45.95.55.12 port 48374
Nov 24 18:05:54 microserver sshd[52007]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.95.55.12
Nov 24 18:05:57 microserver sshd[52007]: Failed password for invalid user burcew from 45.95.55.12 port 48374 ssh2
2019-11-24 22:21:41
45.95.55.12 attack
Nov  4 08:56:46 reporting1 sshd[31793]: Address 45.95.55.12 maps to 45.95.55.12.linkways.de, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Nov  4 08:56:46 reporting1 sshd[31793]: Invalid user knoxville from 45.95.55.12
Nov  4 08:56:46 reporting1 sshd[31793]: Failed password for invalid user knoxville from 45.95.55.12 port 58457 ssh2
Nov  4 09:13:23 reporting1 sshd[9301]: Address 45.95.55.12 maps to 45.95.55.12.linkways.de, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Nov  4 09:13:23 reporting1 sshd[9301]: User r.r from 45.95.55.12 not allowed because not listed in AllowUsers
Nov  4 09:13:23 reporting1 sshd[9301]: Failed password for invalid user r.r from 45.95.55.12 port 54813 ssh2
Nov  4 09:16:55 reporting1 sshd[11109]: Address 45.95.55.12 maps to 45.95.55.12.linkways.de, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Nov  4 09:16:55 reporting1 sshd[11109]: Invalid user terminfo from 45.95.55.12........
-------------------------------
2019-11-09 15:32:31
45.95.55.12 attackspam
Nov  4 08:56:46 reporting1 sshd[31793]: Address 45.95.55.12 maps to 45.95.55.12.linkways.de, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Nov  4 08:56:46 reporting1 sshd[31793]: Invalid user knoxville from 45.95.55.12
Nov  4 08:56:46 reporting1 sshd[31793]: Failed password for invalid user knoxville from 45.95.55.12 port 58457 ssh2
Nov  4 09:13:23 reporting1 sshd[9301]: Address 45.95.55.12 maps to 45.95.55.12.linkways.de, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Nov  4 09:13:23 reporting1 sshd[9301]: User r.r from 45.95.55.12 not allowed because not listed in AllowUsers
Nov  4 09:13:23 reporting1 sshd[9301]: Failed password for invalid user r.r from 45.95.55.12 port 54813 ssh2
Nov  4 09:16:55 reporting1 sshd[11109]: Address 45.95.55.12 maps to 45.95.55.12.linkways.de, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Nov  4 09:16:55 reporting1 sshd[11109]: Invalid user terminfo from 45.95.55.12........
-------------------------------
2019-11-08 08:31:18
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 45.95.55.4
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 20805
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;45.95.55.4.			IN	A

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

;; Query time: 69 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jun 12 07:07:35 CST 2022
;; MSG SIZE  rcvd: 103
Host info
4.55.95.45.in-addr.arpa domain name pointer 45.95.55.4.fly-hosting.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
4.55.95.45.in-addr.arpa	name = 45.95.55.4.fly-hosting.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
45.115.61.194 attackspam
Brute force attempt
2020-02-09 22:46:36
114.25.189.2 attack
[Sun Feb 09 10:36:59.548044 2020] [:error] [pid 31173] [client 114.25.189.2:49739] [client 114.25.189.2] ModSecurity: Access denied with code 403 (phase 2). Operator GE matched 5 at TX:anomaly_score. [file "/usr/share/modsecurity-crs/rules/REQUEST-949-BLOCKING-EVALUATION.conf"] [line "91"] [id "949110"] [msg "Inbound Anomaly Score Exceeded (Total Score: 13)"] [severity "CRITICAL"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-generic"] [hostname "127.0.0.1"] [uri "/shell"] [unique_id "XkAK@SR5xEffHgYKk3384QAAAAQ"]
...
2020-02-09 22:29:06
5.88.155.130 attackspambots
Feb  9 13:28:01 Ubuntu-1404-trusty-64-minimal sshd\[29252\]: Invalid user j2m from 5.88.155.130
Feb  9 13:28:01 Ubuntu-1404-trusty-64-minimal sshd\[29252\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.88.155.130
Feb  9 13:28:03 Ubuntu-1404-trusty-64-minimal sshd\[29252\]: Failed password for invalid user j2m from 5.88.155.130 port 9224 ssh2
Feb  9 14:36:55 Ubuntu-1404-trusty-64-minimal sshd\[10047\]: Invalid user minfo from 5.88.155.130
Feb  9 14:36:55 Ubuntu-1404-trusty-64-minimal sshd\[10047\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.88.155.130
2020-02-09 22:37:40
185.209.0.51 attackspambots
Feb  9 15:32:35 debian-2gb-nbg1-2 kernel: \[3517992.694583\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=185.209.0.51 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=56 PROTO=TCP SPT=44303 DPT=3702 WINDOW=1024 RES=0x00 SYN URGP=0
2020-02-09 22:33:58
190.199.208.98 attackspam
20/2/9@08:37:09: FAIL: Alarm-Network address from=190.199.208.98
20/2/9@08:37:09: FAIL: Alarm-Network address from=190.199.208.98
...
2020-02-09 22:20:12
120.29.77.182 attackspambots
Wordpress login scanning
2020-02-09 22:20:42
125.224.12.196 attackbots
23/tcp 23/tcp
[2020-02-07/08]2pkt
2020-02-09 22:42:45
178.46.210.136 attackspam
23/tcp 23/tcp 23/tcp...
[2020-02-07/08]16pkt,1pt.(tcp)
2020-02-09 22:37:09
76.73.193.60 attackbotsspam
Brute forcing email accounts
2020-02-09 22:30:06
185.56.153.236 attackbots
Feb  9 04:38:17 hpm sshd\[21799\]: Invalid user nmq from 185.56.153.236
Feb  9 04:38:17 hpm sshd\[21799\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.56.153.236
Feb  9 04:38:19 hpm sshd\[21799\]: Failed password for invalid user nmq from 185.56.153.236 port 39178 ssh2
Feb  9 04:47:56 hpm sshd\[23189\]: Invalid user rsh from 185.56.153.236
Feb  9 04:47:56 hpm sshd\[23189\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.56.153.236
2020-02-09 22:56:25
90.66.53.155 attackbots
$f2bV_matches
2020-02-09 22:29:31
49.113.247.180 attack
1581255402 - 02/09/2020 14:36:42 Host: 49.113.247.180/49.113.247.180 Port: 23 TCP Blocked
2020-02-09 22:49:10
159.203.161.141 attackspam
Lines containing failures of 159.203.161.141
Feb  6 14:52:53 kvm05 sshd[9694]: Did not receive identification string from 159.203.161.141 port 59626
Feb  6 14:53:29 kvm05 sshd[9765]: Received disconnect from 159.203.161.141 port 33908:11: Normal Shutdown, Thank you for playing [preauth]
Feb  6 14:53:29 kvm05 sshd[9765]: Disconnected from authenticating user r.r 159.203.161.141 port 33908 [preauth]
Feb  6 14:54:08 kvm05 sshd[9839]: Received disconnect from 159.203.161.141 port 47584:11: Normal Shutdown, Thank you for playing [preauth]
Feb  6 14:54:08 kvm05 sshd[9839]: Disconnected from authenticating user r.r 159.203.161.141 port 47584 [preauth]
Feb  6 14:54:46 kvm05 sshd[9964]: Received disconnect from 159.203.161.141 port 33024:11: Normal Shutdown, Thank you for playing [preauth]
Feb  6 14:54:46 kvm05 sshd[9964]: Disconnected from authenticating user r.r 159.203.161.141 port 33024 [preauth]
Feb  6 14:55:22 kvm05 sshd[10161]: Invalid user admin from 159.203.161.141 port ........
------------------------------
2020-02-09 22:55:15
217.138.194.120 attack
0,66-02/04 [bc01/m09] PostRequest-Spammer scoring: Lusaka01
2020-02-09 23:05:01
112.86.87.234 attack
SSH bruteforce (Triggered fail2ban)
2020-02-09 22:39:19

Recently Reported IPs

137.226.0.142 137.226.1.107 5.167.65.72 23.128.248.91
137.226.1.165 137.226.1.163 5.167.65.141 128.199.16.6
137.226.20.113 217.25.237.241 104.248.0.76 137.226.1.94
43.154.37.60 137.226.0.185 137.226.1.11 168.138.26.137
3.26.51.68 5.167.65.88 180.76.174.26 5.167.65.25