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

;; QUESTION SECTION:
;108.213.218.54.			IN	A

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

;; Query time: 69 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 11 02:44:37 CST 2022
;; MSG SIZE  rcvd: 107
Host info
54.218.213.108.in-addr.arpa domain name pointer 108-213-218-54.lightspeed.sntcca.sbcglobal.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
54.218.213.108.in-addr.arpa	name = 108-213-218-54.lightspeed.sntcca.sbcglobal.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
167.71.6.221 attackbotsspam
Aug  3 04:17:51 server sshd\[6809\]: Invalid user chi from 167.71.6.221
Aug  3 04:17:51 server sshd\[6809\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.6.221
Aug  3 04:17:53 server sshd\[6809\]: Failed password for invalid user chi from 167.71.6.221 port 58788 ssh2
...
2019-10-09 13:48:08
161.142.225.241 attack
(sshd) Failed SSH login from 161.142.225.241 (MY/Malaysia/Penang/George Town/-/[AS9930 TIME dotCom Berhad]): 1 in the last 3600 secs
2019-10-09 13:20:56
167.99.228.223 attack
May  8 11:53:24 server sshd\[223022\]: Invalid user ispapps from 167.99.228.223
May  8 11:53:24 server sshd\[223022\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.228.223
May  8 11:53:25 server sshd\[223022\]: Failed password for invalid user ispapps from 167.99.228.223 port 53514 ssh2
...
2019-10-09 13:28:36
167.114.230.252 attackspam
Jul  9 02:36:45 server sshd\[150320\]: Invalid user solange from 167.114.230.252
Jul  9 02:36:45 server sshd\[150320\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.114.230.252
Jul  9 02:36:47 server sshd\[150320\]: Failed password for invalid user solange from 167.114.230.252 port 33751 ssh2
...
2019-10-09 13:57:04
203.176.131.246 attack
Oct  8 19:35:37 sachi sshd\[13314\]: Invalid user P@55w0rd1234 from 203.176.131.246
Oct  8 19:35:37 sachi sshd\[13314\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.176.131.246
Oct  8 19:35:39 sachi sshd\[13314\]: Failed password for invalid user P@55w0rd1234 from 203.176.131.246 port 60190 ssh2
Oct  8 19:40:38 sachi sshd\[13798\]: Invalid user Official123 from 203.176.131.246
Oct  8 19:40:38 sachi sshd\[13798\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.176.131.246
2019-10-09 13:47:27
95.147.19.112 attackspambots
IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/95.147.19.112/ 
 GB - 1H : (87)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : GB 
 NAME ASN : ASN12576 
 
 IP : 95.147.19.112 
 
 CIDR : 95.147.0.0/16 
 
 PREFIX COUNT : 69 
 
 UNIQUE IP COUNT : 6972928 
 
 
 WYKRYTE ATAKI Z ASN12576 :  
  1H - 1 
  3H - 2 
  6H - 2 
 12H - 3 
 24H - 4 
 
 DateTime : 2019-10-09 05:56:10 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-10-09 13:51:08
222.217.221.179 attack
Unauthorized connection attempt from IP address 222.217.221.179
2019-10-09 13:21:54
167.99.75.174 attackbotsspam
Oct  9 06:52:43 sso sshd[2383]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.75.174
Oct  9 06:52:45 sso sshd[2383]: Failed password for invalid user applmgr from 167.99.75.174 port 44038 ssh2
...
2019-10-09 13:17:14
61.216.159.188 attackbotsspam
MultiHost/MultiPort Probe, Scan, Hack -
2019-10-09 13:27:47
132.232.71.124 attackspambots
2019-10-09T06:18:42.5283921240 sshd\[24906\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.71.124  user=root
2019-10-09T06:18:44.3299201240 sshd\[24906\]: Failed password for root from 132.232.71.124 port 46108 ssh2
2019-10-09T06:23:42.4827421240 sshd\[25167\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.71.124  user=root
...
2019-10-09 13:07:39
222.186.180.41 attack
Oct  9 08:14:58 server sshd\[22229\]: User root from 222.186.180.41 not allowed because listed in DenyUsers
Oct  9 08:15:00 server sshd\[22229\]: Failed none for invalid user root from 222.186.180.41 port 44244 ssh2
Oct  9 08:15:01 server sshd\[22229\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.41  user=root
Oct  9 08:15:03 server sshd\[22229\]: Failed password for invalid user root from 222.186.180.41 port 44244 ssh2
Oct  9 08:15:08 server sshd\[22229\]: Failed password for invalid user root from 222.186.180.41 port 44244 ssh2
2019-10-09 13:16:54
167.99.224.168 attack
Aug  3 11:28:05 server sshd\[49058\]: Invalid user sandy from 167.99.224.168
Aug  3 11:28:05 server sshd\[49058\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.224.168
Aug  3 11:28:07 server sshd\[49058\]: Failed password for invalid user sandy from 167.99.224.168 port 40518 ssh2
...
2019-10-09 13:29:46
167.99.235.251 attack
May 25 01:30:35 server sshd\[194990\]: Invalid user deluge from 167.99.235.251
May 25 01:30:35 server sshd\[194990\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.235.251
May 25 01:30:37 server sshd\[194990\]: Failed password for invalid user deluge from 167.99.235.251 port 34890 ssh2
...
2019-10-09 13:25:13
190.248.67.123 attack
Oct  8 19:13:14 wbs sshd\[32568\]: Invalid user Pink@2017 from 190.248.67.123
Oct  8 19:13:14 wbs sshd\[32568\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.248.67.123
Oct  8 19:13:15 wbs sshd\[32568\]: Failed password for invalid user Pink@2017 from 190.248.67.123 port 50314 ssh2
Oct  8 19:17:24 wbs sshd\[439\]: Invalid user April2017 from 190.248.67.123
Oct  8 19:17:24 wbs sshd\[439\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.248.67.123
2019-10-09 13:44:54
134.209.12.162 attackbotsspam
Oct  9 07:44:38 minden010 sshd[1611]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.12.162
Oct  9 07:44:40 minden010 sshd[1611]: Failed password for invalid user p@ssw0rd1 from 134.209.12.162 port 54462 ssh2
Oct  9 07:48:36 minden010 sshd[4949]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.12.162
...
2019-10-09 13:49:47

Recently Reported IPs

113.112.222.96 112.228.32.204 111.238.191.28 235.35.174.170
155.198.248.249 172.240.116.8 129.145.230.84 180.28.218.39
173.211.10.4 118.43.241.246 131.255.208.64 146.125.115.29
235.194.177.254 250.127.8.137 222.34.27.111 203.172.255.80
151.44.102.131 246.90.211.74 156.216.31.214 161.107.149.14