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: None

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:
IP Type Details Datetime
14.207.137.59 attackspambots
Attempt to attack host OS, exploiting network vulnerabilities, on 21-10-2019 04:50:18.
2019-10-21 15:44:17
14.207.137.221 attackspambots
Sat, 20 Jul 2019 21:54:11 +0000 likely compromised host or open proxy. ddos rate spidering
2019-07-21 14:03:04
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 14.207.137.49
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 27518
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;14.207.137.49.			IN	A

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

;; Query time: 65 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 13:22:09 CST 2022
;; MSG SIZE  rcvd: 106
Host info
49.137.207.14.in-addr.arpa domain name pointer mx-ll-14.207.137-49.dynamic.3bb.in.th.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
49.137.207.14.in-addr.arpa	name = mx-ll-14.207.137-49.dynamic.3bb.in.th.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
112.98.104.30 attackbots
Unauthorised access (Aug 23) SRC=112.98.104.30 LEN=44 TTL=239 ID=52991 TCP DPT=1433 WINDOW=1024 SYN
2020-08-23 14:46:16
159.65.181.225 attackbots
Aug 22 19:27:58 php1 sshd\[19175\]: Invalid user ts3 from 159.65.181.225
Aug 22 19:27:58 php1 sshd\[19175\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.181.225
Aug 22 19:28:00 php1 sshd\[19175\]: Failed password for invalid user ts3 from 159.65.181.225 port 35148 ssh2
Aug 22 19:31:40 php1 sshd\[19572\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.181.225  user=root
Aug 22 19:31:43 php1 sshd\[19572\]: Failed password for root from 159.65.181.225 port 42454 ssh2
2020-08-23 14:29:11
58.222.133.82 attack
Aug 23 08:00:18 h1745522 sshd[13557]: Invalid user ftp from 58.222.133.82 port 45864
Aug 23 08:00:18 h1745522 sshd[13557]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.222.133.82
Aug 23 08:00:18 h1745522 sshd[13557]: Invalid user ftp from 58.222.133.82 port 45864
Aug 23 08:00:20 h1745522 sshd[13557]: Failed password for invalid user ftp from 58.222.133.82 port 45864 ssh2
Aug 23 08:04:06 h1745522 sshd[14195]: Invalid user ec from 58.222.133.82 port 60326
Aug 23 08:04:06 h1745522 sshd[14195]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.222.133.82
Aug 23 08:04:06 h1745522 sshd[14195]: Invalid user ec from 58.222.133.82 port 60326
Aug 23 08:04:08 h1745522 sshd[14195]: Failed password for invalid user ec from 58.222.133.82 port 60326 ssh2
Aug 23 08:08:29 h1745522 sshd[14465]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.222.133.82  user=root
Aug 23 08:08
...
2020-08-23 14:17:20
125.72.106.95 attack
Lines containing failures of 125.72.106.95
Aug 23 07:02:54 nemesis sshd[30178]: Invalid user ht from 125.72.106.95 port 56347
Aug 23 07:02:55 nemesis sshd[30178]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.72.106.95 
Aug 23 07:02:57 nemesis sshd[30178]: Failed password for invalid user ht from 125.72.106.95 port 56347 ssh2
Aug 23 07:02:57 nemesis sshd[30178]: Received disconnect from 125.72.106.95 port 56347:11: Bye Bye [preauth]
Aug 23 07:02:57 nemesis sshd[30178]: Disconnected from invalid user ht 125.72.106.95 port 56347 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=125.72.106.95
2020-08-23 14:21:28
118.69.55.141 attackspambots
Invalid user jur from 118.69.55.141 port 51289
2020-08-23 14:29:38
106.12.97.46 attack
Aug 23 06:04:30 meumeu sshd[119090]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.97.46  user=root
Aug 23 06:04:32 meumeu sshd[119090]: Failed password for root from 106.12.97.46 port 44294 ssh2
Aug 23 06:06:50 meumeu sshd[119180]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.97.46  user=root
Aug 23 06:06:52 meumeu sshd[119180]: Failed password for root from 106.12.97.46 port 43028 ssh2
Aug 23 06:09:07 meumeu sshd[119334]: Invalid user sysadmin from 106.12.97.46 port 41778
Aug 23 06:09:07 meumeu sshd[119334]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.97.46 
Aug 23 06:09:07 meumeu sshd[119334]: Invalid user sysadmin from 106.12.97.46 port 41778
Aug 23 06:09:10 meumeu sshd[119334]: Failed password for invalid user sysadmin from 106.12.97.46 port 41778 ssh2
Aug 23 06:11:29 meumeu sshd[119484]: Invalid user superman from 106.12.97.46 port 40518
...
2020-08-23 14:34:52
166.62.100.99 attackspam
166.62.100.99 - - [23/Aug/2020:08:33:26 +0200] "GET /wp-login.php HTTP/1.1" 200 1689 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
166.62.100.99 - - [23/Aug/2020:08:33:27 +0200] "POST /wp-login.php HTTP/1.1" 200 1819 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
166.62.100.99 - - [23/Aug/2020:08:33:28 +0200] "GET /wp-login.php HTTP/1.1" 200 1689 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
166.62.100.99 - - [23/Aug/2020:08:33:29 +0200] "POST /wp-login.php HTTP/1.1" 200 1796 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
166.62.100.99 - - [23/Aug/2020:08:33:30 +0200] "GET /wp-login.php HTTP/1.1" 200 1689 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
166.62.100.99 - - [23/Aug/2020:08:33:30 +0200] "POST /wp-login.php HTTP/1.1" 200 1797 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Fir
...
2020-08-23 14:33:52
112.85.42.194 attackspam
Aug 23 05:59:24 jumpserver sshd[10371]: Failed password for root from 112.85.42.194 port 37709 ssh2
Aug 23 06:01:08 jumpserver sshd[10381]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.194  user=root
Aug 23 06:01:10 jumpserver sshd[10381]: Failed password for root from 112.85.42.194 port 29134 ssh2
...
2020-08-23 14:11:02
106.13.165.83 attack
Invalid user csserver from 106.13.165.83 port 43624
2020-08-23 14:44:26
122.51.10.222 attackspambots
Aug 23 07:53:39 marvibiene sshd[8108]: Failed password for root from 122.51.10.222 port 58042 ssh2
2020-08-23 14:45:52
154.0.161.99 attackbots
2020-08-23T05:06:53.968067shield sshd\[23479\]: Invalid user sonar from 154.0.161.99 port 40176
2020-08-23T05:06:53.974794shield sshd\[23479\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=baymonitoring.dedicated.co.za
2020-08-23T05:06:56.320714shield sshd\[23479\]: Failed password for invalid user sonar from 154.0.161.99 port 40176 ssh2
2020-08-23T05:12:21.981373shield sshd\[24869\]: Invalid user ralf from 154.0.161.99 port 49512
2020-08-23T05:12:22.020383shield sshd\[24869\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=baymonitoring.dedicated.co.za
2020-08-23 14:19:19
207.244.118.125 attack
(From eric@talkwithwebvisitor.com) Hey, this is Eric and I ran across drjenniferbrandon.com a few minutes ago.

Looks great… but now what?

By that I mean, when someone like me finds your website – either through Search or just bouncing around – what happens next?  Do you get a lot of leads from your site, or at least enough to make you happy?

Honestly, most business websites fall a bit short when it comes to generating paying customers. Studies show that 70% of a site’s visitors disappear and are gone forever after just a moment.

Here’s an idea…
 
How about making it really EASY for every visitor who shows up to get a personal phone call you as soon as they hit your site…
 
You can –
  
Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number.  It signals you the moment they let you know they’re interested – so that you can talk to that lead while they’re literally looking over your site.

CLICK HERE http://www
2020-08-23 14:42:03
101.36.178.48 attack
Invalid user gerencia from 101.36.178.48 port 54598
2020-08-23 14:20:26
142.93.66.165 attack
142.93.66.165 - - [23/Aug/2020:07:45:33 +0200] "GET /wp-login.php HTTP/1.1" 200 8691 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
142.93.66.165 - - [23/Aug/2020:07:45:36 +0200] "POST /wp-login.php HTTP/1.1" 200 8921 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
142.93.66.165 - - [23/Aug/2020:07:45:38 +0200] "POST /xmlrpc.php HTTP/1.1" 200 427 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2020-08-23 14:25:36
81.192.8.14 attackbots
Aug 23 06:20:51 rocket sshd[20529]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.192.8.14
Aug 23 06:20:53 rocket sshd[20529]: Failed password for invalid user tino from 81.192.8.14 port 44736 ssh2
Aug 23 06:24:55 rocket sshd[20849]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.192.8.14
...
2020-08-23 14:13:41

Recently Reported IPs

14.207.137.243 14.207.137.60 14.207.137.55 14.207.137.83
14.207.137.45 14.207.137.87 14.207.138.12 14.207.138.14
14.207.138.143 14.207.138.120 14.207.138.166 14.207.138.162
14.207.138.145 14.207.138.154 14.207.138.172 14.207.138.177
14.207.138.150 14.207.138.18 14.207.138.22 14.207.138.185