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: Frankfurt am Main

Region: Hesse

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

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

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

;; Query time: 54 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Apr 19 05:47:35 CST 2020
;; MSG SIZE  rcvd: 117
Host info
121.41.194.18.in-addr.arpa domain name pointer ec2-18-194-41-121.eu-central-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
121.41.194.18.in-addr.arpa	name = ec2-18-194-41-121.eu-central-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
104.236.131.54 attackspambots
Jul 24 10:59:16 server01 sshd\[5119\]: Invalid user hadoop from 104.236.131.54
Jul 24 10:59:16 server01 sshd\[5119\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.236.131.54
Jul 24 10:59:17 server01 sshd\[5119\]: Failed password for invalid user hadoop from 104.236.131.54 port 38026 ssh2
...
2019-07-24 16:03:29
139.199.158.14 attackspambots
Invalid user mike from 139.199.158.14 port 54625
2019-07-24 16:23:25
130.211.246.128 attackbotsspam
Invalid user zabbix from 130.211.246.128 port 40030
2019-07-24 16:28:39
62.117.12.39 attackbots
Invalid user pi from 62.117.12.39 port 53678
2019-07-24 16:39:47
142.93.74.45 attackbotsspam
Invalid user one from 142.93.74.45 port 33672
2019-07-24 15:56:43
115.254.63.52 attackbots
Invalid user applmgr from 115.254.63.52 port 36451
2019-07-24 16:31:20
139.59.39.174 attackbotsspam
Invalid user jira from 139.59.39.174 port 36578
2019-07-24 15:57:30
94.158.83.31 attackspam
Invalid user pi from 94.158.83.31 port 46646
2019-07-24 16:35:00
201.230.55.55 attack
Jul 24 08:11:04 MK-Soft-VM4 sshd\[9679\]: Invalid user zabbix from 201.230.55.55 port 49882
Jul 24 08:11:04 MK-Soft-VM4 sshd\[9679\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.230.55.55
Jul 24 08:11:06 MK-Soft-VM4 sshd\[9679\]: Failed password for invalid user zabbix from 201.230.55.55 port 49882 ssh2
...
2019-07-24 16:16:02
162.247.74.200 attackspambots
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.247.74.200  user=root
Failed password for root from 162.247.74.200 port 51548 ssh2
Failed password for root from 162.247.74.200 port 51548 ssh2
Failed password for root from 162.247.74.200 port 51548 ssh2
Failed password for root from 162.247.74.200 port 51548 ssh2
2019-07-24 15:54:42
45.55.157.147 attackspambots
Invalid user postgres from 45.55.157.147 port 32846
2019-07-24 16:10:04
185.220.101.67 attack
Invalid user admin from 185.220.101.67 port 39851
2019-07-24 15:49:03
121.151.153.108 attackbots
Invalid user cron from 121.151.153.108 port 50506
2019-07-24 15:59:51
106.12.125.27 attack
Invalid user redis from 106.12.125.27 port 56820
2019-07-24 16:31:46
190.119.190.122 attackspambots
SSH bruteforce (Triggered fail2ban)
2019-07-24 15:46:03

Recently Reported IPs

65.38.200.234 63.95.47.231 190.163.121.78 117.98.161.11
167.56.179.78 179.128.228.207 93.3.254.205 167.100.120.118
221.44.192.29 128.130.46.117 3.228.40.176 213.132.46.76
114.95.226.244 58.95.124.148 47.133.8.113 35.133.111.81
75.67.165.181 102.173.209.172 115.36.245.125 65.111.49.195