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: Oceanside

Region: California

Country: United States

Internet Service Provider: unknown

Hostname: unknown

Organization: Cox Communications Inc.

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

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

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

;; Query time: 2 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Sun Aug 18 02:04:35 CST 2019
;; MSG SIZE  rcvd: 114
Host info
68.23.8.68.in-addr.arpa domain name pointer ip68-8-23-68.sd.sd.cox.net.
Nslookup info:
Server:		67.207.67.2
Address:	67.207.67.2#53

Non-authoritative answer:
68.23.8.68.in-addr.arpa	name = ip68-8-23-68.sd.sd.cox.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
134.202.64.131 attack
(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found staytunedchiropractic.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 softwa
2020-09-06 07:15:16
80.82.77.227 attackspam
firewall-block, port(s): 1024/tcp
2020-09-06 07:22:35
112.85.42.89 attackbotsspam
Sep  6 01:14:26 piServer sshd[25088]: Failed password for root from 112.85.42.89 port 44246 ssh2
Sep  6 01:14:28 piServer sshd[25088]: Failed password for root from 112.85.42.89 port 44246 ssh2
Sep  6 01:14:30 piServer sshd[25088]: Failed password for root from 112.85.42.89 port 44246 ssh2
...
2020-09-06 07:18:50
51.223.213.73 attack
Unauthorized connection attempt from IP address 51.223.213.73 on Port 445(SMB)
2020-09-06 07:34:57
75.162.234.20 attackbots
Brute forcing email accounts
2020-09-06 07:26:11
138.36.201.246 attackbots
Sep 5 18:48:02 *host* postfix/smtps/smtpd\[6367\]: warning: unknown\[138.36.201.246\]: SASL PLAIN authentication failed:
2020-09-06 07:42:44
89.47.62.88 attack
(smtpauth) Failed SMTP AUTH login from 89.47.62.88 (GB/United Kingdom/-): 5 in the last 3600 secs
2020-09-06 07:22:09
165.227.48.147 attack
Sep  5 20:26:11 prod4 sshd\[25841\]: Failed password for root from 165.227.48.147 port 35848 ssh2
Sep  5 20:30:54 prod4 sshd\[28213\]: Failed password for root from 165.227.48.147 port 43530 ssh2
Sep  5 20:35:34 prod4 sshd\[30868\]: Failed password for root from 165.227.48.147 port 51210 ssh2
...
2020-09-06 07:07:41
174.217.14.90 attackspam
Brute forcing email accounts
2020-09-06 07:23:26
94.102.51.95 attack
Port scan on 17 port(s): 3710 4085 6441 7148 12503 17424 22840 26590 35180 35776 38224 41643 41647 42622 59487 59854 61503
2020-09-06 07:30:27
162.243.130.67 attackspam
" "
2020-09-06 07:17:46
14.161.50.104 attack
$f2bV_matches
2020-09-06 07:13:26
218.92.0.192 attackbotsspam
Sep  6 00:59:05 sip sshd[1519637]: Failed password for root from 218.92.0.192 port 40730 ssh2
Sep  6 00:59:08 sip sshd[1519637]: Failed password for root from 218.92.0.192 port 40730 ssh2
Sep  6 00:59:10 sip sshd[1519637]: Failed password for root from 218.92.0.192 port 40730 ssh2
...
2020-09-06 07:38:41
91.192.46.209 attackspambots
(ftpd) Failed FTP login from 91.192.46.209 (UA/Ukraine/-): 10 in the last 3600 secs
2020-09-06 07:30:45
171.103.190.158 attackbots
failed attempts to access the website, searching for vulnerabilities, also using following IPs: 27.37.246.129 , 94.231.218.223 , 116.90.237.125 ,  190.235.214.78 ,  190.98.53.86 , 45.170.129.135 ,  170.239.242.222 , 43.249.113.243 ,  103.140.4.87 ,  171.103.190.158 , 72.210.252.135
2020-09-06 07:35:16

Recently Reported IPs

83.172.131.70 181.56.102.225 112.109.40.104 182.179.69.86
89.187.168.203 220.160.216.56 106.56.75.89 177.22.86.229
211.192.116.203 114.220.71.68 49.69.139.48 2.26.74.80
5.74.248.252 198.45.232.92 82.237.61.17 71.143.194.133
174.138.22.214 123.68.46.119 65.27.187.255 155.78.97.76