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

;; QUESTION SECTION:
;193.239.82.117.			IN	A

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

;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 00:46:12 CST 2025
;; MSG SIZE  rcvd: 107
Host info
117.82.239.193.in-addr.arpa domain name pointer nat82-117.merinet.pl.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
117.82.239.193.in-addr.arpa	name = nat82-117.merinet.pl.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
201.108.215.67 attackbotsspam
Unauthorized connection attempt from IP address 201.108.215.67 on Port 445(SMB)
2019-10-02 08:54:54
106.2.25.17 attackbots
Port scan
2019-10-02 08:14:01
167.99.65.138 attackspam
Oct  1 13:40:26 sachi sshd\[28177\]: Invalid user admin from 167.99.65.138
Oct  1 13:40:26 sachi sshd\[28177\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.65.138
Oct  1 13:40:27 sachi sshd\[28177\]: Failed password for invalid user admin from 167.99.65.138 port 46100 ssh2
Oct  1 13:45:04 sachi sshd\[28626\]: Invalid user ftptest from 167.99.65.138
Oct  1 13:45:04 sachi sshd\[28626\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.65.138
2019-10-02 08:29:35
188.166.87.238 attack
2019-10-02T00:27:04.464596shield sshd\[19644\]: Invalid user joan from 188.166.87.238 port 48920
2019-10-02T00:27:04.470100shield sshd\[19644\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.87.238
2019-10-02T00:27:06.142086shield sshd\[19644\]: Failed password for invalid user joan from 188.166.87.238 port 48920 ssh2
2019-10-02T00:31:01.447280shield sshd\[19889\]: Invalid user temp from 188.166.87.238 port 60664
2019-10-02T00:31:01.452562shield sshd\[19889\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.87.238
2019-10-02 08:37:59
190.52.128.8 attack
Oct  1 14:06:01 web9 sshd\[31914\]: Invalid user manjaro from 190.52.128.8
Oct  1 14:06:01 web9 sshd\[31914\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.52.128.8
Oct  1 14:06:03 web9 sshd\[31914\]: Failed password for invalid user manjaro from 190.52.128.8 port 50032 ssh2
Oct  1 14:10:55 web9 sshd\[361\]: Invalid user king from 190.52.128.8
Oct  1 14:10:55 web9 sshd\[361\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.52.128.8
2019-10-02 08:25:18
187.178.77.146 attackbotsspam
Automatic report - Port Scan Attack
2019-10-02 08:32:09
49.255.179.216 attack
Oct  2 02:06:48 microserver sshd[47534]: Invalid user gitlab from 49.255.179.216 port 44666
Oct  2 02:06:48 microserver sshd[47534]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.255.179.216
Oct  2 02:06:50 microserver sshd[47534]: Failed password for invalid user gitlab from 49.255.179.216 port 44666 ssh2
Oct  2 02:12:02 microserver sshd[48219]: Invalid user swadmin from 49.255.179.216 port 56464
Oct  2 02:12:02 microserver sshd[48219]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.255.179.216
Oct  2 02:22:15 microserver sshd[49561]: Invalid user apagar from 49.255.179.216 port 51822
Oct  2 02:22:15 microserver sshd[49561]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.255.179.216
Oct  2 02:22:17 microserver sshd[49561]: Failed password for invalid user apagar from 49.255.179.216 port 51822 ssh2
Oct  2 02:27:28 microserver sshd[50228]: pam_unix(sshd:auth): authentication fail
2019-10-02 08:40:14
91.121.2.33 attackbots
Oct  2 02:09:44 MK-Soft-VM7 sshd[1032]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.121.2.33 
Oct  2 02:09:46 MK-Soft-VM7 sshd[1032]: Failed password for invalid user negotino3 from 91.121.2.33 port 51559 ssh2
...
2019-10-02 08:54:12
82.199.96.164 attackspam
Unauthorized connection attempt from IP address 82.199.96.164 on Port 445(SMB)
2019-10-02 08:35:54
186.224.63.172 attack
WordPress wp-login brute force :: 186.224.63.172 0.120 BYPASS [02/Oct/2019:07:01:26  1000] [censored_1] "POST /wp-login.php HTTP/1.1" 200 3972 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-10-02 08:22:45
64.202.187.152 attack
Jul 22 18:48:11 vtv3 sshd\[18934\]: Invalid user dv from 64.202.187.152 port 43614
Jul 22 18:48:11 vtv3 sshd\[18934\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.202.187.152
Jul 22 18:48:13 vtv3 sshd\[18934\]: Failed password for invalid user dv from 64.202.187.152 port 43614 ssh2
Jul 22 18:52:38 vtv3 sshd\[21139\]: Invalid user testuser from 64.202.187.152 port 40446
Jul 22 18:52:38 vtv3 sshd\[21139\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.202.187.152
Jul 22 19:05:40 vtv3 sshd\[28165\]: Invalid user jira from 64.202.187.152 port 59174
Jul 22 19:05:40 vtv3 sshd\[28165\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.202.187.152
Jul 22 19:05:42 vtv3 sshd\[28165\]: Failed password for invalid user jira from 64.202.187.152 port 59174 ssh2
Jul 22 19:10:07 vtv3 sshd\[30382\]: Invalid user andi from 64.202.187.152 port 56010
Jul 22 19:10:07 vtv3 sshd\[30382\]: pa
2019-10-02 08:20:30
197.185.186.77 attackspambots
Unauthorized connection attempt from IP address 197.185.186.77 on Port 445(SMB)
2019-10-02 08:10:13
103.76.20.158 attackbotsspam
Unauthorized connection attempt from IP address 103.76.20.158 on Port 445(SMB)
2019-10-02 08:35:11
200.201.217.104 attack
Oct  2 03:33:49 server sshd\[9738\]: Invalid user smb from 200.201.217.104 port 57052
Oct  2 03:33:49 server sshd\[9738\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.201.217.104
Oct  2 03:33:51 server sshd\[9738\]: Failed password for invalid user smb from 200.201.217.104 port 57052 ssh2
Oct  2 03:38:58 server sshd\[26211\]: Invalid user teamspeak from 200.201.217.104 port 41830
Oct  2 03:38:58 server sshd\[26211\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.201.217.104
2019-10-02 08:46:28
193.32.161.48 attack
firewall-block, port(s): 2728/tcp, 2729/tcp, 2730/tcp, 6892/tcp, 26690/tcp
2019-10-02 08:36:44

Recently Reported IPs

72.51.170.189 63.110.140.131 184.231.27.111 159.61.17.106
216.82.188.19 131.127.190.168 182.214.173.113 217.101.101.236
131.210.154.5 74.68.142.225 244.122.38.245 48.34.215.161
191.167.137.38 248.148.143.47 69.100.233.123 166.152.78.119
218.140.120.175 123.41.40.71 218.249.26.237 3.208.170.1