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

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

;; QUESTION SECTION:
;148.82.116.160.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jan 31 13:47:14 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 160.116.82.148.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server:		183.60.82.98
Address:	183.60.82.98#53

** server can't find 160.116.82.148.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
80.254.104.101 attackbotsspam
Unauthorized connection attempt from IP address 80.254.104.101 on Port 445(SMB)
2019-10-03 02:02:58
112.175.120.64 attackspambots
3389BruteforceFW23
2019-10-03 02:02:30
79.139.180.174 attackspambots
Oct  2 12:12:59 f201 sshd[32125]: Connection closed by 79.139.180.174 [preauth]
Oct  2 13:28:26 f201 sshd[19012]: Connection closed by 79.139.180.174 [preauth]
Oct  2 14:11:49 f201 sshd[30540]: Connection closed by 79.139.180.174 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=79.139.180.174
2019-10-03 01:36:16
51.255.168.30 attack
2019-10-02T15:14:23.348896abusebot-4.cloudsearch.cf sshd\[17622\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=30.ip-51-255-168.eu  user=root
2019-10-03 01:49:04
112.175.120.216 attackbotsspam
Oct  2 07:15:20 localhost kernel: [3752739.237399] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:a8:41:08:00 SRC=112.175.120.216 DST=[mungedIP2] LEN=40 TOS=0x08 PREC=0x20 TTL=82 ID=5949 DF PROTO=TCP SPT=56422 DPT=22 WINDOW=29200 RES=0x00 SYN URGP=0 
Oct  2 07:15:20 localhost kernel: [3752739.237423] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:a8:41:08:00 SRC=112.175.120.216 DST=[mungedIP2] LEN=40 TOS=0x08 PREC=0x20 TTL=82 ID=5949 DF PROTO=TCP SPT=56422 DPT=22 SEQ=912109526 ACK=0 WINDOW=29200 RES=0x00 SYN URGP=0 
Oct  2 08:31:35 localhost kernel: [3757314.737323] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:aa:c1:08:00 SRC=112.175.120.216 DST=[mungedIP2] LEN=40 TOS=0x08 PREC=0x20 TTL=82 ID=23703 DF PROTO=TCP SPT=65322 DPT=22 WINDOW=29200 RES=0x00 SYN URGP=0 
Oct  2 08:31:35 localhost kernel: [3757314.737356] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:aa:c1:08:00 SRC=112.175.120.216 DST=[mungedIP2] LEN=40 TOS=0
2019-10-03 01:38:02
177.191.159.211 attackspam
19/10/2@08:31:41: FAIL: Alarm-Intrusion address from=177.191.159.211
19/10/2@08:31:41: FAIL: Alarm-Intrusion address from=177.191.159.211
...
2019-10-03 01:26:51
112.175.120.100 attackspam
" "
2019-10-03 02:09:27
190.104.167.194 attackbots
Oct  2 13:21:34 ny01 sshd[7360]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.104.167.194
Oct  2 13:21:36 ny01 sshd[7360]: Failed password for invalid user hcat from 190.104.167.194 port 7009 ssh2
Oct  2 13:27:10 ny01 sshd[8701]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.104.167.194
2019-10-03 01:27:48
110.164.189.53 attackbotsspam
Oct  2 19:23:28 vps01 sshd[17818]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.164.189.53
Oct  2 19:23:31 vps01 sshd[17818]: Failed password for invalid user ma from 110.164.189.53 port 40440 ssh2
2019-10-03 01:24:40
213.32.71.196 attack
2019-10-02T20:32:15.388595enmeeting.mahidol.ac.th sshd\[26307\]: Invalid user matt from 213.32.71.196 port 42988
2019-10-02T20:32:15.407312enmeeting.mahidol.ac.th sshd\[26307\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=196.ip-213-32-71.eu
2019-10-02T20:32:16.858538enmeeting.mahidol.ac.th sshd\[26307\]: Failed password for invalid user matt from 213.32.71.196 port 42988 ssh2
...
2019-10-03 01:41:03
112.175.120.111 attackbots
3389BruteforceFW23
2019-10-03 02:12:34
152.136.192.187 attack
Oct  2 19:02:52 server sshd\[3931\]: Invalid user cacti from 152.136.192.187 port 44272
Oct  2 19:02:52 server sshd\[3931\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.136.192.187
Oct  2 19:02:54 server sshd\[3931\]: Failed password for invalid user cacti from 152.136.192.187 port 44272 ssh2
Oct  2 19:09:17 server sshd\[5585\]: Invalid user zmss from 152.136.192.187 port 55848
Oct  2 19:09:17 server sshd\[5585\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.136.192.187
2019-10-03 01:37:37
51.38.179.179 attack
$f2bV_matches
2019-10-03 01:43:40
113.121.243.245 attack
SASL broute force
2019-10-03 02:10:21
106.13.15.153 attackspambots
Oct  2 18:47:20 vmanager6029 sshd\[32150\]: Invalid user nou from 106.13.15.153 port 48058
Oct  2 18:47:20 vmanager6029 sshd\[32150\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.15.153
Oct  2 18:47:22 vmanager6029 sshd\[32150\]: Failed password for invalid user nou from 106.13.15.153 port 48058 ssh2
2019-10-03 01:23:25

Recently Reported IPs

103.181.57.213 225.55.176.15 43.18.244.232 161.225.204.249
225.6.79.197 115.100.52.219 48.9.44.99 60.200.117.61
140.14.89.157 187.112.106.88 118.90.143.222 241.97.107.246
150.252.136.177 33.255.234.18 7.177.72.148 96.76.147.150
251.220.70.192 139.186.139.247 89.129.111.161 218.60.2.241