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

;; QUESTION SECTION:
;68.8.149.185.			IN	A

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

;; Query time: 57 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 14 09:08:38 CST 2022
;; MSG SIZE  rcvd: 105
Host info
185.149.8.68.in-addr.arpa domain name pointer ip68-8-149-185.sd.sd.cox.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
185.149.8.68.in-addr.arpa	name = ip68-8-149-185.sd.sd.cox.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
212.70.149.52 attackspam
Sep  5 01:00:58 srv01 postfix/smtpd\[12736\]: warning: unknown\[212.70.149.52\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep  5 01:01:00 srv01 postfix/smtpd\[5862\]: warning: unknown\[212.70.149.52\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep  5 01:01:00 srv01 postfix/smtpd\[12449\]: warning: unknown\[212.70.149.52\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep  5 01:01:05 srv01 postfix/smtpd\[6681\]: warning: unknown\[212.70.149.52\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep  5 01:01:24 srv01 postfix/smtpd\[12736\]: warning: unknown\[212.70.149.52\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-09-05 14:25:02
178.128.248.121 attackspambots
2020-09-05T13:21:01.000568hostname sshd[97805]: Failed password for invalid user edmond from 178.128.248.121 port 60208 ssh2
...
2020-09-05 14:28:49
61.161.250.202 attackspambots
Invalid user elk from 61.161.250.202 port 53314
2020-09-05 14:10:10
179.96.254.100 attack
Sep  4 18:51:07 mellenthin postfix/smtpd[32144]: NOQUEUE: reject: RCPT from 179-96-254-100.outcenter.com.br[179.96.254.100]: 554 5.7.1 Service unavailable; Client host [179.96.254.100] blocked using zen.spamhaus.org; https://www.spamhaus.org/query/ip/179.96.254.100; from= to= proto=ESMTP helo=<179-96-254-100.outcenter.com.br>
2020-09-05 14:08:41
212.129.25.123 attackspambots
Automatic report - XMLRPC Attack
2020-09-05 14:47:20
106.12.3.28 attackspam
Sep  5 08:15:14 lnxweb62 sshd[25523]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.3.28
2020-09-05 14:23:46
198.23.250.38 attack
(From eric@talkwithwebvisitor.com) Cool website!

My name’s Eric, and I just found your site - myvenicechiropractor.com - while surfing the net. You showed up at the top of the search results, so I checked you out. Looks like what you’re doing is pretty cool.
 
But if you don’t mind me asking – after someone like me stumbles across myvenicechiropractor.com, what usually happens?

Is your site generating leads for your business? 
 
I’m guessing some, but I also bet you’d like more… studies show that 7 out 10 who land on a site wind up leaving without a trace.

Not good.

Here’s a thought – what if there was an easy way for every visitor to “raise their hand” to get a phone call from you INSTANTLY… the second they hit your site and said, “call me now.”

You can –
  
Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number.  It lets you know IMMEDIATELY – so that you can talk to that lead while they’re literally look
2020-09-05 14:22:13
191.234.178.249 attackspam
(mod_security) mod_security (id:210492) triggered by 191.234.178.249 (BR/Brazil/-): 5 in the last 3600 secs
2020-09-05 14:48:49
121.46.244.194 attackbotsspam
Sep  5 07:32:29 mavik sshd[26723]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.46.244.194
Sep  5 07:32:31 mavik sshd[26723]: Failed password for invalid user maven from 121.46.244.194 port 28408 ssh2
Sep  5 07:35:58 mavik sshd[26926]: Invalid user odoo from 121.46.244.194
Sep  5 07:35:58 mavik sshd[26926]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.46.244.194
Sep  5 07:36:00 mavik sshd[26926]: Failed password for invalid user odoo from 121.46.244.194 port 48471 ssh2
...
2020-09-05 14:38:24
172.245.58.78 attackspambots
(From eric@talkwithwebvisitor.com) Good day, 

My name is Eric and unlike a lot of emails you might get, I wanted to instead provide you with a word of encouragement – Congratulations

What for?  

Part of my job is to check out websites and the work you’ve done with guarinochiropractic.com definitely stands out. 

It’s clear you took building a website seriously and made a real investment of time and resources into making it top quality.

There is, however, a catch… more accurately, a question…

So when someone like me happens to find your site – maybe at the top of the search results (nice job BTW) or just through a random link, how do you know? 

More importantly, how do you make a connection with that person?

Studies show that 7 out of 10 visitors don’t stick around – they’re there one second and then gone with the wind.

Here’s a way to create INSTANT engagement that you may not have known about… 

Talk With Web Visitor is a software widget that’s works on your site, ready to capture
2020-09-05 14:41:04
195.54.160.180 attackbotsspam
Sep  5 08:32:16 home sshd[789933]: Invalid user payingit from 195.54.160.180 port 41555
Sep  5 08:32:16 home sshd[789933]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.54.160.180 
Sep  5 08:32:16 home sshd[789933]: Invalid user payingit from 195.54.160.180 port 41555
Sep  5 08:32:18 home sshd[789933]: Failed password for invalid user payingit from 195.54.160.180 port 41555 ssh2
Sep  5 08:32:20 home sshd[789936]: Invalid user pi from 195.54.160.180 port 52420
...
2020-09-05 14:34:42
85.26.233.32 attackbotsspam
Sep  4 18:50:51 mellenthin postfix/smtpd[32078]: NOQUEUE: reject: RCPT from unknown[85.26.233.32]: 554 5.7.1 Service unavailable; Client host [85.26.233.32] blocked using zen.spamhaus.org; https://www.spamhaus.org/query/ip/85.26.233.32; from= to= proto=ESMTP helo=<[85.26.233.32]>
2020-09-05 14:22:45
80.232.241.122 attack
Port Scan detected!
...
2020-09-05 14:36:18
60.2.224.234 attackspam
Sep  5 07:53:54 server sshd[5060]: Failed password for root from 60.2.224.234 port 40194 ssh2
Sep  5 08:05:31 server sshd[10479]: Failed password for invalid user jdoe from 60.2.224.234 port 45244 ssh2
Sep  5 08:14:40 server sshd[14792]: Failed password for invalid user dasusr1 from 60.2.224.234 port 42332 ssh2
2020-09-05 14:23:18
178.128.243.225 attack
Invalid user user01 from 178.128.243.225 port 60506
2020-09-05 14:30:32

Recently Reported IPs

68.56.173.114 68.80.206.32 68.81.70.156 68.78.70.79
68.82.72.87 68.96.138.200 68.96.237.89 68.98.187.221
69.138.144.167 69.135.42.50 69.133.53.86 69.131.129.236
69.119.109.186 69.146.112.153 69.163.203.138 69.171.232.148
69.173.215.137 69.167.190.53 69.165.37.59 69.202.201.91