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

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

;; QUESTION SECTION:
;108.139.229.44.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Mar 06 10:25:36 CST 2022
;; MSG SIZE  rcvd: 107
Host info
44.229.139.108.in-addr.arpa domain name pointer server-108-139-229-44.fco50.r.cloudfront.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
44.229.139.108.in-addr.arpa	name = server-108-139-229-44.fco50.r.cloudfront.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
45.115.232.23 attackspam
firewall-block, port(s): 3389/tcp
2019-09-04 23:56:09
163.172.106.112 attackspambots
Caught in portsentry honeypot
2019-09-05 00:01:22
106.75.65.4 attack
$f2bV_matches
2019-09-04 23:44:46
71.6.232.4 attackspam
firewall-block, port(s): 80/tcp
2019-09-04 23:52:02
5.188.86.22 attack
firewall-block, port(s): 3380/tcp, 9805/tcp, 9812/tcp, 9814/tcp
2019-09-05 00:03:04
94.176.15.146 attackspam
Unauthorised access (Sep  4) SRC=94.176.15.146 LEN=40 PREC=0x20 TTL=235 ID=61598 DF TCP DPT=23 WINDOW=14600 SYN
2019-09-05 00:42:05
201.212.227.95 attackspambots
F2B jail: sshd. Time: 2019-09-04 15:28:03, Reported by: VKReport
2019-09-05 00:35:28
51.68.189.69 attack
Sep  4 11:33:20 TORMINT sshd\[23995\]: Invalid user nick from 51.68.189.69
Sep  4 11:33:20 TORMINT sshd\[23995\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.68.189.69
Sep  4 11:33:22 TORMINT sshd\[23995\]: Failed password for invalid user nick from 51.68.189.69 port 37063 ssh2
...
2019-09-04 23:42:05
42.157.128.188 attackbotsspam
Sep  4 04:47:55 wbs sshd\[15662\]: Invalid user dayz from 42.157.128.188
Sep  4 04:47:55 wbs sshd\[15662\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.157.128.188
Sep  4 04:47:58 wbs sshd\[15662\]: Failed password for invalid user dayz from 42.157.128.188 port 39630 ssh2
Sep  4 04:50:55 wbs sshd\[15946\]: Invalid user hoandy from 42.157.128.188
Sep  4 04:50:55 wbs sshd\[15946\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.157.128.188
2019-09-04 23:33:49
167.71.217.144 attackspam
2019-09-04T15:55:56.019822abusebot-3.cloudsearch.cf sshd\[13893\]: Invalid user livia from 167.71.217.144 port 34428
2019-09-05 00:25:22
77.247.181.165 attackspam
tried it too often
2019-09-05 00:45:42
167.71.14.214 attack
Sep  4 12:15:36 plusreed sshd[19181]: Invalid user johanna from 167.71.14.214
...
2019-09-05 00:17:40
190.232.0.206 attackbots
port scan and connect, tcp 23 (telnet)
2019-09-05 00:14:56
67.218.96.156 attackbots
2019-09-04T15:51:58.181612abusebot-6.cloudsearch.cf sshd\[13701\]: Invalid user jboss from 67.218.96.156 port 32925
2019-09-05 00:06:17
178.45.0.209 attack
445/tcp
[2019-09-04]1pkt
2019-09-05 00:43:52

Recently Reported IPs

108.136.181.213 108.136.226.160 108.139.229.123 113.120.39.50
108.156.211.124 108.156.211.43 108.156.211.94 108.156.245.34
108.139.229.95 108.156.211.80 108.156.245.105 113.120.39.52
108.160.144.116 108.160.146.161 108.160.146.124 108.156.245.61
108.160.131.122 108.156.245.70 108.160.145.102 108.160.144.10