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

;; QUESTION SECTION:
;82.110.104.242.			IN	A

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

;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 23 11:46:59 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 242.104.110.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 242.104.110.82.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
104.248.123.197 attackbotsspam
Invalid user lois from 104.248.123.197 port 42692
2020-08-31 01:27:37
192.99.168.9 attackbotsspam
Aug 30 19:24:58 ift sshd\[63922\]: Invalid user daniel from 192.99.168.9Aug 30 19:24:59 ift sshd\[63922\]: Failed password for invalid user daniel from 192.99.168.9 port 42128 ssh2Aug 30 19:28:34 ift sshd\[64572\]: Failed password for invalid user admin from 192.99.168.9 port 39358 ssh2Aug 30 19:31:57 ift sshd\[65101\]: Invalid user raju from 192.99.168.9Aug 30 19:31:59 ift sshd\[65101\]: Failed password for invalid user raju from 192.99.168.9 port 36588 ssh2
...
2020-08-31 01:09:12
164.132.145.70 attack
Aug 30 21:19:06 webhost01 sshd[8106]: Failed password for root from 164.132.145.70 port 33554 ssh2
Aug 30 21:22:40 webhost01 sshd[8158]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.145.70
...
2020-08-31 01:16:02
222.89.70.216 attack
ET SCAN Suspicious inbound to mySQL port 3306 - port: 3306 proto: tcp cat: Potentially Bad Trafficbytes: 60
2020-08-31 01:53:43
222.186.175.182 attackbotsspam
[MK-VM4] SSH login failed
2020-08-31 01:45:26
51.83.69.84 attackspam
fahrlehrer-fortbildung-hessen.de 51.83.69.84 [30/Aug/2020:15:11:19 +0200] "POST /xmlrpc.php HTTP/1.0" 301 537 "-" "Mozilla/5.0 (Windows NT 10.0; WOW64; rv:56.0) Gecko/20100101 Firefox/56.0"
www.fahrlehrerfortbildung-hessen.de 51.83.69.84 [30/Aug/2020:15:11:20 +0200] "POST /xmlrpc.php HTTP/1.0" 200 3595 "-" "Mozilla/5.0 (Windows NT 10.0; WOW64; rv:56.0) Gecko/20100101 Firefox/56.0"
2020-08-31 01:49:54
104.152.59.33 attackspam
2020-08-30T12:13:01.939471shield sshd\[22167\]: Invalid user admin from 104.152.59.33 port 38019
2020-08-30T12:13:01.984415shield sshd\[22167\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.152.59.33
2020-08-30T12:13:03.863950shield sshd\[22167\]: Failed password for invalid user admin from 104.152.59.33 port 38019 ssh2
2020-08-30T12:13:04.351524shield sshd\[22178\]: Invalid user admin from 104.152.59.33 port 38084
2020-08-30T12:13:04.395476shield sshd\[22178\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.152.59.33
2020-08-31 01:26:14
101.37.158.147 attackbots
(sshd) Failed SSH login from 101.37.158.147 (CN/China/-): 5 in the last 3600 secs
2020-08-31 01:29:46
104.244.76.170 attackspambots
Invalid user admin from 104.244.76.170 port 43382
2020-08-31 01:29:16
49.235.202.65 attack
Aug 30 19:18:00 server sshd[543]: Failed password for invalid user user from 49.235.202.65 port 47838 ssh2
Aug 30 19:19:07 server sshd[2558]: Failed password for invalid user koen from 49.235.202.65 port 32832 ssh2
Aug 30 19:20:13 server sshd[4393]: Failed password for root from 49.235.202.65 port 46052 ssh2
2020-08-31 01:30:42
49.232.5.172 attackspambots
2020-08-30T16:41:32.091547abusebot-6.cloudsearch.cf sshd[4402]: Invalid user etl from 49.232.5.172 port 46356
2020-08-30T16:41:32.097669abusebot-6.cloudsearch.cf sshd[4402]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.5.172
2020-08-30T16:41:32.091547abusebot-6.cloudsearch.cf sshd[4402]: Invalid user etl from 49.232.5.172 port 46356
2020-08-30T16:41:34.737561abusebot-6.cloudsearch.cf sshd[4402]: Failed password for invalid user etl from 49.232.5.172 port 46356 ssh2
2020-08-30T16:46:25.628815abusebot-6.cloudsearch.cf sshd[4405]: Invalid user web from 49.232.5.172 port 46530
2020-08-30T16:46:25.634541abusebot-6.cloudsearch.cf sshd[4405]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.5.172
2020-08-30T16:46:25.628815abusebot-6.cloudsearch.cf sshd[4405]: Invalid user web from 49.232.5.172 port 46530
2020-08-30T16:46:27.496703abusebot-6.cloudsearch.cf sshd[4405]: Failed password for invalid use
...
2020-08-31 01:28:08
178.33.212.220 attackspam
SSH BruteForce Attack
2020-08-31 01:41:28
176.31.181.168 attackspam
Invalid user steam from 176.31.181.168 port 51266
2020-08-31 01:41:48
192.64.80.135 attackspambots
(sshd) Failed SSH login from 192.64.80.135 (US/United States/server.sabrilogic.com): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Aug 30 11:18:53 server sshd[9112]: Invalid user angelo from 192.64.80.135 port 19079
Aug 30 11:18:55 server sshd[9112]: Failed password for invalid user angelo from 192.64.80.135 port 19079 ssh2
Aug 30 11:27:39 server sshd[13185]: Invalid user manu from 192.64.80.135 port 59358
Aug 30 11:27:42 server sshd[13185]: Failed password for invalid user manu from 192.64.80.135 port 59358 ssh2
Aug 30 11:32:50 server sshd[15668]: Invalid user lat from 192.64.80.135 port 12177
2020-08-31 01:12:28
224.0.0.252 botsattackproxy
there are unmediated big problems with this ip range still, in someway utilising bt tv stream packets unbeknowing to bt home hub wifi customers. devices become host servers and use of US at&t proxy ip's on some home hub locations routing other traffic. BT do not use proxy's on home hub connections
2020-08-31 01:27:40

Recently Reported IPs

193.195.108.174 98.61.175.67 186.133.180.205 222.170.163.204
211.55.69.53 250.230.145.220 90.205.141.113 55.186.63.121
148.45.1.206 228.158.114.210 190.163.3.8 204.85.7.66
24.72.181.41 241.197.107.164 48.183.173.245 180.115.177.215
142.52.158.29 154.35.121.166 120.188.176.254 207.219.99.253