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 Kingdom of Great Britain and Northern Ireland (the)

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

;; QUESTION SECTION:
;82.2.166.13.			IN	A

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

;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 07 00:32:23 CST 2025
;; MSG SIZE  rcvd: 104
Host info
Host 13.166.2.82.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 13.166.2.82.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
176.32.185.242 attackspam
unauthorized connection attempt
2020-02-07 13:13:55
61.219.170.130 attackspam
unauthorized connection attempt
2020-02-07 13:37:56
156.222.22.178 attackbotsspam
unauthorized connection attempt
2020-02-07 13:14:56
64.202.186.32 attackbotsspam
serveres are UTC 
Lines containing failures of 64.202.186.32
Feb  6 23:04:57 tux2 sshd[1942]: Did not receive identification string from 64.202.186.32 port 45094
Feb  6 23:08:03 tux2 sshd[2128]: Failed password for r.r from 64.202.186.32 port 42180 ssh2
Feb  6 23:08:03 tux2 sshd[2128]: Received disconnect from 64.202.186.32 port 42180:11: Normal Shutdown, Thank you for playing [preauth]
Feb  6 23:08:03 tux2 sshd[2128]: Disconnected from authenticating user r.r 64.202.186.32 port 42180 [preauth]
Feb  6 23:09:08 tux2 sshd[2181]: Failed password for r.r from 64.202.186.32 port 41166 ssh2
Feb  6 23:09:08 tux2 sshd[2181]: Received disconnect from 64.202.186.32 port 41166:11: Normal Shutdown, Thank you for playing [preauth]
Feb  6 23:09:08 tux2 sshd[2181]: Disconnected from authenticating user r.r 64.202.186.32 port 41166 [preauth]
Feb  6 23:10:33 tux2 sshd[2268]: Failed password for r.r from 64.202.186.32 port 40156 ssh2
Feb  6 23:10:33 tux2 sshd[2268]: Received disconnect fr........
------------------------------
2020-02-07 13:29:16
58.87.103.110 attack
unauthorized connection attempt
2020-02-07 13:26:57
103.38.14.84 attack
Automatic report - Port Scan Attack
2020-02-07 13:25:48
115.61.13.174 attack
unauthorized connection attempt
2020-02-07 13:16:05
218.161.97.174 attackbotsspam
unauthorized connection attempt
2020-02-07 13:08:55
180.177.241.252 attackbotsspam
unauthorized connection attempt
2020-02-07 13:25:08
40.126.120.71 attack
Feb  7 01:51:14 firewall sshd[25595]: Invalid user soy from 40.126.120.71
Feb  7 01:51:15 firewall sshd[25595]: Failed password for invalid user soy from 40.126.120.71 port 55174 ssh2
Feb  7 01:56:00 firewall sshd[25816]: Invalid user wto from 40.126.120.71
...
2020-02-07 13:45:39
136.232.104.50 attack
unauthorized connection attempt
2020-02-07 13:03:39
111.229.57.229 attackbots
unauthorized connection attempt
2020-02-07 13:05:57
177.53.105.88 attack
unauthorized connection attempt
2020-02-07 13:13:16
59.99.211.184 attackbots
unauthorized connection attempt
2020-02-07 13:07:52
36.34.121.198 attackspambots
unauthorized connection attempt
2020-02-07 13:20:13

Recently Reported IPs

50.120.212.101 159.29.31.210 194.65.94.5 107.133.126.61
34.1.126.202 3.182.56.141 215.133.250.237 152.225.156.176
119.84.250.171 253.142.208.132 245.87.164.190 247.158.210.199
20.207.2.218 210.90.41.215 87.101.118.89 228.106.255.122
245.173.145.255 72.37.64.221 19.64.216.93 18.147.99.87