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

;; QUESTION SECTION:
;104.139.236.249.		IN	A

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

;; Query time: 33 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 05 10:22:49 CST 2025
;; MSG SIZE  rcvd: 108
Host info
249.236.139.104.in-addr.arpa domain name pointer syn-104-139-236-249.res.spectrum.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
249.236.139.104.in-addr.arpa	name = syn-104-139-236-249.res.spectrum.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
118.98.43.121 attack
Jan 17 21:47:09 server sshd\[7837\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.98.43.121  user=root
Jan 17 21:47:11 server sshd\[7837\]: Failed password for root from 118.98.43.121 port 13064 ssh2
Jan 17 22:36:42 server sshd\[20501\]: Invalid user test from 118.98.43.121
Jan 17 22:36:42 server sshd\[20501\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.98.43.121 
Jan 17 22:36:43 server sshd\[20501\]: Failed password for invalid user test from 118.98.43.121 port 13064 ssh2
...
2020-01-18 04:35:54
181.57.153.190 attackbotsspam
Unauthorized connection attempt detected from IP address 181.57.153.190 to port 2220 [J]
2020-01-18 05:02:20
180.89.58.27 attackspam
Unauthorized connection attempt detected from IP address 180.89.58.27 to port 2220 [J]
2020-01-18 05:02:36
187.102.15.152 attack
Invalid user mo from 187.102.15.152 port 53119
2020-01-18 05:00:10
211.103.208.153 attackbotsspam
Invalid user admin from 211.103.208.153 port 34471
2020-01-18 04:51:25
176.31.255.63 attack
Invalid user monica from 176.31.255.63 port 45068
2020-01-18 05:04:24
117.232.127.50 attackspam
Invalid user sybase from 117.232.127.50 port 50760
2020-01-18 04:36:48
171.228.20.85 attackbots
Invalid user admin from 171.228.20.85 port 58806
2020-01-18 05:05:59
188.166.8.178 attackspam
Invalid user test from 188.166.8.178 port 34558
2020-01-18 04:59:09
148.70.226.228 attack
Unauthorized connection attempt detected from IP address 148.70.226.228 to port 2220 [J]
2020-01-18 05:07:56
197.47.12.154 attack
Invalid user admin from 197.47.12.154 port 50399
2020-01-18 04:56:25
220.175.137.216 attackspambots
Unauthorized connection attempt detected from IP address 220.175.137.216 to port 2220 [J]
2020-01-18 04:50:15
27.76.238.240 attackspambots
Email server abuse
2020-01-18 04:48:12
103.9.159.66 attack
Unauthorized connection attempt detected from IP address 103.9.159.66 to port 2220 [J]
2020-01-18 04:42:19
49.234.179.127 attackbotsspam
Unauthorized connection attempt detected from IP address 49.234.179.127 to port 2220 [J]
2020-01-18 04:45:12

Recently Reported IPs

31.9.85.244 254.91.43.160 164.80.220.183 226.36.197.47
234.177.52.223 246.72.39.101 38.175.250.9 205.189.181.185
94.176.185.106 24.51.226.60 172.128.119.219 164.166.17.36
76.17.91.96 253.182.236.165 64.41.57.135 41.66.34.197
164.135.142.210 195.66.215.89 91.114.131.48 37.216.76.217