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: AT&T

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

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

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

;; Query time: 53 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jan 03 04:29:27 CST 2020
;; MSG SIZE  rcvd: 117
Host info
52.242.140.12.in-addr.arpa domain name pointer 52.wl242.tscn.attga31ur.dsl.att.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
52.242.140.12.in-addr.arpa	name = 52.wl242.tscn.attga31ur.dsl.att.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
54.37.68.33 attack
k+ssh-bruteforce
2020-07-06 22:58:03
180.140.108.241 attackbots
Unauthorised access (Jul  6) SRC=180.140.108.241 LEN=40 TTL=50 ID=3878 TCP DPT=23 WINDOW=1060 SYN
2020-07-06 22:49:16
193.169.252.21 attack
 UDP 193.169.252.21:33331 -> port 6881, len 119
2020-07-06 23:07:24
45.9.47.66 attack
45.9.47.66 - - [06/Jul/2020:15:14:24 +0100] "POST /wp-login.php HTTP/1.1" 200 5618 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)"
45.9.47.66 - - [06/Jul/2020:15:24:51 +0100] "POST /xmlrpc.php HTTP/1.1" 403 219 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)"
45.9.47.66 - - [06/Jul/2020:15:24:51 +0100] "POST /wp-login.php HTTP/1.1" 200 5611 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)"
...
2020-07-06 22:44:18
122.228.19.79 attack
Mon Jul  6 16:31:43 2020 122.228.19.79:5255 TLS Error: TLS handshake failed
2020-07-06 22:33:23
45.55.233.213 attackbotsspam
Jul  6 06:31:32 mockhub sshd[23647]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.233.213
Jul  6 06:31:35 mockhub sshd[23647]: Failed password for invalid user prem from 45.55.233.213 port 57692 ssh2
...
2020-07-06 22:36:16
171.67.71.100 attack
scans 6 times in preceeding hours on the ports (in chronological order) 27394 27394 33333 43225 58699 62234
2020-07-06 23:12:38
222.186.30.57 attackspam
Unauthorized connection attempt detected from IP address 222.186.30.57 to port 22
2020-07-06 22:53:14
113.172.127.154 attackspambots
SSH brute-force attempt
2020-07-06 23:00:31
193.186.15.35 attack
Jul  6 14:10:59 rush sshd[20577]: Failed password for root from 193.186.15.35 port 38259 ssh2
Jul  6 14:14:15 rush sshd[20634]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.186.15.35
Jul  6 14:14:17 rush sshd[20634]: Failed password for invalid user tobias from 193.186.15.35 port 35983 ssh2
...
2020-07-06 22:35:42
188.166.233.216 attackspam
WordPress login Brute force / Web App Attack on client site.
2020-07-06 22:58:28
1.246.222.9 attackspambots
Automatic report - Port Scan Attack
2020-07-06 22:39:46
94.102.51.28 attack
 TCP (SYN) 94.102.51.28:41291 -> port 72, len 44
2020-07-06 22:54:17
209.126.127.163 attackspambots
Unauthorized connection attempt detected from IP address 209.126.127.163 to port 2375
2020-07-06 23:06:00
202.152.1.89 attackspam
 TCP (SYN) 202.152.1.89:41995 -> port 2541, len 44
2020-07-06 23:06:54

Recently Reported IPs

64.61.108.181 5.84.125.248 110.80.221.242 173.254.223.52
212.142.199.99 47.156.164.26 182.8.15.76 67.253.54.121
42.179.18.104 86.182.17.184 126.195.217.127 178.81.143.19
119.18.197.48 97.129.34.173 125.27.255.94 118.108.216.216
209.104.238.72 104.4.111.71 186.162.101.253 42.6.130.28