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

;; QUESTION SECTION:
;104.86.122.34.			IN	A

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

;; Query time: 23 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Nov 23 10:33:10 CST 2023
;; MSG SIZE  rcvd: 106
Host info
34.122.86.104.in-addr.arpa domain name pointer a104-86-122-34.deploy.static.akamaitechnologies.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
34.122.86.104.in-addr.arpa	name = a104-86-122-34.deploy.static.akamaitechnologies.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
107.189.11.193 attackbots
Invalid user fake from 107.189.11.193 port 42396
2020-01-18 04:39:31
170.84.224.240 attack
Unauthorized connection attempt detected from IP address 170.84.224.240 to port 2220 [J]
2020-01-18 05:06:14
209.141.55.231 attackbots
Lines containing failures of 209.141.55.231 (max 1000)
Jan 15 10:52:30 server sshd[26803]: Connection from 209.141.55.231 port 54236 on 62.116.165.82 port 22
Jan 15 10:52:31 server sshd[26803]: Invalid user liang from 209.141.55.231 port 54236
Jan 15 10:52:31 server sshd[26803]: Received disconnect from 209.141.55.231 port 54236:11: Bye Bye [preauth]
Jan 15 10:52:31 server sshd[26803]: Disconnected from 209.141.55.231 port 54236 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=209.141.55.231
2020-01-18 04:52:04
202.137.155.220 attackspambots
Invalid user admin from 202.137.155.220 port 35103
2020-01-18 04:54:19
187.45.103.15 attackbotsspam
Input Traffic from this IP, but critial abuseconfidencescore
2020-01-18 05:00:39
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
103.86.51.93 attackbotsspam
Unauthorized connection attempt detected from IP address 103.86.51.93 to port 2220 [J]
2020-01-18 04:41:22
187.185.70.10 attackspambots
Unauthorized connection attempt detected from IP address 187.185.70.10 to port 2220 [J]
2020-01-18 04:59:36
107.135.147.127 attack
Jan 17 20:45:16 MK-Soft-VM8 sshd[28637]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.135.147.127 
Jan 17 20:45:18 MK-Soft-VM8 sshd[28637]: Failed password for invalid user wine from 107.135.147.127 port 51962 ssh2
...
2020-01-18 04:39:49
145.239.89.243 attackspambots
Unauthorized connection attempt detected from IP address 145.239.89.243 to port 2220 [J]
2020-01-18 04:29:41
37.192.170.184 attackspambots
Invalid user admin from 37.192.170.184 port 44848
2020-01-18 04:46:40
123.20.229.142 attackbotsspam
Invalid user admin from 123.20.229.142 port 45507
2020-01-18 04:34:17
34.242.99.103 attack
Invalid user gv from 34.242.99.103 port 41756
2020-01-18 04:47:16
211.103.208.153 attackbotsspam
Invalid user admin from 211.103.208.153 port 34471
2020-01-18 04:51:25
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

Recently Reported IPs

104.86.102.95 104.85.8.253 104.85.98.201 104.86.105.44
104.85.226.18 104.86.123.142 104.85.6.179 104.85.48.103
104.86.158.227 104.86.131.197 104.86.135.80 104.86.116.246
104.86.162.137 104.86.109.235 104.85.87.100 104.85.168.145
104.85.95.150 104.86.189.86 104.86.19.240 104.86.187.249