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

;; QUESTION SECTION:
;66.104.134.214.			IN	A

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

;; Query time: 40 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 23 01:39:24 CST 2025
;; MSG SIZE  rcvd: 107
Host info
214.134.104.66.in-addr.arpa domain name pointer ip66-104-134-214.z134-104-66.customer.algx.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
214.134.104.66.in-addr.arpa	name = ip66-104-134-214.z134-104-66.customer.algx.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
106.13.44.85 attack
sshd jail - ssh hack attempt
2019-11-25 09:12:55
190.129.49.62 attackspam
Nov 25 03:32:21 server sshd\[19190\]: Invalid user rosli from 190.129.49.62
Nov 25 03:32:21 server sshd\[19190\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.129.49.62 
Nov 25 03:32:23 server sshd\[19190\]: Failed password for invalid user rosli from 190.129.49.62 port 55020 ssh2
Nov 25 03:43:52 server sshd\[21910\]: Invalid user chopot from 190.129.49.62
Nov 25 03:43:52 server sshd\[21910\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.129.49.62 
...
2019-11-25 09:16:09
104.236.33.155 attackbots
Nov 24 19:41:44 XXX sshd[37224]: Invalid user constance from 104.236.33.155 port 48474
2019-11-25 08:57:22
92.53.90.84 attackbots
Connection by 92.53.90.84 on port: 15000 got caught by honeypot at 11/24/2019 11:49:18 PM
2019-11-25 08:57:09
212.119.45.12 attackbots
Fail2Ban Ban Triggered
HTTP Attempted Bot Registration
2019-11-25 08:49:15
106.12.102.178 attackbots
106.12.102.178 was recorded 23 times by 15 hosts attempting to connect to the following ports: 4243,2377,2375,2376. Incident counter (4h, 24h, all-time): 23, 138, 221
2019-11-25 09:15:40
222.186.190.92 attackspambots
Nov 25 01:29:34 srv206 sshd[4962]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.190.92  user=root
Nov 25 01:29:36 srv206 sshd[4962]: Failed password for root from 222.186.190.92 port 40580 ssh2
...
2019-11-25 08:46:09
58.8.194.188 attackbots
19/11/24@17:55:35: FAIL: IoT-Telnet address from=58.8.194.188
...
2019-11-25 09:12:41
123.144.23.251 attackspambots
1574636145 - 11/24/2019 23:55:45 Host: 123.144.23.251/123.144.23.251 Port: 6001 TCP Blocked
2019-11-25 09:07:37
34.95.212.142 attackspam
34.95.212.142 was recorded 5 times by 1 hosts attempting to connect to the following ports: 23. Incident counter (4h, 24h, all-time): 5, 5, 5
2019-11-25 09:10:44
201.238.239.151 attackbotsspam
Nov 24 14:52:24 web1 sshd\[21022\]: Invalid user morgan from 201.238.239.151
Nov 24 14:52:24 web1 sshd\[21022\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.238.239.151
Nov 24 14:52:27 web1 sshd\[21022\]: Failed password for invalid user morgan from 201.238.239.151 port 38565 ssh2
Nov 24 14:56:53 web1 sshd\[21421\]: Invalid user dovecot from 201.238.239.151
Nov 24 14:56:53 web1 sshd\[21421\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.238.239.151
2019-11-25 09:14:55
46.219.3.144 attackbotsspam
2019-11-25T00:58:37.820518  sshd[19686]: Invalid user poor from 46.219.3.144 port 54314
2019-11-25T00:58:37.835197  sshd[19686]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.219.3.144
2019-11-25T00:58:37.820518  sshd[19686]: Invalid user poor from 46.219.3.144 port 54314
2019-11-25T00:58:39.452703  sshd[19686]: Failed password for invalid user poor from 46.219.3.144 port 54314 ssh2
2019-11-25T01:04:50.559610  sshd[19817]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.219.3.144  user=root
2019-11-25T01:04:52.718923  sshd[19817]: Failed password for root from 46.219.3.144 port 33818 ssh2
...
2019-11-25 08:57:43
13.251.171.10 attackspambots
RDP Bruteforce
2019-11-25 08:48:46
151.80.254.73 attackspambots
Nov 25 00:08:59 srv01 sshd[28177]: Invalid user test from 151.80.254.73 port 58800
Nov 25 00:08:59 srv01 sshd[28177]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=151.80.254.73
Nov 25 00:08:59 srv01 sshd[28177]: Invalid user test from 151.80.254.73 port 58800
Nov 25 00:09:01 srv01 sshd[28177]: Failed password for invalid user test from 151.80.254.73 port 58800 ssh2
Nov 25 00:15:39 srv01 sshd[28770]: Invalid user ci from 151.80.254.73 port 38462
...
2019-11-25 09:00:16
61.153.213.210 attackbotsspam
11/24/2019-17:55:47.580503 61.153.213.210 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-11-25 09:07:05

Recently Reported IPs

199.244.154.252 101.128.4.204 148.121.126.130 82.97.249.115
190.124.106.174 100.82.221.253 224.92.60.178 228.216.179.52
122.110.32.97 159.43.156.192 221.125.52.29 240.250.101.101
106.201.205.208 76.145.150.221 134.160.144.89 130.232.21.131
63.183.217.202 52.117.80.231 28.87.153.160 44.92.216.30