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

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

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

;; Query time: 40 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jul 12 18:20:58 CST 2020
;; MSG SIZE  rcvd: 117
Host info
Host 163.66.139.52.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 163.66.139.52.in-addr.arpa: NXDOMAIN

Related IP info:
Related comments:
IP Type Details Datetime
60.19.64.10 attackspambots
Dec 27 17:56:22 web1 postfix/smtpd[18931]: warning: unknown[60.19.64.10]: SASL LOGIN authentication failed: authentication failure
...
2019-12-28 07:28:10
222.186.173.238 attackspambots
19/12/27@17:57:03: FAIL: Alarm-SSH address from=222.186.173.238
...
2019-12-28 07:01:53
209.13.179.82 attackspambots
Fail2Ban Ban Triggered
2019-12-28 06:51:28
103.52.135.48 attackbotsspam
SIP/5060 Probe, BF, Hack -
2019-12-28 06:53:54
111.229.175.115 attackbots
$f2bV_matches
2019-12-28 07:01:08
165.22.240.63 attackbots
165.22.240.63 - - \[27/Dec/2019:23:56:16 +0100\] "POST /wp-login.php HTTP/1.0" 200 4128 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
165.22.240.63 - - \[27/Dec/2019:23:56:18 +0100\] "POST /wp-login.php HTTP/1.0" 200 3955 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
165.22.240.63 - - \[27/Dec/2019:23:56:23 +0100\] "POST /xmlrpc.php HTTP/1.0" 200 736 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-12-28 07:27:28
46.38.144.17 attack
Brute force SMTP login attempts.
2019-12-28 07:12:15
3.16.164.153 attackspambots
3.16.164.153 - - [27/Dec/2019:22:55:51 +0000] "POST /wp-login.php HTTP/1.1" 200 6393 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
3.16.164.153 - - [27/Dec/2019:22:56:24 +0000] "POST /wp-login.php HTTP/1.1" 200 6256 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2019-12-28 07:27:04
45.125.66.69 attackbotsspam
2019-12-27 dovecot_login authenticator failed for \(User\) \[45.125.66.69\]: 535 Incorrect authentication data \(set_id=qwerty1\)
2019-12-27 dovecot_login authenticator failed for \(User\) \[45.125.66.69\]: 535 Incorrect authentication data \(set_id=garbage\)
2019-12-27 dovecot_login authenticator failed for \(User\) \[45.125.66.69\]: 535 Incorrect authentication data \(set_id=load\)
2019-12-28 07:29:18
200.56.60.44 attackbotsspam
Dec 27 23:12:42 localhost sshd\[114729\]: Invalid user hung from 200.56.60.44 port 18814
Dec 27 23:12:42 localhost sshd\[114729\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.56.60.44
Dec 27 23:12:45 localhost sshd\[114729\]: Failed password for invalid user hung from 200.56.60.44 port 18814 ssh2
Dec 27 23:16:28 localhost sshd\[114829\]: Invalid user motashaw from 200.56.60.44 port 43285
Dec 27 23:16:28 localhost sshd\[114829\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.56.60.44
...
2019-12-28 07:25:48
190.61.43.133 attack
Honeypot attack, port: 23, PTR: host-190-61-43-133.ufinet.com.co.
2019-12-28 06:55:47
93.148.209.74 attackbotsspam
Invalid user baldick from 93.148.209.74 port 35214
2019-12-28 07:11:57
104.255.169.139 attackspambots
12/27/2019-17:56:45.586835 104.255.169.139 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-12-28 07:14:49
163.172.36.146 attack
2019-12-27T22:53:42.250837shield sshd\[26583\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=163.172.36.146  user=root
2019-12-27T22:53:43.589287shield sshd\[26583\]: Failed password for root from 163.172.36.146 port 46604 ssh2
2019-12-27T22:56:38.014116shield sshd\[27193\]: Invalid user inuzuka from 163.172.36.146 port 36440
2019-12-27T22:56:38.019769shield sshd\[27193\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=163.172.36.146
2019-12-27T22:56:40.186589shield sshd\[27193\]: Failed password for invalid user inuzuka from 163.172.36.146 port 36440 ssh2
2019-12-28 07:18:31
81.145.158.178 attack
Dec 27 22:57:02 IngegnereFirenze sshd[19998]: Failed password for invalid user ftp from 81.145.158.178 port 46213 ssh2
...
2019-12-28 07:04:57

Recently Reported IPs

186.77.49.101 236.0.155.6 2.128.199.17 120.235.163.82
94.74.135.142 186.95.158.98 121.239.20.191 27.102.113.165
190.13.6.220 182.52.192.107 185.225.28.114 151.233.97.79
31.42.91.131 37.98.75.217 51.158.65.243 209.203.148.242
202.208.109.75 35.62.6.159 195.82.189.53 13.65.240.44