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: South Africa

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

;; QUESTION SECTION:
;105.214.168.85.			IN	A

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

;; Query time: 20 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Nov 23 09:19:36 CST 2023
;; MSG SIZE  rcvd: 107
Host info
Host 85.168.214.105.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 85.168.214.105.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
222.186.52.107 attack
Sep 30 11:18:08 dedicated sshd[14503]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.52.107  user=root
Sep 30 11:18:10 dedicated sshd[14503]: Failed password for root from 222.186.52.107 port 14838 ssh2
2019-09-30 17:30:45
67.205.153.16 attackspam
frenzy
2019-09-30 17:35:02
212.20.54.63 attackspambots
09/29/2019-23:53:08.266500 212.20.54.63 Protocol: 1 GPL SCAN PING NMAP
2019-09-30 17:38:57
139.129.130.253 attackbotsspam
php WP PHPmyadamin ABUSE blocked for 12h
2019-09-30 17:44:05
146.66.244.246 attack
Fail2Ban - SSH Bruteforce Attempt
2019-09-30 17:20:44
113.57.130.172 attackspambots
$f2bV_matches
2019-09-30 17:55:54
23.250.36.89 attackbotsspam
(From BillGrant0124@gmail.com) Hi!

Do you want your website to start performing better on Google? The fact of the matter is that every website needs to be optimized before it can attain its full potential out on the Web. Your website is definitely no exception - but here's the good news. 

With a few key feature upgrades and inspections of your website's structure and code, we can get it up to spec. You can begin demolishing your competition - even the ones that have been around for years. It's definitely not impossible. Remember: if you're not on the first page, then you might be missing a lot of business opportunities. We can work together to help you reach the top.

I'm offering you a free consultation, so I can show you how the optimization can make your website rank higher on Google and other search engines. Kindly let me know if you're interested, so I can give you a call at a time that works best for you. I hope to speak with you soon.

Thank you.
Bill Grant
2019-09-30 17:59:59
45.55.158.8 attack
$f2bV_matches
2019-09-30 17:28:02
148.235.57.183 attackspambots
Sep 30 04:32:28 plusreed sshd[4586]: Invalid user yi123 from 148.235.57.183
...
2019-09-30 17:47:28
202.65.154.162 attack
Sep 30 07:09:33 www2 sshd\[28376\]: Invalid user shi from 202.65.154.162Sep 30 07:09:35 www2 sshd\[28376\]: Failed password for invalid user shi from 202.65.154.162 port 13496 ssh2Sep 30 07:14:57 www2 sshd\[28966\]: Failed password for root from 202.65.154.162 port 16909 ssh2
...
2019-09-30 17:36:55
185.245.84.50 attack
CloudCIX Reconnaissance Scan Detected, PTR: no-mans-land.m247.com.
2019-09-30 17:48:43
216.14.163.172 attackspam
SSH/22 MH Probe, BF, Hack -
2019-09-30 17:33:05
171.67.70.91 attack
Here more information about 171.67.70.91 
info: [Unhostnameed States] 32 Stanford Univershostnamey 
DNS: research.esrg.stanford.edu 
Connected: 6 servere(s) 
Reason: ssh 
Portscan/portflood
Ports: 22,110,1433 
Services: ssh,pop3,ms-sql-s 
servere: Europe/Moscow (UTC+3) 
Found at blocklist: abuseIPDB.com
myIP:89.179.244.250 
 
[2019-09-28 12:29:09] (tcp) myIP:22 <- 171.67.70.91:40976
[2019-09-28 15:04:23] (tcp) myIP:110 <- 171.67.70.91:45445
[2019-09-28 16:21:56] (tcp) myIP:1433 <- 171.67.70.91:43447
[2019-09-29 12:29:06] (tcp) myIP:22 <- 171.67.70.91:37034
[2019-09-29 15:04:23] (tcp) myIP:110 <- 171.67.70.91:35696
[2019-09-29 16:21:57] (tcp) myIP:1433 <- 171.67.70.91:53933


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=171.67.70.91
2019-09-30 17:45:51
125.130.110.20 attackspam
Sep 30 09:55:43 pornomens sshd\[17621\]: Invalid user lutz from 125.130.110.20 port 40186
Sep 30 09:55:43 pornomens sshd\[17621\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.130.110.20
Sep 30 09:55:45 pornomens sshd\[17621\]: Failed password for invalid user lutz from 125.130.110.20 port 40186 ssh2
...
2019-09-30 17:55:40
222.186.169.194 attack
Sep 30 11:24:57 legacy sshd[3780]: Failed password for root from 222.186.169.194 port 62272 ssh2
Sep 30 11:25:02 legacy sshd[3780]: Failed password for root from 222.186.169.194 port 62272 ssh2
Sep 30 11:25:06 legacy sshd[3780]: Failed password for root from 222.186.169.194 port 62272 ssh2
Sep 30 11:25:14 legacy sshd[3780]: error: maximum authentication attempts exceeded for root from 222.186.169.194 port 62272 ssh2 [preauth]
...
2019-09-30 17:33:27

Recently Reported IPs

105.215.205.25 105.215.178.30 105.214.23.25 105.214.88.15
105.214.107.70 105.214.48.229 105.214.143.204 105.214.195.134
105.215.112.15 105.214.222.24 105.214.157.27 105.214.45.66
105.214.174.24 105.215.55.46 105.215.62.244 105.214.15.170
105.214.198.218 105.214.131.254 105.214.138.198 105.215.141.35