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: United States

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

;; QUESTION SECTION:
;159.140.212.77.			IN	A

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

;; Query time: 71 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Jul 23 05:23:51 CST 2022
;; MSG SIZE  rcvd: 107
Host info
77.212.140.159.in-addr.arpa domain name pointer my.cerner.com.
77.212.140.159.in-addr.arpa domain name pointer myorigin.cerner.com.
77.212.140.159.in-addr.arpa domain name pointer devices.cerner.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
77.212.140.159.in-addr.arpa	name = my.cerner.com.
77.212.140.159.in-addr.arpa	name = myorigin.cerner.com.
77.212.140.159.in-addr.arpa	name = devices.cerner.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
36.22.187.34 attackspam
2020-06-26T23:33:00.624203hostname sshd[27214]: Invalid user lqy from 36.22.187.34 port 46076
2020-06-26T23:33:02.784823hostname sshd[27214]: Failed password for invalid user lqy from 36.22.187.34 port 46076 ssh2
2020-06-26T23:37:07.448447hostname sshd[30307]: Invalid user postgres from 36.22.187.34 port 55870
...
2020-06-27 19:19:48
157.0.132.174 attack
Port scan: Attack repeated for 24 hours
2020-06-27 19:25:08
218.92.0.145 attack
Jun 27 13:46:04 server sshd[22048]: Failed none for root from 218.92.0.145 port 40635 ssh2
Jun 27 13:46:06 server sshd[22048]: Failed password for root from 218.92.0.145 port 40635 ssh2
Jun 27 13:46:10 server sshd[22048]: Failed password for root from 218.92.0.145 port 40635 ssh2
2020-06-27 19:46:31
181.48.120.219 attackbotsspam
Jun 27 11:39:32 web8 sshd\[20140\]: Invalid user www from 181.48.120.219
Jun 27 11:39:32 web8 sshd\[20140\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.48.120.219
Jun 27 11:39:34 web8 sshd\[20140\]: Failed password for invalid user www from 181.48.120.219 port 7711 ssh2
Jun 27 11:42:50 web8 sshd\[21766\]: Invalid user admin from 181.48.120.219
Jun 27 11:42:50 web8 sshd\[21766\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.48.120.219
2020-06-27 19:51:40
13.65.243.121 attackspam
2020-06-26 UTC: (2x) - root(2x)
2020-06-27 19:32:49
110.172.188.220 attackspam
Telnet Server BruteForce Attack
2020-06-27 19:48:49
61.177.172.54 attackbotsspam
Jun 27 13:20:21 vpn01 sshd[23644]: Failed password for root from 61.177.172.54 port 5074 ssh2
Jun 27 13:20:31 vpn01 sshd[23644]: Failed password for root from 61.177.172.54 port 5074 ssh2
...
2020-06-27 19:54:52
24.142.35.133 attackspam
Jun 27 13:23:10 [host] sshd[9067]: Invalid user te
Jun 27 13:23:10 [host] sshd[9067]: pam_unix(sshd:a
Jun 27 13:23:13 [host] sshd[9067]: Failed password
2020-06-27 19:35:20
20.185.106.195 attack
2020-06-26 UTC: (4x) - root(4x)
2020-06-27 19:52:22
20.185.32.70 attack
Invalid user admin from 20.185.32.70 port 6622
2020-06-27 19:37:00
198.245.64.185 attackspambots
(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found loischiropractic.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well.

So here’s my question – what happens AFTER someone lands on your site?  Anything?

Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever.

That means that all the work and effort you put into getting them to show up, goes down the tubes.

Why would you want all that good work – and the great site you’ve built – go to waste?

Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry.

But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket?
  
You can – thanks to revolutionary new software th
2020-06-27 19:24:38
138.68.158.215 attack
138.68.158.215 - - [27/Jun/2020:12:47:46 +0200] "GET /wp-login.php HTTP/1.1" 200 6310 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
138.68.158.215 - - [27/Jun/2020:12:47:47 +0200] "POST /wp-login.php HTTP/1.1" 200 6561 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
138.68.158.215 - - [27/Jun/2020:12:47:48 +0200] "POST /xmlrpc.php HTTP/1.1" 200 427 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2020-06-27 19:55:46
46.245.222.203 attack
2020-06-27T12:40:11.684991snf-827550 sshd[4125]: Invalid user ek from 46.245.222.203 port 1368
2020-06-27T12:40:13.263184snf-827550 sshd[4125]: Failed password for invalid user ek from 46.245.222.203 port 1368 ssh2
2020-06-27T12:48:51.148979snf-827550 sshd[4203]: Invalid user fhl from 46.245.222.203 port 39486
...
2020-06-27 19:42:41
139.170.150.250 attackspambots
prod11
...
2020-06-27 19:44:19
60.167.177.28 attack
bruteforce detected
2020-06-27 19:31:19

Recently Reported IPs

159.141.179.186 159.140.179.8 159.144.243.129 159.140.151.167
159.144.255.191 159.140.16.5 159.140.62.213 159.144.45.162
159.144.67.199 159.144.32.26 159.144.116.246 159.14.164.51
159.143.16.125 159.14.92.151 159.14.107.97 159.14.187.226
159.143.193.179 159.140.158.1 159.140.118.86 159.14.126.32