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: AT&T

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;68.78.150.99.			IN	A

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

;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Apr 26 05:38:15 CST 2020
;; MSG SIZE  rcvd: 116
Host info
Host 99.150.78.68.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 99.150.78.68.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
119.28.132.211 attackspambots
Apr 22 14:04:19 nextcloud sshd\[23433\]: Invalid user is from 119.28.132.211
Apr 22 14:04:19 nextcloud sshd\[23433\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.28.132.211
Apr 22 14:04:21 nextcloud sshd\[23433\]: Failed password for invalid user is from 119.28.132.211 port 44020 ssh2
2020-04-22 21:05:50
218.102.55.123 attack
Honeypot attack, port: 5555, PTR: wtsc5a123.netvigator.com.
2020-04-22 20:50:34
81.51.156.171 attack
Apr 22 12:19:54 localhost sshd\[28128\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.51.156.171  user=root
Apr 22 12:19:56 localhost sshd\[28128\]: Failed password for root from 81.51.156.171 port 39386 ssh2
Apr 22 12:33:41 localhost sshd\[28477\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.51.156.171  user=root
...
2020-04-22 20:59:22
37.59.100.22 attackspam
Apr 22 09:23:07 firewall sshd[2815]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.59.100.22
Apr 22 09:23:07 firewall sshd[2815]: Invalid user sg from 37.59.100.22
Apr 22 09:23:10 firewall sshd[2815]: Failed password for invalid user sg from 37.59.100.22 port 42766 ssh2
...
2020-04-22 20:34:10
106.12.209.117 attack
Apr 22 15:20:41 hosting sshd[11224]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.209.117  user=root
Apr 22 15:20:43 hosting sshd[11224]: Failed password for root from 106.12.209.117 port 47710 ssh2
Apr 22 15:28:59 hosting sshd[11886]: Invalid user test from 106.12.209.117 port 58680
...
2020-04-22 21:06:20
191.102.156.130 attackbots
(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found millenniumchiro.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 tha
2020-04-22 20:42:48
94.177.217.21 attack
Apr 22 08:48:59 CT721 sshd[10287]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.177.217.21  user=r.r
Apr 22 08:49:01 CT721 sshd[10287]: Failed password for r.r from 94.177.217.21 port 37648 ssh2
Apr 22 08:49:01 CT721 sshd[10287]: Received disconnect from 94.177.217.21 port 37648:11: Bye Bye [preauth]
Apr 22 08:49:01 CT721 sshd[10287]: Disconnected from 94.177.217.21 port 37648 [preauth]
Apr 22 08:57:49 CT721 sshd[10500]: Invalid user nd from 94.177.217.21 port 53888
Apr 22 08:57:49 CT721 sshd[10500]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.177.217.21
Apr 22 08:57:51 CT721 sshd[10500]: Failed password for invalid user nd from 94.177.217.21 port 53888 ssh2
Apr 22 08:57:51 CT721 sshd[10500]: Received disconnect from 94.177.217.21 port 53888:11: Bye Bye [preauth]
Apr 22 08:57:51 CT721 sshd[10500]: Disconnected from 94.177.217.21 port 53888 [preauth]


........
-----------------------------------------------
https://ww
2020-04-22 20:30:24
51.91.251.20 attackbotsspam
Apr 22 14:04:43 * sshd[32358]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.91.251.20
Apr 22 14:04:45 * sshd[32358]: Failed password for invalid user kw from 51.91.251.20 port 42286 ssh2
2020-04-22 20:41:16
75.127.5.72 attackspambots
(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found millenniumchiro.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 tha
2020-04-22 20:48:41
222.186.30.76 attackbots
2020-04-22T14:42:39.752963sd-86998 sshd[31623]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.76  user=root
2020-04-22T14:42:41.744054sd-86998 sshd[31623]: Failed password for root from 222.186.30.76 port 37069 ssh2
2020-04-22T14:42:43.907630sd-86998 sshd[31623]: Failed password for root from 222.186.30.76 port 37069 ssh2
2020-04-22T14:42:39.752963sd-86998 sshd[31623]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.76  user=root
2020-04-22T14:42:41.744054sd-86998 sshd[31623]: Failed password for root from 222.186.30.76 port 37069 ssh2
2020-04-22T14:42:43.907630sd-86998 sshd[31623]: Failed password for root from 222.186.30.76 port 37069 ssh2
2020-04-22T14:42:39.752963sd-86998 sshd[31623]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.76  user=root
2020-04-22T14:42:41.744054sd-86998 sshd[31623]: Failed password for root from 222.186
...
2020-04-22 20:57:38
222.186.42.136 attack
Apr 22 14:44:17 vpn01 sshd[10432]: Failed password for root from 222.186.42.136 port 13996 ssh2
Apr 22 14:44:19 vpn01 sshd[10432]: Failed password for root from 222.186.42.136 port 13996 ssh2
...
2020-04-22 20:44:41
174.138.64.163 attackbots
Apr 22 06:13:46 server1 sshd\[19316\]: Failed password for invalid user test from 174.138.64.163 port 58164 ssh2
Apr 22 06:18:14 server1 sshd\[20597\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.64.163  user=root
Apr 22 06:18:17 server1 sshd\[20597\]: Failed password for root from 174.138.64.163 port 43704 ssh2
Apr 22 06:22:47 server1 sshd\[21790\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.64.163  user=root
Apr 22 06:22:49 server1 sshd\[21790\]: Failed password for root from 174.138.64.163 port 57476 ssh2
...
2020-04-22 20:34:24
180.76.156.178 attack
Apr 22 12:04:51 work-partkepr sshd\[19968\]: Invalid user ke from 180.76.156.178 port 40516
Apr 22 12:04:51 work-partkepr sshd\[19968\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.156.178
...
2020-04-22 20:39:15
194.26.29.114 attack
Apr 22 13:43:49 [host] kernel: [4184902.418562] [U
Apr 22 13:55:21 [host] kernel: [4185594.694044] [U
Apr 22 14:04:01 [host] kernel: [4186114.011631] [U
Apr 22 14:31:40 [host] kernel: [4187773.096069] [U
Apr 22 14:32:34 [host] kernel: [4187826.770087] [U
Apr 22 14:40:14 [host] kernel: [4188286.828051] [U
2020-04-22 20:54:37
45.123.43.114 attackbotsspam
Sending SPAM email
2020-04-22 20:27:04

Recently Reported IPs

201.255.99.208 177.229.23.199 185.198.64.120 2.104.149.79
217.163.205.228 32.60.73.191 24.42.239.154 89.223.28.175
67.35.1.222 202.82.171.68 154.236.25.86 83.29.88.228
124.28.132.209 169.38.131.81 182.63.158.157 123.214.195.45
74.254.78.7 151.205.229.10 61.119.164.91 49.166.9.202