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 States

Internet Service Provider: unknown

Hostname: unknown

Organization: University of California, San Diego

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;44.82.173.242.			IN	A

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

;; Query time: 3 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Sat Jul 13 23:43:34 CST 2019
;; MSG SIZE  rcvd: 117
Host info
Host 242.173.82.44.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		67.207.67.2
Address:	67.207.67.2#53

** server can't find 242.173.82.44.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
106.54.18.121 attackbots
Fail2Ban Ban Triggered
2019-11-25 06:05:39
113.142.58.76 attack
24.11.2019 16:27:08 Connection to port 3306 blocked by firewall
2019-11-25 05:58:18
104.236.244.98 attack
frenzy
2019-11-25 06:06:45
222.186.175.161 attack
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.161  user=root
Failed password for root from 222.186.175.161 port 64502 ssh2
Failed password for root from 222.186.175.161 port 64502 ssh2
Failed password for root from 222.186.175.161 port 64502 ssh2
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.161  user=root
2019-11-25 05:49:31
105.96.40.155 attackbots
Attempt to attack host OS, exploiting network vulnerabilities, on 24-11-2019 14:45:22.
2019-11-25 05:47:29
117.2.166.67 attackbotsspam
Unauthorized connection attempt from IP address 117.2.166.67 on Port 445(SMB)
2019-11-25 05:53:52
171.255.117.31 attack
Attempt to attack host OS, exploiting network vulnerabilities, on 24-11-2019 14:45:24.
2019-11-25 05:43:54
178.128.21.32 attackbots
Repeated brute force against a port
2019-11-25 06:15:38
182.30.66.72 attack
Attempt to attack host OS, exploiting network vulnerabilities, on 24-11-2019 14:45:25.
2019-11-25 05:42:54
118.70.215.62 attackspam
SSH brutforce
2019-11-25 05:45:17
46.101.73.64 attackbotsspam
2019-11-24T19:30:01.305254shield sshd\[3651\]: Invalid user 1qazasd from 46.101.73.64 port 60396
2019-11-24T19:30:01.309779shield sshd\[3651\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.73.64
2019-11-24T19:30:03.817004shield sshd\[3651\]: Failed password for invalid user 1qazasd from 46.101.73.64 port 60396 ssh2
2019-11-24T19:35:55.147833shield sshd\[5487\]: Invalid user moldskred from 46.101.73.64 port 39920
2019-11-24T19:35:55.152426shield sshd\[5487\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.73.64
2019-11-25 06:07:12
123.207.88.97 attack
" "
2019-11-25 06:06:31
49.234.99.246 attack
Nov 24 21:04:22 lnxmysql61 sshd[16944]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.99.246
2019-11-25 05:48:46
36.71.239.43 attackbotsspam
Unauthorized connection attempt from IP address 36.71.239.43 on Port 445(SMB)
2019-11-25 06:01:56
168.232.130.188 attackspambots
2019-11-24T14:44:45.535Z CLOSE host=168.232.130.188 port=56139 fd=4 time=20.017 bytes=13
...
2019-11-25 06:13:03

Recently Reported IPs

179.99.15.190 91.227.2.222 134.84.161.123 168.187.81.185
38.163.44.17 177.65.183.226 195.2.205.220 122.23.82.86
195.241.186.109 47.136.23.199 46.201.66.25 13.90.47.13
145.118.206.252 66.172.221.152 141.237.77.101 91.91.98.216
201.176.173.7 101.103.227.124 114.232.194.16 57.184.78.125