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

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

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

;; Query time: 100 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat May 30 06:37:04 CST 2020
;; MSG SIZE  rcvd: 117
Host info
Host 41.249.140.12.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 41.249.140.12.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
189.112.109.189 attackspam
$f2bV_matches
2020-02-18 03:21:42
213.206.227.150 spam
Used many times per day for SPAM, PHISHING, SCAM and/or SEXE on STOLLEN list we don't know where without our agreement, as usual with LIERS and ROBERS !
2020-02-18 03:46:34
163.172.53.162 attackspam
Unauthorized connection attempt detected from IP address 163.172.53.162 to port 139
2020-02-18 03:37:05
218.92.0.171 attack
Feb 17 16:14:47 firewall sshd[15248]: Failed password for root from 218.92.0.171 port 37372 ssh2
Feb 17 16:14:51 firewall sshd[15248]: Failed password for root from 218.92.0.171 port 37372 ssh2
Feb 17 16:14:54 firewall sshd[15248]: Failed password for root from 218.92.0.171 port 37372 ssh2
...
2020-02-18 03:18:20
113.23.43.77 attackbotsspam
20/2/17@08:34:34: FAIL: Alarm-Network address from=113.23.43.77
...
2020-02-18 03:24:46
85.119.8.201 attackspam
20/2/17@11:58:10: FAIL: Alarm-Network address from=85.119.8.201
20/2/17@11:58:10: FAIL: Alarm-Network address from=85.119.8.201
...
2020-02-18 03:14:08
111.250.27.205 attack
SMB Server BruteForce Attack
2020-02-18 03:34:12
203.92.33.29 attackbots
Feb 17 15:12:30 powerpi2 sshd[30043]: Failed password for invalid user cxh from 203.92.33.29 port 6453 ssh2
Feb 17 15:20:58 powerpi2 sshd[30458]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.92.33.29  user=root
Feb 17 15:21:00 powerpi2 sshd[30458]: Failed password for root from 203.92.33.29 port 23408 ssh2
...
2020-02-18 03:41:15
89.217.10.19 attackspam
Feb 17 18:11:46 sticky sshd\[3688\]: Invalid user wwl from 89.217.10.19 port 35826
Feb 17 18:11:46 sticky sshd\[3688\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.217.10.19
Feb 17 18:11:48 sticky sshd\[3688\]: Failed password for invalid user wwl from 89.217.10.19 port 35826 ssh2
Feb 17 18:20:32 sticky sshd\[3753\]: Invalid user z from 89.217.10.19 port 53494
Feb 17 18:20:32 sticky sshd\[3753\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.217.10.19
...
2020-02-18 03:33:21
183.129.141.30 attack
(sshd) Failed SSH login from 183.129.141.30 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Feb 17 19:21:59 elude sshd[8079]: Invalid user jayant from 183.129.141.30 port 52124
Feb 17 19:22:00 elude sshd[8079]: Failed password for invalid user jayant from 183.129.141.30 port 52124 ssh2
Feb 17 19:31:47 elude sshd[8611]: Invalid user amdsa from 183.129.141.30 port 50126
Feb 17 19:31:49 elude sshd[8611]: Failed password for invalid user amdsa from 183.129.141.30 port 50126 ssh2
Feb 17 19:34:47 elude sshd[8817]: Invalid user celery from 183.129.141.30 port 48420
2020-02-18 03:13:06
195.117.101.79 attack
SSH authentication failure x 6 reported by Fail2Ban
...
2020-02-18 03:43:16
49.147.160.172 attackspam
1581946467 - 02/17/2020 14:34:27 Host: 49.147.160.172/49.147.160.172 Port: 445 TCP Blocked
2020-02-18 03:32:24
222.186.173.238 attackbots
2020-02-17T19:26:18.997343abusebot-2.cloudsearch.cf sshd[7621]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.238  user=root
2020-02-17T19:26:20.514519abusebot-2.cloudsearch.cf sshd[7621]: Failed password for root from 222.186.173.238 port 14498 ssh2
2020-02-17T19:26:24.025651abusebot-2.cloudsearch.cf sshd[7621]: Failed password for root from 222.186.173.238 port 14498 ssh2
2020-02-17T19:26:18.997343abusebot-2.cloudsearch.cf sshd[7621]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.238  user=root
2020-02-17T19:26:20.514519abusebot-2.cloudsearch.cf sshd[7621]: Failed password for root from 222.186.173.238 port 14498 ssh2
2020-02-17T19:26:24.025651abusebot-2.cloudsearch.cf sshd[7621]: Failed password for root from 222.186.173.238 port 14498 ssh2
2020-02-17T19:26:18.997343abusebot-2.cloudsearch.cf sshd[7621]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh
...
2020-02-18 03:40:36
77.43.74.58 attackspam
Feb 17 17:46:29  sshd\[23410\]: Invalid user www from 77.43.74.58Feb 17 17:46:31  sshd\[23410\]: Failed password for invalid user www from 77.43.74.58 port 51604 ssh2
...
2020-02-18 03:31:07
88.247.170.218 attackspambots
Automatic report - Port Scan Attack
2020-02-18 03:30:40

Recently Reported IPs

154.250.137.25 116.43.227.70 50.89.177.122 174.242.69.59
32.230.177.67 183.207.242.130 46.147.44.50 76.91.101.137
123.19.28.30 101.160.233.192 208.191.163.24 1.145.170.110
210.54.82.3 180.76.186.145 207.255.157.239 175.206.30.98
98.76.244.200 94.238.121.98 105.138.23.161 46.87.96.10