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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 134.94.57.14
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 28217
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;134.94.57.14.			IN	A

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

;; Query time: 19 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jan 09 08:28:39 CST 2022
;; MSG SIZE  rcvd: 105
Host info
14.57.94.134.in-addr.arpa domain name pointer pool-14-57.vpn.kfa-juelich.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
14.57.94.134.in-addr.arpa	name = pool-14-57.vpn.kfa-juelich.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
95.217.124.145 attackspam
(From raymundo.moose@msn.com) Listen,

There’s one thing better than f'r.ee traffic, and that’s passive, organic traffic that keeps coming in steadily with ZERO effort from you – ever!

My friends Yogesh Agarwal and venkata has launched a platform that has been able to bring in literally tons of visitors to their users 

HOW IS THIS Even Possible?

It’s simple…

They’ve created a software that leverages the mighty Google for hundreds of Free BUYERS…

>> https://bit.ly/vSuites

Now this software completely automates all the manual work for you…

And the best part?

It 100% complies with Google, which mean evergreen passive traffic and sales for you…

No Tech Skills Or Experience Needed...

No Hidden Or Monthly Fees...

No Video Creation Required

Check out a demo here:
>> https://bit.ly/vSuites

Wishing you all the best
2020-04-23 07:47:42
213.111.245.224 attack
Apr 22 22:45:16 localhost sshd[107480]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=224.245-pool.nikopol.net  user=root
Apr 22 22:45:18 localhost sshd[107480]: Failed password for root from 213.111.245.224 port 34022 ssh2
Apr 22 22:51:09 localhost sshd[108166]: Invalid user on from 213.111.245.224 port 41373
Apr 22 22:51:09 localhost sshd[108166]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=224.245-pool.nikopol.net
Apr 22 22:51:09 localhost sshd[108166]: Invalid user on from 213.111.245.224 port 41373
Apr 22 22:51:11 localhost sshd[108166]: Failed password for invalid user on from 213.111.245.224 port 41373 ssh2
...
2020-04-23 07:45:16
180.76.104.167 attackspambots
Apr 22 23:43:34 ns382633 sshd\[10334\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.104.167  user=root
Apr 22 23:43:36 ns382633 sshd\[10334\]: Failed password for root from 180.76.104.167 port 36404 ssh2
Apr 22 23:48:59 ns382633 sshd\[11320\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.104.167  user=root
Apr 22 23:49:01 ns382633 sshd\[11320\]: Failed password for root from 180.76.104.167 port 47698 ssh2
Apr 22 23:50:50 ns382633 sshd\[11893\]: Invalid user r from 180.76.104.167 port 47582
Apr 22 23:50:50 ns382633 sshd\[11893\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.104.167
2020-04-23 08:07:53
193.112.219.207 attackspam
Apr 23 03:12:06 itv-usvr-01 sshd[13104]: Invalid user fk from 193.112.219.207
Apr 23 03:12:06 itv-usvr-01 sshd[13104]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.112.219.207
Apr 23 03:12:06 itv-usvr-01 sshd[13104]: Invalid user fk from 193.112.219.207
Apr 23 03:12:07 itv-usvr-01 sshd[13104]: Failed password for invalid user fk from 193.112.219.207 port 54530 ssh2
2020-04-23 08:06:06
18.162.124.44 attack
Apr 22 20:07:46 game-panel sshd[14960]: Failed password for root from 18.162.124.44 port 41908 ssh2
Apr 22 20:12:29 game-panel sshd[15239]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=18.162.124.44
Apr 22 20:12:31 game-panel sshd[15239]: Failed password for invalid user postgres from 18.162.124.44 port 50074 ssh2
2020-04-23 07:50:42
51.137.94.78 attackspambots
Invalid user zy from 51.137.94.78 port 51198
2020-04-23 07:53:20
51.91.77.104 attackbots
SASL PLAIN auth failed: ruser=...
2020-04-23 07:48:21
106.75.10.4 attackspambots
2020-04-22T23:18:56.887705shield sshd\[12970\]: Invalid user sz from 106.75.10.4 port 55042
2020-04-22T23:18:56.891739shield sshd\[12970\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.10.4
2020-04-22T23:18:59.254300shield sshd\[12970\]: Failed password for invalid user sz from 106.75.10.4 port 55042 ssh2
2020-04-22T23:28:02.690071shield sshd\[14515\]: Invalid user test1 from 106.75.10.4 port 59698
2020-04-22T23:28:02.695360shield sshd\[14515\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.10.4
2020-04-23 07:39:42
49.88.112.68 attackbotsspam
Apr 23 01:23:25 v22018053744266470 sshd[3245]: Failed password for root from 49.88.112.68 port 33385 ssh2
Apr 23 01:29:44 v22018053744266470 sshd[3668]: Failed password for root from 49.88.112.68 port 20244 ssh2
...
2020-04-23 07:43:26
180.119.54.33 attack
Unauthorised access (Apr 22) SRC=180.119.54.33 LEN=40 TTL=52 ID=45566 TCP DPT=8080 WINDOW=45051 SYN 
Unauthorised access (Apr 22) SRC=180.119.54.33 LEN=40 TTL=52 ID=1319 TCP DPT=8080 WINDOW=45051 SYN 
Unauthorised access (Apr 22) SRC=180.119.54.33 LEN=40 TTL=52 ID=54780 TCP DPT=8080 WINDOW=43854 SYN
2020-04-23 08:02:26
119.146.150.134 attackspam
Invalid user sr from 119.146.150.134 port 32772
2020-04-23 07:43:09
106.12.22.209 attack
Scanned 4 times in the last 24 hours on port 22
2020-04-23 08:18:17
51.77.148.77 attack
detected by Fail2Ban
2020-04-23 08:16:39
157.230.245.91 attackbotsspam
Apr 22 23:59:13 lock-38 sshd[1383102]: Failed password for invalid user vv from 157.230.245.91 port 47630 ssh2
Apr 22 23:59:13 lock-38 sshd[1383102]: Disconnected from invalid user vv 157.230.245.91 port 47630 [preauth]
Apr 23 00:00:37 lock-38 sshd[1383321]: Invalid user tester from 157.230.245.91 port 40306
Apr 23 00:00:37 lock-38 sshd[1383321]: Invalid user tester from 157.230.245.91 port 40306
Apr 23 00:00:37 lock-38 sshd[1383321]: Failed password for invalid user tester from 157.230.245.91 port 40306 ssh2
...
2020-04-23 08:11:26
51.38.179.179 attackbots
Apr 22 22:01:46 game-panel sshd[19900]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.38.179.179
Apr 22 22:01:48 game-panel sshd[19900]: Failed password for invalid user postgres from 51.38.179.179 port 35616 ssh2
Apr 22 22:08:37 game-panel sshd[20077]: Failed password for root from 51.38.179.179 port 42590 ssh2
2020-04-23 07:48:37

Recently Reported IPs

148.255.87.121 78.130.218.238 129.117.195.185 69.1.11.10
2602:ffc5:60::1:ac18 2.134.34.240 45.241.229.215 202.84.67.216
10.141.86.112 192.146.9.148 165.248.143.96 179.66.99.250
208.99.173.195 94.26.38.161 0.84.114.76 79.191.111.176
237.77.236.151 10.8.169.81 199.19.149.190 153.212.133.52