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: Norway

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

;; QUESTION SECTION:
;83.108.139.121.			IN	A

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

;; Query time: 38 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 12 20:01:56 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 121.139.108.83.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 121.139.108.83.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
188.165.24.200 attackbotsspam
Automatic report - SSH Brute-Force Attack
2019-09-29 01:38:28
43.226.146.112 attack
2019-09-28T12:30:15.749952abusebot-6.cloudsearch.cf sshd\[32508\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.226.146.112  user=root
2019-09-29 01:46:12
107.173.51.116 attackbotsspam
Sep 28 08:25:55 ny01 sshd[15046]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.173.51.116
Sep 28 08:25:57 ny01 sshd[15046]: Failed password for invalid user trustguest from 107.173.51.116 port 54530 ssh2
Sep 28 08:30:18 ny01 sshd[15979]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.173.51.116
2019-09-29 01:41:56
118.163.178.146 attackbotsspam
Sep 28 08:47:55 ny01 sshd[19347]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.163.178.146
Sep 28 08:47:58 ny01 sshd[19347]: Failed password for invalid user I2b2workdata2 from 118.163.178.146 port 36240 ssh2
Sep 28 08:57:06 ny01 sshd[21348]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.163.178.146
2019-09-29 01:47:39
64.202.187.48 attackbots
2019-09-28T16:34:48.506441tmaserv sshd\[25034\]: Failed password for invalid user bis123 from 64.202.187.48 port 55276 ssh2
2019-09-28T16:47:07.880438tmaserv sshd\[25746\]: Invalid user tania123 from 64.202.187.48 port 35068
2019-09-28T16:47:07.883914tmaserv sshd\[25746\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.202.187.48
2019-09-28T16:47:10.003733tmaserv sshd\[25746\]: Failed password for invalid user tania123 from 64.202.187.48 port 35068 ssh2
2019-09-28T16:51:12.248629tmaserv sshd\[25980\]: Invalid user asd123 from 64.202.187.48 port 47168
2019-09-28T16:51:12.251525tmaserv sshd\[25980\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.202.187.48
...
2019-09-29 01:43:47
183.82.118.179 attackspam
Unauthorized connection attempt from IP address 183.82.118.179 on Port 445(SMB)
2019-09-29 01:29:10
51.38.224.46 attackspambots
Sep 28 04:04:59 aiointranet sshd\[21780\]: Invalid user shclient from 51.38.224.46
Sep 28 04:04:59 aiointranet sshd\[21780\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.38.224.46
Sep 28 04:05:01 aiointranet sshd\[21780\]: Failed password for invalid user shclient from 51.38.224.46 port 46208 ssh2
Sep 28 04:09:37 aiointranet sshd\[22268\]: Invalid user admin from 51.38.224.46
Sep 28 04:09:37 aiointranet sshd\[22268\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.38.224.46
2019-09-29 02:04:46
202.122.23.70 attackbots
Triggered by Fail2Ban at Vostok web server
2019-09-29 02:00:02
198.71.238.14 attack
xmlrpc attack
2019-09-29 01:42:31
195.16.41.170 attack
[Aegis] @ 2019-09-28 18:14:37  0100 -> Attempted Administrator Privilege Gain: ET SCAN LibSSH Based Frequent SSH Connections Likely BruteForce Attack
2019-09-29 01:25:24
103.27.202.18 attackbotsspam
Sep 28 07:07:54 web9 sshd\[32419\]: Invalid user Oyster from 103.27.202.18
Sep 28 07:07:54 web9 sshd\[32419\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.27.202.18
Sep 28 07:07:56 web9 sshd\[32419\]: Failed password for invalid user Oyster from 103.27.202.18 port 59080 ssh2
Sep 28 07:12:33 web9 sshd\[877\]: Invalid user valvoja from 103.27.202.18
Sep 28 07:12:33 web9 sshd\[877\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.27.202.18
2019-09-29 01:45:05
14.162.56.109 attackbotsspam
Unauthorized connection attempt from IP address 14.162.56.109 on Port 445(SMB)
2019-09-29 01:39:48
82.223.24.191 attack
Sep 28 18:37:15 MainVPS sshd[20617]: Invalid user sales from 82.223.24.191 port 39604
Sep 28 18:37:15 MainVPS sshd[20617]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.223.24.191
Sep 28 18:37:15 MainVPS sshd[20617]: Invalid user sales from 82.223.24.191 port 39604
Sep 28 18:37:17 MainVPS sshd[20617]: Failed password for invalid user sales from 82.223.24.191 port 39604 ssh2
Sep 28 18:41:41 MainVPS sshd[21069]: Invalid user u from 82.223.24.191 port 52772
...
2019-09-29 02:04:17
78.176.246.34 attackspambots
Unauthorized connection attempt from IP address 78.176.246.34 on Port 445(SMB)
2019-09-29 01:34:50
77.247.110.241 attack
firewall-block, port(s): 15060/udp
2019-09-29 02:02:38

Recently Reported IPs

162.18.29.138 224.69.227.143 250.104.71.19 202.205.189.31
17.231.157.6 164.85.210.28 226.201.50.153 158.10.75.222
245.97.100.24 79.197.133.68 178.28.68.207 61.224.62.83
240.188.51.162 7.164.5.4 230.51.133.190 251.130.238.155
130.245.90.62 223.248.31.42 232.66.128.73 9.119.201.164