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

;; QUESTION SECTION:
;66.52.148.194.			IN	A

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

;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jan 10 13:40:08 CST 2022
;; MSG SIZE  rcvd: 106
Host info
194.148.52.66.in-addr.arpa domain name pointer 066-052-148-194.res.spectrum.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
194.148.52.66.in-addr.arpa	name = 066-052-148-194.res.spectrum.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
148.70.96.124 attackspam
Dec  7 10:50:34 srv206 sshd[29146]: Invalid user cavaney from 148.70.96.124
...
2019-12-07 18:03:57
222.186.175.148 attackspam
2019-12-07T09:29:36.211605abusebot-3.cloudsearch.cf sshd\[9583\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.148  user=root
2019-12-07 17:34:38
218.153.113.217 attackspambots
UTC: 2019-12-06 port: 26/tcp
2019-12-07 17:56:54
91.215.244.12 attack
<6 unauthorized SSH connections
2019-12-07 17:47:46
195.14.105.107 attack
Dec  7 12:39:32 areeb-Workstation sshd[5478]: Failed password for root from 195.14.105.107 port 36106 ssh2
...
2019-12-07 18:07:34
222.102.27.19 attackbotsspam
MVPower DVR TV Shell Unauthenticated Command Execution Vulnerability, PTR: PTR record not found
2019-12-07 17:43:37
123.12.166.26 attackspambots
Port Scan
2019-12-07 17:49:13
222.186.173.238 attack
Dec  7 12:48:06 debian-2gb-vpn-nbg1-1 sshd[7401]: Failed password for root from 222.186.173.238 port 13886 ssh2
Dec  7 12:48:10 debian-2gb-vpn-nbg1-1 sshd[7401]: Failed password for root from 222.186.173.238 port 13886 ssh2
Dec  7 12:48:13 debian-2gb-vpn-nbg1-1 sshd[7401]: Failed password for root from 222.186.173.238 port 13886 ssh2
Dec  7 12:48:17 debian-2gb-vpn-nbg1-1 sshd[7401]: Failed password for root from 222.186.173.238 port 13886 ssh2
2019-12-07 17:50:17
99.56.194.131 attack
Netgear DGN Device Remote Command Execution Vulnerability, PTR: PTR record not found
2019-12-07 17:58:43
188.213.49.60 attack
Dec  7 10:09:27 vps691689 sshd[12735]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.213.49.60
Dec  7 10:09:29 vps691689 sshd[12735]: Failed password for invalid user rpm from 188.213.49.60 port 47230 ssh2
Dec  7 10:17:07 vps691689 sshd[12967]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.213.49.60
...
2019-12-07 17:27:43
163.172.7.215 attackspam
163.172.7.215 was recorded 15 times by 15 hosts attempting to connect to the following ports: 5060. Incident counter (4h, 24h, all-time): 15, 15, 36
2019-12-07 17:37:22
118.25.189.123 attackspam
Dec  7 09:51:41 tuxlinux sshd[43811]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.25.189.123  user=root
Dec  7 09:51:43 tuxlinux sshd[43811]: Failed password for root from 118.25.189.123 port 55284 ssh2
Dec  7 09:51:41 tuxlinux sshd[43811]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.25.189.123  user=root
Dec  7 09:51:43 tuxlinux sshd[43811]: Failed password for root from 118.25.189.123 port 55284 ssh2
Dec  7 10:04:35 tuxlinux sshd[44034]: Invalid user refat from 118.25.189.123 port 40312
...
2019-12-07 18:01:17
144.91.113.246 attackbotsspam
Lines containing failures of 144.91.113.246
auth.log:Dec  4 20:13:50 omfg sshd[12160]: Connection from 144.91.113.246 port 40952 on 78.46.60.41 port 22
auth.log:Dec  4 20:13:50 omfg sshd[12160]: Did not receive identification string from 144.91.113.246
auth.log:Dec  4 20:13:50 omfg sshd[12161]: Connection from 144.91.113.246 port 40056 on 78.46.60.53 port 22
auth.log:Dec  4 20:13:50 omfg sshd[12161]: Did not receive identification string from 144.91.113.246
auth.log:Dec  4 20:13:50 omfg sshd[12164]: Connection from 144.91.113.246 port 36410 on 78.46.60.16 port 22
auth.log:Dec  4 20:13:50 omfg sshd[12164]: Did not receive identification string from 144.91.113.246
auth.log:Dec  4 20:13:50 omfg sshd[12162]: Connection from 144.91.113.246 port 58736 on 78.46.60.40 port 22
auth.log:Dec  4 20:13:50 omfg sshd[12162]: Did not receive identification string from 144.91.113.246
auth.log:Dec  4 20:13:50 omfg sshd[12163]: Connection from 144.91.113.246 port 48244 on 78.46.60.42 port ........
------------------------------
2019-12-07 18:04:21
106.13.214.108 attackspambots
$f2bV_matches
2019-12-07 17:58:16
51.91.108.124 attackspam
Dec  7 11:48:28 server sshd\[9164\]: Invalid user info from 51.91.108.124
Dec  7 11:48:28 server sshd\[9164\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.ip-51-91-108.eu 
Dec  7 11:48:30 server sshd\[9164\]: Failed password for invalid user info from 51.91.108.124 port 52226 ssh2
Dec  7 11:54:19 server sshd\[10552\]: Invalid user ubnt from 51.91.108.124
Dec  7 11:54:19 server sshd\[10552\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.ip-51-91-108.eu 
...
2019-12-07 17:56:08

Recently Reported IPs

233.53.230.98 186.104.42.215 158.52.190.28 172.85.99.74
127.26.218.232 10.193.34.104 255.88.154.206 152.36.191.207
0.51.135.177 236.24.190.110 155.210.108.173 235.68.2.195
14.206.26.232 117.34.154.203 118.21.233.176 197.158.230.103
185.63.250.174 177.221.9.60 161.35.119.201 250.162.26.11