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

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.138.99 attackbotsspam
Honeypot attack, port: 445, PTR: mx-ll-14.207.138-99.dynamic.3bb.in.th.
2020-02-08 17:49:59
14.207.13.222 attackspam
2019-11-01T04:50:14.6823061240 sshd\[27897\]: Invalid user ubnt from 14.207.13.222 port 60391
2019-11-01T04:50:14.8890651240 sshd\[27897\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.207.13.222
2019-11-01T04:50:16.4920951240 sshd\[27897\]: Failed password for invalid user ubnt from 14.207.13.222 port 60391 ssh2
...
2019-11-01 17:39:49
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
14.207.136.9 attack
wordpress exploit scan
...
2019-07-15 14:54:34
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 14.207.13.217
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 39322
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;14.207.13.217.			IN	A

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

;; Query time: 63 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 13:21:38 CST 2022
;; MSG SIZE  rcvd: 106
Host info
217.13.207.14.in-addr.arpa domain name pointer mx-ll-14.207.13-217.dynamic.3bb.in.th.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
217.13.207.14.in-addr.arpa	name = mx-ll-14.207.13-217.dynamic.3bb.in.th.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
139.199.29.155 attack
Oct 16 09:59:46 pkdns2 sshd\[13355\]: Invalid user demo from 139.199.29.155Oct 16 09:59:48 pkdns2 sshd\[13355\]: Failed password for invalid user demo from 139.199.29.155 port 16998 ssh2Oct 16 10:04:31 pkdns2 sshd\[13594\]: Invalid user oracle from 139.199.29.155Oct 16 10:04:33 pkdns2 sshd\[13594\]: Failed password for invalid user oracle from 139.199.29.155 port 51324 ssh2Oct 16 10:09:01 pkdns2 sshd\[13777\]: Invalid user lm from 139.199.29.155Oct 16 10:09:03 pkdns2 sshd\[13777\]: Failed password for invalid user lm from 139.199.29.155 port 29135 ssh2
...
2019-10-16 15:52:49
189.109.247.149 attackspambots
SSH Bruteforce attempt
2019-10-16 16:03:39
211.195.12.33 attackspambots
Oct 16 10:23:45 server sshd\[1794\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.195.12.33  user=root
Oct 16 10:23:47 server sshd\[1794\]: Failed password for root from 211.195.12.33 port 37603 ssh2
Oct 16 10:42:07 server sshd\[8683\]: Invalid user stupid from 211.195.12.33
Oct 16 10:42:07 server sshd\[8683\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.195.12.33 
Oct 16 10:42:09 server sshd\[8683\]: Failed password for invalid user stupid from 211.195.12.33 port 37472 ssh2
...
2019-10-16 16:00:58
111.230.247.243 attack
Triggered by Fail2Ban at Vostok web server
2019-10-16 15:59:13
69.194.8.237 attackspambots
Oct 16 05:00:06 mail sshd[24216]: Invalid user pakistan from 69.194.8.237
Oct 16 05:00:06 mail sshd[24216]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.194.8.237
Oct 16 05:00:06 mail sshd[24216]: Invalid user pakistan from 69.194.8.237
Oct 16 05:00:08 mail sshd[24216]: Failed password for invalid user pakistan from 69.194.8.237 port 40536 ssh2
Oct 16 05:26:38 mail sshd[27709]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.194.8.237  user=backup
Oct 16 05:26:40 mail sshd[27709]: Failed password for backup from 69.194.8.237 port 52458 ssh2
...
2019-10-16 15:29:41
45.140.168.154 attack
Automatic report - Port Scan Attack
2019-10-16 15:31:16
190.177.92.135 attackbotsspam
Oct 16 05:08:44 mxgate1 postfix/postscreen[16446]: CONNECT from [190.177.92.135]:40610 to [176.31.12.44]:25
Oct 16 05:08:44 mxgate1 postfix/dnsblog[16451]: addr 190.177.92.135 listed by domain cbl.abuseat.org as 127.0.0.2
Oct 16 05:08:44 mxgate1 postfix/dnsblog[16449]: addr 190.177.92.135 listed by domain zen.spamhaus.org as 127.0.0.11
Oct 16 05:08:44 mxgate1 postfix/dnsblog[16449]: addr 190.177.92.135 listed by domain zen.spamhaus.org as 127.0.0.4
Oct 16 05:08:44 mxgate1 postfix/dnsblog[16448]: addr 190.177.92.135 listed by domain bl.spamcop.net as 127.0.0.2
Oct 16 05:08:44 mxgate1 postfix/dnsblog[16447]: addr 190.177.92.135 listed by domain b.barracudacentral.org as 127.0.0.2
Oct 16 05:08:50 mxgate1 postfix/postscreen[16446]: DNSBL rank 5 for [190.177.92.135]:40610
Oct x@x
Oct 16 05:08:52 mxgate1 postfix/postscreen[16446]: HANGUP after 2.2 from [190.177.92.135]:40610 in tests after SMTP handshake
Oct 16 05:08:52 mxgate1 postfix/postscreen[16446]: DISCONNECT [190.177.9........
-------------------------------
2019-10-16 15:40:58
59.13.139.50 attackspambots
Oct 16 07:08:13 icinga sshd[27574]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.13.139.50 
Oct 16 07:08:15 icinga sshd[27574]: Failed password for invalid user hp from 59.13.139.50 port 57092 ssh2
Oct 16 07:43:59 icinga sshd[51129]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.13.139.50 
...
2019-10-16 15:42:51
36.90.254.32 attackspam
Automatic report - SSH Brute-Force Attack
2019-10-16 15:39:59
54.37.66.73 attack
Oct 16 06:47:00 lnxweb62 sshd[2532]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.66.73
2019-10-16 15:35:28
182.139.134.107 attack
Oct 16 08:51:20 vpn01 sshd[1330]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.139.134.107
Oct 16 08:51:22 vpn01 sshd[1330]: Failed password for invalid user s3guridad from 182.139.134.107 port 56446 ssh2
...
2019-10-16 15:52:00
222.186.169.194 attackspambots
Oct 16 10:01:40 tux-35-217 sshd\[11229\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.169.194  user=root
Oct 16 10:01:42 tux-35-217 sshd\[11229\]: Failed password for root from 222.186.169.194 port 24634 ssh2
Oct 16 10:01:46 tux-35-217 sshd\[11229\]: Failed password for root from 222.186.169.194 port 24634 ssh2
Oct 16 10:01:50 tux-35-217 sshd\[11229\]: Failed password for root from 222.186.169.194 port 24634 ssh2
...
2019-10-16 16:04:41
103.39.216.153 attack
Oct 16 07:25:14 eventyay sshd[13976]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.39.216.153
Oct 16 07:25:15 eventyay sshd[13976]: Failed password for invalid user mongo123 from 103.39.216.153 port 43044 ssh2
Oct 16 07:30:21 eventyay sshd[14067]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.39.216.153
...
2019-10-16 16:07:45
62.173.154.12 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-10-16 15:32:05
111.231.63.14 attack
Oct 16 03:41:28 plusreed sshd[7449]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.231.63.14  user=root
Oct 16 03:41:30 plusreed sshd[7449]: Failed password for root from 111.231.63.14 port 38198 ssh2
...
2019-10-16 15:56:44

Recently Reported IPs

14.207.13.210 14.207.13.208 14.207.13.202 14.207.13.204
14.207.13.221 14.207.13.219 99.65.189.15 14.207.13.215
14.207.13.228 14.207.13.237 14.207.13.244 14.207.13.233
14.207.13.249 14.207.13.49 14.207.13.56 14.207.13.36
14.207.13.52 14.207.13.240 14.207.13.29 14.207.13.246