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: None

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
1.119.55.61 attackspambots
Automatic report BANNED IP
2020-08-10 00:33:12
1.119.55.60 attack
2020-05-06T12:01:38.486281ionos.janbro.de sshd[531]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.119.55.60  user=root
2020-05-06T12:01:40.971895ionos.janbro.de sshd[531]: Failed password for root from 1.119.55.60 port 35331 ssh2
2020-05-06T12:01:43.217680ionos.janbro.de sshd[533]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.119.55.60  user=root
2020-05-06T12:01:44.724765ionos.janbro.de sshd[533]: Failed password for root from 1.119.55.60 port 35441 ssh2
2020-05-06T12:01:47.577928ionos.janbro.de sshd[535]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.119.55.60  user=root
2020-05-06T12:01:48.964663ionos.janbro.de sshd[535]: Failed password for root from 1.119.55.60 port 35551 ssh2
2020-05-06T12:01:50.897604ionos.janbro.de sshd[537]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.119.55.60  user=root
2020-05-06T
...
2020-05-06 20:58:42
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 1.119.55.104
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1934
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;1.119.55.104.			IN	A

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

;; Query time: 24 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Sep 26 05:47:01 CST 2022
;; MSG SIZE  rcvd: 105
Host info
b';; connection timed out; no servers could be reached
'
Nslookup info:
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server:		183.60.82.98
Address:	183.60.82.98#53

** server can't find 104.55.119.1.in-addr.arpa: SERVFAIL

Related IP info:
Related comments:
IP Type Details Datetime
142.93.39.29 attackbotsspam
Triggered by Fail2Ban at Vostok web server
2019-06-22 12:49:50
31.47.240.195 attackspam
Automatic report - Web App Attack
2019-06-22 12:57:07
188.2.59.218 attack
Request: "GET / HTTP/1.1"
2019-06-22 12:29:13
58.242.83.31 attackbotsspam
2019-06-22T06:43:44.997192scmdmz1 sshd\[7344\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.242.83.31  user=root
2019-06-22T06:43:47.205347scmdmz1 sshd\[7344\]: Failed password for root from 58.242.83.31 port 42880 ssh2
2019-06-22T06:43:49.388149scmdmz1 sshd\[7344\]: Failed password for root from 58.242.83.31 port 42880 ssh2
...
2019-06-22 12:50:23
106.13.107.106 attack
Jun 22 06:36:59 s1 sshd\[9575\]: User root from 106.13.107.106 not allowed because not listed in AllowUsers
Jun 22 06:36:59 s1 sshd\[9575\]: Failed password for invalid user root from 106.13.107.106 port 58200 ssh2
Jun 22 06:39:26 s1 sshd\[10007\]: Invalid user uploader from 106.13.107.106 port 47884
Jun 22 06:39:26 s1 sshd\[10007\]: Failed password for invalid user uploader from 106.13.107.106 port 47884 ssh2
Jun 22 06:40:49 s1 sshd\[10951\]: Invalid user vnc from 106.13.107.106 port 59974
Jun 22 06:40:49 s1 sshd\[10951\]: Failed password for invalid user vnc from 106.13.107.106 port 59974 ssh2
...
2019-06-22 12:55:05
203.114.102.69 attack
Jun 22 03:52:41 ns41 sshd[8565]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.114.102.69
Jun 22 03:52:41 ns41 sshd[8565]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.114.102.69
2019-06-22 12:24:11
176.119.134.84 attackbotsspam
Request: "GET / HTTP/1.1"
2019-06-22 12:33:09
199.195.250.77 attack
Automatic report - Web App Attack
2019-06-22 12:21:24
179.52.119.159 attackspambots
Automatic report - SSH Brute-Force Attack
2019-06-22 12:10:51
54.223.168.233 attack
2019-06-22T04:40:48.436169abusebot-4.cloudsearch.cf sshd\[1488\]: Invalid user ansible from 54.223.168.233 port 42558
2019-06-22 12:55:30
61.34.172.200 attackspam
23/tcp
[2019-06-22]1pkt
2019-06-22 12:53:24
114.97.243.253 attack
Jun 21 21:34:25 andromeda postfix/smtpd\[26465\]: warning: unknown\[114.97.243.253\]: SASL LOGIN authentication failed: authentication failure
Jun 21 21:34:26 andromeda postfix/smtpd\[40316\]: warning: unknown\[114.97.243.253\]: SASL LOGIN authentication failed: authentication failure
Jun 21 21:34:27 andromeda postfix/smtpd\[26465\]: warning: unknown\[114.97.243.253\]: SASL LOGIN authentication failed: authentication failure
Jun 21 21:34:28 andromeda postfix/smtpd\[40316\]: warning: unknown\[114.97.243.253\]: SASL LOGIN authentication failed: authentication failure
Jun 21 21:34:30 andromeda postfix/smtpd\[26465\]: warning: unknown\[114.97.243.253\]: SASL LOGIN authentication failed: authentication failure
2019-06-22 12:18:38
82.80.143.226 attackspam
Request: "GET / HTTP/1.1"
2019-06-22 12:21:56
46.105.99.163 attackspambots
as always with OVH 
All domain names registered at ovh are attacked
2019-06-22 12:42:19
54.36.110.42 attackspam
Bad Request: "\x05\x01\x00" Bad Request: "\x04\x01\x00\x19\xA6\xD8\x95\x81\x00"
2019-06-22 12:29:33

Recently Reported IPs

0.106.181.158 0.248.34.138 0.106.91.16 0.107.22.71
0.106.68.177 0.104.49.74 0.107.104.139 0.108.47.134
0.106.22.145 0.107.133.159 0.107.57.142 0.107.15.83
0.105.35.9 0.105.151.187 0.109.139.230 0.104.71.143
0.108.46.194 0.108.181.184 0.105.185.17 0.105.143.234