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: United States of America (the)

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

;; QUESTION SECTION:
;55.104.117.111.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 23 03:23:54 CST 2025
;; MSG SIZE  rcvd: 107
Host info
b'Host 111.117.104.55.in-addr.arpa not found: 2(SERVFAIL)
'
Nslookup info:
server can't find 55.104.117.111.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
37.6.43.135 attackbotsspam
1582390138 - 02/22/2020 17:48:58 Host: 37.6.43.135/37.6.43.135 Port: 23 TCP Blocked
2020-02-23 02:52:53
113.31.115.119 attack
Tried sshing with brute force.
2020-02-23 02:29:00
118.80.74.253 attackspambots
firewall-block, port(s): 23/tcp
2020-02-23 02:51:02
220.134.142.37 attackbots
Sat Feb 22 09:49:55 2020 - Child process 169478 handling connection
Sat Feb 22 09:49:55 2020 - New connection from: 220.134.142.37:46962
Sat Feb 22 09:49:55 2020 - Sending data to client: [Login: ]
Sat Feb 22 09:49:55 2020 - Got data: admin
Sat Feb 22 09:49:56 2020 - Sending data to client: [Password: ]
Sat Feb 22 09:49:56 2020 - Child aborting
Sat Feb 22 09:49:56 2020 - Reporting IP address: 220.134.142.37 - mflag: 0
2020-02-23 02:40:50
103.74.118.216 attackbots
Automatic report - XMLRPC Attack
2020-02-23 02:31:01
138.197.89.194 attack
Invalid user student from 138.197.89.194 port 41852
2020-02-23 03:08:51
180.166.141.58 attackspambots
firewall-block, port(s): 1953/tcp, 2255/tcp, 4266/tcp
2020-02-23 02:46:31
201.253.168.65 attackbotsspam
Unauthorized connection attempt detected from IP address 201.253.168.65 to port 445
2020-02-23 03:05:57
222.186.30.76 attackspambots
Feb 22 13:33:10 plusreed sshd[22251]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.76  user=root
Feb 22 13:33:12 plusreed sshd[22251]: Failed password for root from 222.186.30.76 port 21202 ssh2
...
2020-02-23 02:36:30
177.69.85.145 attackspam
Feb 22 15:52:22 vps46666688 sshd[17805]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.69.85.145
Feb 22 15:52:24 vps46666688 sshd[17805]: Failed password for invalid user dr from 177.69.85.145 port 39620 ssh2
...
2020-02-23 02:55:00
139.99.125.191 attackspam
139.99.125.191 was recorded 13 times by 9 hosts attempting to connect to the following ports: 55391,50570,26014,4892,51856,54434,56610,39019. Incident counter (4h, 24h, all-time): 13, 66, 69
2020-02-23 02:58:21
49.235.107.14 attackbotsspam
suspicious action Sat, 22 Feb 2020 13:48:39 -0300
2020-02-23 03:09:27
119.206.67.103 attackspam
20/2/22@11:49:23: FAIL: Alarm-Telnet address from=119.206.67.103
...
2020-02-23 02:33:47
159.89.160.91 attackbots
02/22/2020-13:18:34.284943 159.89.160.91 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-02-23 03:02:24
180.252.168.153 attackbotsspam
Automatic report - SSH Brute-Force Attack
2020-02-23 02:33:25

Recently Reported IPs

20.135.78.142 217.241.34.123 174.137.245.135 34.61.16.29
37.50.252.53 100.206.167.117 202.144.23.206 157.176.236.246
71.237.174.182 236.52.186.2 33.28.255.24 218.119.67.35
170.68.137.21 17.185.58.115 166.98.7.245 212.133.71.136
212.109.41.248 45.115.129.157 137.194.103.232 127.148.235.239