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

;; QUESTION SECTION:
;14.207.213.55.			IN	A

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

;; Query time: 64 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 13:30:59 CST 2022
;; MSG SIZE  rcvd: 106
Host info
55.213.207.14.in-addr.arpa domain name pointer mx-ll-14.207.213-55.dynamic.3bb.co.th.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
55.213.207.14.in-addr.arpa	name = mx-ll-14.207.213-55.dynamic.3bb.co.th.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
185.175.93.101 attackbots
11/02/2019-13:04:52.823509 185.175.93.101 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2019-11-03 01:18:53
149.202.55.18 attack
Nov  2 09:14:44 debian sshd\[22364\]: Invalid user gamasucc from 149.202.55.18 port 34470
Nov  2 09:14:44 debian sshd\[22364\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=149.202.55.18
Nov  2 09:14:46 debian sshd\[22364\]: Failed password for invalid user gamasucc from 149.202.55.18 port 34470 ssh2
...
2019-11-03 01:22:36
165.192.91.85 attackbots
Microsoft-Windows-Security-Auditing
2019-11-03 01:24:56
88.3.125.195 attackbotsspam
(sshd) Failed SSH login from 88.3.125.195 (ES/Spain/195.red-88-3-125.dynamicip.rima-tde.net): 3 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Nov  2 11:52:28 andromeda sshd[15379]: Invalid user pi from 88.3.125.195 port 35164
Nov  2 11:52:28 andromeda sshd[15380]: Invalid user pi from 88.3.125.195 port 35174
Nov  2 11:52:30 andromeda sshd[15379]: Failed password for invalid user pi from 88.3.125.195 port 35164 ssh2
2019-11-03 01:12:32
70.132.62.88 attackbots
Automatic report generated by Wazuh
2019-11-03 01:05:47
89.214.212.39 attack
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/89.214.212.39/ 
 
 PT - 1H : (10)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : PT 
 NAME ASN : ASN42863 
 
 IP : 89.214.212.39 
 
 CIDR : 89.214.0.0/16 
 
 PREFIX COUNT : 9 
 
 UNIQUE IP COUNT : 254976 
 
 
 ATTACKS DETECTED ASN42863 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 2 
 24H - 2 
 
 DateTime : 2019-11-02 12:52:28 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-11-03 01:17:28
177.73.104.199 attack
Automatic report - Banned IP Access
2019-11-03 01:24:41
196.194.145.94 attackspambots
Lines containing failures of 196.194.145.94
Nov  2 04:41:52 Tosca sshd[28293]: Invalid user admin from 196.194.145.94 port 40576
Nov  2 04:41:52 Tosca sshd[28293]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=196.194.145.94 
Nov  2 04:41:53 Tosca sshd[28293]: Failed password for invalid user admin from 196.194.145.94 port 40576 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=196.194.145.94
2019-11-03 00:48:56
91.224.182.202 attack
Unauthorised access (Nov  2) SRC=91.224.182.202 LEN=52 TTL=118 ID=18889 DF TCP DPT=445 WINDOW=8192 SYN
2019-11-03 00:54:55
183.88.218.141 attackbots
Nov  2 14:49:34 master sshd[31082]: Failed password for invalid user admin from 183.88.218.141 port 35356 ssh2
2019-11-03 00:46:28
80.82.64.214 attackbots
Auto reported by IDS
2019-11-03 00:40:23
156.96.155.246 attackspam
Nov  2 17:09:34 tor-proxy-02 sshd\[28381\]: User root from 156.96.155.246 not allowed because not listed in AllowUsers
Nov  2 17:09:35 tor-proxy-02 sshd\[28383\]: User root from 156.96.155.246 not allowed because not listed in AllowUsers
Nov  2 17:09:39 tor-proxy-02 sshd\[28387\]: Invalid user admin from 156.96.155.246 port 2008
...
2019-11-03 00:41:31
175.101.19.186 attackspambots
Unauthorised access (Nov  2) SRC=175.101.19.186 LEN=44 TTL=244 ID=62448 TCP DPT=445 WINDOW=1024 SYN
2019-11-03 00:54:26
185.162.235.113 attack
2019-11-02T18:05:02.286141mail01 postfix/smtpd[31878]: warning: unknown[185.162.235.113]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-11-02T18:10:20.373191mail01 postfix/smtpd[23751]: warning: unknown[185.162.235.113]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-11-02T18:10:20.373608mail01 postfix/smtpd[23752]: warning: unknown[185.162.235.113]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-11-03 01:12:14
154.16.67.143 attack
Nov  2 02:05:33 sachi sshd\[11931\]: Invalid user wacao from 154.16.67.143
Nov  2 02:05:34 sachi sshd\[11931\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=154.16.67.143
Nov  2 02:05:35 sachi sshd\[11931\]: Failed password for invalid user wacao from 154.16.67.143 port 60318 ssh2
Nov  2 02:09:53 sachi sshd\[12405\]: Invalid user jermaine from 154.16.67.143
Nov  2 02:09:53 sachi sshd\[12405\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=154.16.67.143
2019-11-03 01:07:56

Recently Reported IPs

14.207.213.39 14.207.213.179 14.207.213.208 14.207.213.30
14.207.213.6 14.207.213.88 14.207.213.9 14.207.213.80
14.207.213.56 14.207.214.131 14.207.214.12 112.198.205.227
14.207.213.82 14.207.214.140 14.207.213.73 14.207.214.105
14.207.214.167 14.207.214.183 14.207.214.208 14.207.214.199