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

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

;; QUESTION SECTION:
;109.232.216.82.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 25 12:53:25 CST 2022
;; MSG SIZE  rcvd: 107
Host info
82.216.232.109.in-addr.arpa domain name pointer srvc79.turhost.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
82.216.232.109.in-addr.arpa	name = srvc79.turhost.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
210.4.118.100 attackbots
Feb  5 05:55:28 grey postfix/smtpd\[26517\]: NOQUEUE: reject: RCPT from unknown\[210.4.118.100\]: 554 5.7.1 Service unavailable\; Client host \[210.4.118.100\] blocked using cbl.abuseat.org\; Blocked - see http://www.abuseat.org/lookup.cgi\?ip=210.4.118.100\; from=\ to=\ proto=ESMTP helo=\<\[210.4.118.100\]\>
...
2020-02-05 13:10:10
103.56.113.69 attack
Unauthorized connection attempt detected from IP address 103.56.113.69 to port 2220 [J]
2020-02-05 10:34:05
186.211.3.36 attackspam
Unauthorized connection attempt detected from IP address 186.211.3.36 to port 80 [J]
2020-02-05 10:52:16
77.120.102.132 attackbots
2,50-01/01 [bc02/m78] PostRequest-Spammer scoring: lisboa
2020-02-05 13:06:41
45.74.150.144 attackbotsspam
Unauthorized connection attempt detected from IP address 45.74.150.144 to port 5555 [J]
2020-02-05 10:42:51
42.115.164.64 attackspam
Unauthorized connection attempt detected from IP address 42.115.164.64 to port 23 [J]
2020-02-05 10:17:35
223.99.216.130 attack
Unauthorized connection attempt detected from IP address 223.99.216.130 to port 1433 [J]
2020-02-05 10:20:07
124.156.241.17 attackbotsspam
Unauthorized connection attempt detected from IP address 124.156.241.17 to port 2600 [J]
2020-02-05 10:27:56
82.80.154.234 attackbotsspam
Unauthorized connection attempt detected from IP address 82.80.154.234 to port 23 [J]
2020-02-05 10:37:04
31.206.124.106 attack
Unauthorized connection attempt detected from IP address 31.206.124.106 to port 23 [J]
2020-02-05 10:18:46
143.255.2.146 attack
Unauthorized connection attempt detected from IP address 143.255.2.146 to port 8080 [J]
2020-02-05 10:26:43
175.4.222.250 attack
Unauthorized connection attempt detected from IP address 175.4.222.250 to port 23 [J]
2020-02-05 10:24:21
41.221.84.234 attackbots
Unauthorized connection attempt detected from IP address 41.221.84.234 to port 1433 [J]
2020-02-05 10:43:30
27.221.97.3 attackbots
Unauthorized connection attempt detected from IP address 27.221.97.3 to port 2220 [J]
2020-02-05 10:45:26
190.94.149.243 attackbotsspam
Unauthorized connection attempt detected from IP address 190.94.149.243 to port 80 [J]
2020-02-05 10:22:20

Recently Reported IPs

109.232.217.10 109.232.217.103 109.232.217.183 109.232.217.197
109.232.217.192 109.232.217.211 109.232.217.40 109.232.217.37
109.232.217.49 109.232.219.100 109.232.219.182 109.232.218.236
109.232.220.120 109.232.218.61 108.167.175.130 109.234.161.18
109.234.161.194 109.234.161.110 109.234.161.109 109.234.161.158