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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 14.207.139.56
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 60114
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;14.207.139.56.			IN	A

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

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

Non-authoritative answer:
56.139.207.14.in-addr.arpa	name = mx-ll-14.207.139-56.dynamic.3bb.in.th.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
64.20.48.178 attack
Jul 27 20:50:13 server6 sshd[11423]: reveeclipse mapping checking getaddrinfo for server.newssellprod.club [64.20.48.178] failed - POSSIBLE BREAK-IN ATTEMPT!
Jul 27 20:50:13 server6 sshd[11423]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.20.48.178  user=r.r
Jul 27 20:50:15 server6 sshd[11423]: Failed password for r.r from 64.20.48.178 port 49388 ssh2
Jul 27 20:50:15 server6 sshd[11423]: Received disconnect from 64.20.48.178: 11: Bye Bye [preauth]
Jul 27 21:01:45 server6 sshd[25303]: reveeclipse mapping checking getaddrinfo for server.newssellprod.club [64.20.48.178] failed - POSSIBLE BREAK-IN ATTEMPT!
Jul 27 21:01:45 server6 sshd[25303]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.20.48.178  user=r.r
Jul 27 21:01:47 server6 sshd[25303]: Failed password for r.r from 64.20.48.178 port 32920 ssh2
Jul 27 21:01:47 server6 sshd[25303]: Received disconnect from 64.20.48.178: 11: Bye ........
-------------------------------
2019-07-28 16:10:24
176.58.124.134 attack
Port scan and direct access per IP instead of hostname
2019-07-28 15:44:05
93.114.82.239 attack
Jul 28 09:00:59 mout sshd[8786]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=93.114.82.239  user=root
Jul 28 09:01:01 mout sshd[8786]: Failed password for root from 93.114.82.239 port 57726 ssh2
2019-07-28 16:30:40
210.115.225.166 attackbotsspam
Jul 28 09:28:58 vibhu-HP-Z238-Microtower-Workstation sshd\[11101\]: Invalid user chapter from 210.115.225.166
Jul 28 09:28:58 vibhu-HP-Z238-Microtower-Workstation sshd\[11101\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.115.225.166
Jul 28 09:29:01 vibhu-HP-Z238-Microtower-Workstation sshd\[11101\]: Failed password for invalid user chapter from 210.115.225.166 port 38282 ssh2
Jul 28 09:34:30 vibhu-HP-Z238-Microtower-Workstation sshd\[11235\]: Invalid user saibaba from 210.115.225.166
Jul 28 09:34:30 vibhu-HP-Z238-Microtower-Workstation sshd\[11235\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.115.225.166
...
2019-07-28 16:00:25
92.91.60.249 attackbotsspam
Jul 28 06:24:55 debian sshd\[16260\]: Invalid user lke from 92.91.60.249 port 57282
Jul 28 06:24:55 debian sshd\[16260\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.91.60.249
...
2019-07-28 16:28:43
60.48.64.167 attack
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=60.48.64.167  user=root
Failed password for root from 60.48.64.167 port 37186 ssh2
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=60.48.64.167  user=root
Failed password for root from 60.48.64.167 port 48264 ssh2
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=60.48.64.167  user=root
2019-07-28 16:13:51
139.162.146.15 attackbots
GET /api/v1/pods HTTP/1.1
2019-07-28 16:15:52
132.232.168.65 attackbotsspam
POST /App.php?_=156264152c7b0 HTTP/1.1
2019-07-28 16:32:50
23.129.64.204 attackspambots
Jul 28 04:41:38 vpn01 sshd\[11319\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=23.129.64.204  user=root
Jul 28 04:41:40 vpn01 sshd\[11319\]: Failed password for root from 23.129.64.204 port 57114 ssh2
Jul 28 04:41:49 vpn01 sshd\[11319\]: Failed password for root from 23.129.64.204 port 57114 ssh2
2019-07-28 15:38:49
134.73.129.232 attackbots
Jul 28 02:07:37 mail sshd\[32448\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.73.129.232  user=root
Jul 28 02:07:39 mail sshd\[32448\]: Failed password for root from 134.73.129.232 port 52248 ssh2
...
2019-07-28 15:58:59
203.153.46.89 attackspambots
Jul 28 04:38:42 host sshd\[50838\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.153.46.89  user=root
Jul 28 04:38:44 host sshd\[50838\]: Failed password for root from 203.153.46.89 port 57406 ssh2
...
2019-07-28 15:45:15
180.159.0.182 attackspam
28.07.2019 01:07:25 SSH access blocked by firewall
2019-07-28 16:08:13
141.105.102.155 attackbots
Port scan and direct access per IP instead of hostname
2019-07-28 16:12:49
95.32.44.96 attack
port scan and connect, tcp 23 (telnet)
2019-07-28 15:28:19
139.59.34.17 attackbotsspam
Jul 28 07:23:34 XXX sshd[7269]: Invalid user applmgr from 139.59.34.17 port 41486
2019-07-28 16:22:49

Recently Reported IPs

14.207.139.75 14.207.14.155 14.207.14.167 14.207.14.165
14.207.14.170 14.207.144.199 14.207.144.22 14.207.144.20
14.207.144.177 14.207.144.172 14.207.144.193 14.207.144.196
14.207.144.168 14.207.144.179 14.207.144.184 14.207.144.208
14.207.144.160 14.207.144.232 14.207.144.251 14.207.144.53