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

;; QUESTION SECTION:
;64.241.139.138.			IN	A

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

;; Query time: 208 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 05 00:42:34 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 138.139.241.64.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 138.139.241.64.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
45.152.34.24 attack
(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 plinkechiropractic.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-04-16 21:53:05
45.55.222.162 attackbots
Apr 16 07:24:02 server1 sshd\[15060\]: Invalid user virus from 45.55.222.162
Apr 16 07:24:02 server1 sshd\[15060\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.222.162 
Apr 16 07:24:04 server1 sshd\[15060\]: Failed password for invalid user virus from 45.55.222.162 port 43212 ssh2
Apr 16 07:25:32 server1 sshd\[15489\]: Invalid user cj from 45.55.222.162
Apr 16 07:25:32 server1 sshd\[15489\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.222.162 
...
2020-04-16 21:39:13
218.92.0.145 attackbots
2020-04-16T13:14:29.652334abusebot-3.cloudsearch.cf sshd[18761]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.145  user=root
2020-04-16T13:14:31.561376abusebot-3.cloudsearch.cf sshd[18761]: Failed password for root from 218.92.0.145 port 18194 ssh2
2020-04-16T13:14:35.466536abusebot-3.cloudsearch.cf sshd[18761]: Failed password for root from 218.92.0.145 port 18194 ssh2
2020-04-16T13:14:29.652334abusebot-3.cloudsearch.cf sshd[18761]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.145  user=root
2020-04-16T13:14:31.561376abusebot-3.cloudsearch.cf sshd[18761]: Failed password for root from 218.92.0.145 port 18194 ssh2
2020-04-16T13:14:35.466536abusebot-3.cloudsearch.cf sshd[18761]: Failed password for root from 218.92.0.145 port 18194 ssh2
2020-04-16T13:14:29.652334abusebot-3.cloudsearch.cf sshd[18761]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rho
...
2020-04-16 21:24:32
122.51.71.184 attack
Apr 16 14:28:13 prod4 sshd\[27814\]: Invalid user ke from 122.51.71.184
Apr 16 14:28:16 prod4 sshd\[27814\]: Failed password for invalid user ke from 122.51.71.184 port 59356 ssh2
Apr 16 14:29:59 prod4 sshd\[28390\]: Invalid user git from 122.51.71.184
...
2020-04-16 21:30:06
103.129.222.135 attackspam
prod3
...
2020-04-16 22:01:28
103.255.4.31 attack
Unauthorized connection attempt from IP address 103.255.4.31 on Port 445(SMB)
2020-04-16 21:23:04
49.88.112.111 attackbotsspam
Apr 16 18:22:12 gw1 sshd[32246]: Failed password for root from 49.88.112.111 port 44739 ssh2
Apr 16 18:22:15 gw1 sshd[32246]: Failed password for root from 49.88.112.111 port 44739 ssh2
...
2020-04-16 21:33:03
222.186.180.8 attackbotsspam
Apr 16 15:40:06 eventyay sshd[6701]: Failed password for root from 222.186.180.8 port 14284 ssh2
Apr 16 15:40:20 eventyay sshd[6701]: error: maximum authentication attempts exceeded for root from 222.186.180.8 port 14284 ssh2 [preauth]
Apr 16 15:40:25 eventyay sshd[6704]: Failed password for root from 222.186.180.8 port 24142 ssh2
...
2020-04-16 21:50:19
49.88.112.112 attack
April 16 2020, 13:23:06 [sshd] - Banned from the Cipher Host hosting platform by Fail2ban.
2020-04-16 21:32:03
118.96.45.212 attackspam
Port scan on 1 port(s): 25565
2020-04-16 21:35:26
103.254.120.222 attackspam
Apr 16 14:51:53 h2779839 sshd[31648]: Invalid user git from 103.254.120.222 port 38548
Apr 16 14:51:53 h2779839 sshd[31648]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.254.120.222
Apr 16 14:51:53 h2779839 sshd[31648]: Invalid user git from 103.254.120.222 port 38548
Apr 16 14:51:55 h2779839 sshd[31648]: Failed password for invalid user git from 103.254.120.222 port 38548 ssh2
Apr 16 14:56:39 h2779839 sshd[31860]: Invalid user userftp from 103.254.120.222 port 48664
Apr 16 14:56:39 h2779839 sshd[31860]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.254.120.222
Apr 16 14:56:39 h2779839 sshd[31860]: Invalid user userftp from 103.254.120.222 port 48664
Apr 16 14:56:41 h2779839 sshd[31860]: Failed password for invalid user userftp from 103.254.120.222 port 48664 ssh2
Apr 16 15:01:29 h2779839 sshd[31917]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.25
...
2020-04-16 22:05:37
41.233.139.125 attackspambots
SMTP brute force
...
2020-04-16 21:57:31
46.102.175.105 attack
firewall-block, port(s): 5564/tcp
2020-04-16 22:06:17
193.112.18.55 attack
Unauthorized SSH login attempts
2020-04-16 21:30:56
118.127.110.54 attackbots
Apr 16 14:14:40 haigwepa sshd[28902]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.127.110.54 
Apr 16 14:14:42 haigwepa sshd[28902]: Failed password for invalid user admin from 118.127.110.54 port 32892 ssh2
...
2020-04-16 21:52:05

Recently Reported IPs

204.180.219.185 231.51.91.97 149.108.163.159 136.211.141.212
245.4.160.83 28.254.23.117 131.116.247.76 96.56.220.202
181.56.110.210 33.140.118.24 94.21.240.55 37.163.37.105
138.240.233.130 72.159.104.23 39.226.142.195 167.187.199.112
99.204.120.70 138.20.213.172 31.119.183.87 189.192.54.37