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 of America (the)

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

;; QUESTION SECTION:
;68.131.41.59.			IN	A

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

;; Query time: 37 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 04 09:16:15 CST 2025
;; MSG SIZE  rcvd: 105
Host info
59.41.131.68.in-addr.arpa domain name pointer pool-68-131-41-59.nrflva.fios.verizon.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
59.41.131.68.in-addr.arpa	name = pool-68-131-41-59.nrflva.fios.verizon.net.

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

My name’s Eric, I found ottochiropractic.net 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-09-07 07:42:11
192.99.8.102 attack
(mod_security) mod_security (id:1010101) triggered by 192.99.8.102 (CA/Canada/ns553671.ip-192-99-8.net): 5 in the last 3600 secs
2020-09-07 07:57:17
185.158.142.144 attack
Honeypot attack, port: 445, PTR: 144-142-158-185.wifi4all.it.
2020-09-07 08:19:52
101.227.82.60 attackspambots
Ssh brute force
2020-09-07 08:02:29
140.143.143.200 attackspambots
Sep  6 18:41:12 MainVPS sshd[14696]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.143.200  user=root
Sep  6 18:41:14 MainVPS sshd[14696]: Failed password for root from 140.143.143.200 port 33416 ssh2
Sep  6 18:45:59 MainVPS sshd[21436]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.143.200  user=root
Sep  6 18:46:01 MainVPS sshd[21436]: Failed password for root from 140.143.143.200 port 56844 ssh2
Sep  6 18:50:44 MainVPS sshd[29113]: Invalid user kxy from 140.143.143.200 port 52056
...
2020-09-07 08:15:56
158.69.163.156 attack
[portscan] Port scan
2020-09-07 08:18:09
190.8.116.177 attack
$f2bV_matches
2020-09-07 08:17:32
159.203.219.38 attackbotsspam
Sep  6 21:31:53 xeon sshd[42337]: Failed password for root from 159.203.219.38 port 50382 ssh2
2020-09-07 07:57:33
138.255.0.27 attackspambots
$f2bV_matches
2020-09-07 08:01:56
222.89.70.216 attackspam
 TCP (SYN) 222.89.70.216:62926 -> port 22, len 44
2020-09-07 07:47:08
122.51.68.119 attack
Sep  7 00:23:17 myvps sshd[6262]: Failed password for root from 122.51.68.119 port 57754 ssh2
Sep  7 00:34:55 myvps sshd[13630]: Failed password for root from 122.51.68.119 port 58898 ssh2
...
2020-09-07 08:15:09
145.239.62.249 attack
Sep  1 00:02:34 cloud sshd[23326]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=145.239.62.249  user=r.r
Sep  1 00:02:35 cloud sshd[23326]: Failed password for r.r from 145.239.62.249 port 37562 ssh2
Sep  1 00:17:41 cloud sshd[24466]: Invalid user version from 145.239.62.249 port 58988
Sep  1 00:17:41 cloud sshd[24466]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=145.239.62.249

........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=145.239.62.249
2020-09-07 07:55:11
51.68.11.199 attack
MYH,DEF GET /wp-login.php
2020-09-07 08:17:00
77.78.157.71 attack
Email rejected due to spam filtering
2020-09-07 08:03:39
172.104.242.173 attackbotsspam
Multiport scan : 4 ports scanned 8332 8333 9001 9090
2020-09-07 08:10:11

Recently Reported IPs

191.151.124.160 8.161.233.35 53.126.77.76 234.254.43.40
147.196.54.37 30.90.247.103 96.170.141.192 85.25.113.215
152.3.57.232 167.19.159.174 212.115.121.232 193.29.148.229
95.4.166.235 79.51.121.106 233.38.136.140 78.64.144.197
13.252.244.134 117.31.184.22 170.155.86.165 59.87.0.253