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

;; QUESTION SECTION:
;108.220.241.2.			IN	A

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

;; Query time: 42 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 04 01:39:24 CST 2022
;; MSG SIZE  rcvd: 106
Host info
2.241.220.108.in-addr.arpa domain name pointer 108-220-241-2.lightspeed.gdrpmi.sbcglobal.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
2.241.220.108.in-addr.arpa	name = 108-220-241-2.lightspeed.gdrpmi.sbcglobal.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
31.43.99.81 attackspam
Honeypot attack, port: 5555, PTR: unallocated.sta.lan.ua.
2020-04-25 01:17:18
43.248.124.132 attackbotsspam
Brute-force attempt banned
2020-04-25 01:32:40
92.118.37.83 attackspam
Apr 24 19:04:20 debian-2gb-nbg1-2 kernel: \[10006803.619297\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=92.118.37.83 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=15885 PROTO=TCP SPT=51044 DPT=5005 WINDOW=1024 RES=0x00 SYN URGP=0
2020-04-25 01:28:50
39.87.250.92 attack
Honeypot Spam Send
2020-04-25 01:25:29
164.132.101.56 attack
Tried sshing with brute force.
2020-04-25 01:24:48
192.241.175.48 attack
(sshd) Failed SSH login from 192.241.175.48 (US/United States/-): 2 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr 24 19:07:38 ubnt-55d23 sshd[15471]: Invalid user xxx from 192.241.175.48 port 47186
Apr 24 19:07:41 ubnt-55d23 sshd[15471]: Failed password for invalid user xxx from 192.241.175.48 port 47186 ssh2
2020-04-25 01:42:27
139.59.75.111 attackbots
Apr 24 12:31:56 game-panel sshd[19152]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.75.111
Apr 24 12:31:57 game-panel sshd[19152]: Failed password for invalid user limorov from 139.59.75.111 port 46934 ssh2
Apr 24 12:36:07 game-panel sshd[19374]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.75.111
2020-04-25 01:28:33
51.38.80.173 attack
Apr 24 17:47:02 l03 sshd[5604]: Invalid user cherry from 51.38.80.173 port 44998
...
2020-04-25 01:35:46
139.199.0.84 attack
Apr 24 02:31:16 web9 sshd\[6949\]: Invalid user admin from 139.199.0.84
Apr 24 02:31:16 web9 sshd\[6949\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.0.84
Apr 24 02:31:19 web9 sshd\[6949\]: Failed password for invalid user admin from 139.199.0.84 port 47054 ssh2
Apr 24 02:33:50 web9 sshd\[7305\]: Invalid user mu from 139.199.0.84
Apr 24 02:33:50 web9 sshd\[7305\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.0.84
2020-04-25 01:26:43
119.97.164.247 attackbots
2020-04-24T13:30:16.760314shield sshd\[13708\]: Invalid user liman from 119.97.164.247 port 52908
2020-04-24T13:30:16.763796shield sshd\[13708\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.97.164.247
2020-04-24T13:30:19.069264shield sshd\[13708\]: Failed password for invalid user liman from 119.97.164.247 port 52908 ssh2
2020-04-24T13:33:25.289228shield sshd\[14317\]: Invalid user tomcat from 119.97.164.247 port 53024
2020-04-24T13:33:25.292963shield sshd\[14317\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.97.164.247
2020-04-25 01:50:12
94.41.10.126 attackspambots
Unauthorized connection attempt detected from IP address 94.41.10.126 to port 9530 [T]
2020-04-25 01:54:12
129.211.51.65 attack
Apr 24 06:17:15 server1 sshd\[11493\]: Invalid user pekomo from 129.211.51.65
Apr 24 06:17:15 server1 sshd\[11493\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.51.65 
Apr 24 06:17:17 server1 sshd\[11493\]: Failed password for invalid user pekomo from 129.211.51.65 port 49474 ssh2
Apr 24 06:21:59 server1 sshd\[12770\]: Invalid user eric from 129.211.51.65
Apr 24 06:21:59 server1 sshd\[12770\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.51.65 
...
2020-04-25 01:38:31
103.248.33.51 attackbots
(sshd) Failed SSH login from 103.248.33.51 (IN/India/prod1.adisoftronics.net): 2 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr 24 14:36:15 ubnt-55d23 sshd[512]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.248.33.51  user=proftpd
Apr 24 14:36:17 ubnt-55d23 sshd[512]: Failed password for proftpd from 103.248.33.51 port 48540 ssh2
2020-04-25 01:16:18
122.155.204.128 attack
Apr 24 13:32:35 ws19vmsma01 sshd[205006]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.155.204.128
Apr 24 13:32:38 ws19vmsma01 sshd[205006]: Failed password for invalid user jo from 122.155.204.128 port 46180 ssh2
...
2020-04-25 01:37:36
179.95.73.255 attack
Automatic report - Port Scan Attack
2020-04-25 01:42:50

Recently Reported IPs

78.72.191.243 251.114.143.104 164.160.146.230 2.255.96.51
131.114.55.209 62.115.177.119 183.86.191.129 56.50.136.94
156.136.86.101 121.253.57.35 83.121.215.60 93.113.246.71
128.212.239.21 117.205.207.54 19.146.204.195 14.126.159.120
50.144.255.18 57.4.0.181 131.65.30.234 156.101.136.245