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

;; QUESTION SECTION:
;82.145.209.140.			IN	A

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

;; Query time: 62 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 02 20:59:52 CST 2022
;; MSG SIZE  rcvd: 107
Host info
140.209.145.82.in-addr.arpa domain name pointer h12-08-07.opera-mini.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
140.209.145.82.in-addr.arpa	name = h12-08-07.opera-mini.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
189.207.250.86 attackspambots
445/tcp 445/tcp
[2019-10-22/23]2pkt
2019-10-24 14:02:02
18.225.31.114 attack
Oct 24 07:49:01 MK-Soft-VM3 sshd[32414]: Failed password for root from 18.225.31.114 port 55982 ssh2
Oct 24 07:52:51 MK-Soft-VM3 sshd[32553]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=18.225.31.114 
...
2019-10-24 14:00:21
123.207.231.63 attack
Oct 24 06:54:23 minden010 sshd[5598]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.207.231.63
Oct 24 06:54:25 minden010 sshd[5598]: Failed password for invalid user 123 from 123.207.231.63 port 49876 ssh2
Oct 24 06:59:26 minden010 sshd[7284]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.207.231.63
...
2019-10-24 14:09:51
123.152.215.222 attack
23/tcp
[2019-10-24]1pkt
2019-10-24 14:32:41
222.186.175.212 attack
Oct 24 11:17:00 gw1 sshd[9699]: Failed password for root from 222.186.175.212 port 52408 ssh2
Oct 24 11:17:04 gw1 sshd[9699]: Failed password for root from 222.186.175.212 port 52408 ssh2
...
2019-10-24 14:21:15
117.232.127.50 attackbots
$f2bV_matches
2019-10-24 14:08:19
139.219.14.12 attackbots
$f2bV_matches
2019-10-24 14:06:03
157.245.103.117 attack
Oct 24 00:48:58 firewall sshd[13154]: Invalid user rosa from 157.245.103.117
Oct 24 00:49:00 firewall sshd[13154]: Failed password for invalid user rosa from 157.245.103.117 port 33078 ssh2
Oct 24 00:53:17 firewall sshd[13217]: Invalid user naomi from 157.245.103.117
...
2019-10-24 14:13:56
159.203.190.189 attack
Oct 24 07:45:20 vps647732 sshd[24611]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.203.190.189
Oct 24 07:45:21 vps647732 sshd[24611]: Failed password for invalid user sammy from 159.203.190.189 port 49801 ssh2
...
2019-10-24 14:04:28
112.175.127.186 attackbots
10/24/2019-02:01:02.935888 112.175.127.186 Protocol: 6 ET SCAN Potential SSH Scan
2019-10-24 14:06:34
182.61.22.205 attackbotsspam
web-1 [ssh_2] SSH Attack
2019-10-24 14:32:20
218.94.140.106 attackspam
2019-10-24T03:53:03.722834abusebot-3.cloudsearch.cf sshd\[2389\]: Invalid user 1qaz@2wsx from 218.94.140.106 port 2101
2019-10-24 14:22:15
112.175.127.189 attackspambots
10/24/2019-02:26:38.344169 112.175.127.189 Protocol: 6 ET SCAN Potential SSH Scan
2019-10-24 14:27:03
113.160.202.136 attack
1433/tcp
[2019-10-24]1pkt
2019-10-24 14:23:34
89.197.125.206 attackbots
22/tcp 22/tcp
[2019-10-20/24]2pkt
2019-10-24 14:05:17

Recently Reported IPs

113.117.15.48 164.110.97.91 113.117.180.51 113.117.187.218
113.117.190.5 113.117.191.230 113.117.192.11 89.173.10.135
113.117.192.127 113.117.192.135 113.117.192.146 113.117.192.149
113.117.192.151 113.117.192.154 113.117.192.160 113.117.192.164
113.117.192.170 113.117.192.179 113.117.192.181 113.117.192.184