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

;; QUESTION SECTION:
;64.138.134.40.			IN	A

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

;; Query time: 40 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 10 09:40:51 CST 2025
;; MSG SIZE  rcvd: 106
Host info
40.134.138.64.in-addr.arpa domain name pointer host-64-138-134-40.masergy.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
40.134.138.64.in-addr.arpa	name = host-64-138-134-40.masergy.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
102.250.6.148 attackspam
PHI,WP GET /wp-login.php
2019-10-30 23:37:05
121.157.82.218 attack
2019-10-30T15:29:05.285448abusebot-5.cloudsearch.cf sshd\[18171\]: Invalid user robert from 121.157.82.218 port 50558
2019-10-30T15:29:05.290851abusebot-5.cloudsearch.cf sshd\[18171\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.157.82.218
2019-10-31 00:20:14
36.237.212.219 attack
23/tcp
[2019-10-30]1pkt
2019-10-30 23:35:48
23.129.64.155 attackbotsspam
$f2bV_matches
2019-10-30 23:41:02
106.54.112.173 attackspambots
2019-10-30T15:29:19.542212shield sshd\[12899\]: Invalid user sd from 106.54.112.173 port 45484
2019-10-30T15:29:19.548142shield sshd\[12899\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.112.173
2019-10-30T15:29:21.037589shield sshd\[12899\]: Failed password for invalid user sd from 106.54.112.173 port 45484 ssh2
2019-10-30T15:35:04.358959shield sshd\[13665\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.112.173  user=root
2019-10-30T15:35:06.877193shield sshd\[13665\]: Failed password for root from 106.54.112.173 port 55290 ssh2
2019-10-30 23:43:10
34.93.229.63 attackbots
Oct 30 10:34:30 ws24vmsma01 sshd[121061]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=34.93.229.63
Oct 30 10:34:33 ws24vmsma01 sshd[121061]: Failed password for invalid user user from 34.93.229.63 port 43120 ssh2
...
2019-10-31 00:10:00
222.186.169.194 attackbotsspam
Oct 30 16:52:04 rotator sshd\[9417\]: Failed password for root from 222.186.169.194 port 40798 ssh2Oct 30 16:52:07 rotator sshd\[9417\]: Failed password for root from 222.186.169.194 port 40798 ssh2Oct 30 16:52:11 rotator sshd\[9417\]: Failed password for root from 222.186.169.194 port 40798 ssh2Oct 30 16:52:16 rotator sshd\[9417\]: Failed password for root from 222.186.169.194 port 40798 ssh2Oct 30 16:52:19 rotator sshd\[9417\]: Failed password for root from 222.186.169.194 port 40798 ssh2Oct 30 16:52:25 rotator sshd\[9422\]: Failed password for root from 222.186.169.194 port 52744 ssh2
...
2019-10-30 23:59:38
178.62.41.7 attackspambots
Oct 30 14:41:29 vps01 sshd[25412]: Failed password for root from 178.62.41.7 port 60864 ssh2
2019-10-30 23:52:43
185.234.218.68 attackspam
Postfix Brute-Force reported by Fail2Ban
2019-10-30 23:34:03
128.14.181.58 attack
Port Scan: TCP/389
2019-10-30 23:36:37
114.108.181.139 attack
Oct 30 03:25:50 auw2 sshd\[18705\]: Invalid user jboss from 114.108.181.139
Oct 30 03:25:50 auw2 sshd\[18705\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.108.181.139
Oct 30 03:25:52 auw2 sshd\[18705\]: Failed password for invalid user jboss from 114.108.181.139 port 45333 ssh2
Oct 30 03:31:37 auw2 sshd\[19137\]: Invalid user craig from 114.108.181.139
Oct 30 03:31:37 auw2 sshd\[19137\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.108.181.139
2019-10-31 00:21:30
119.75.24.68 attack
SSH Brute-Force reported by Fail2Ban
2019-10-30 23:34:30
121.34.35.123 attackbotsspam
Oct 30 06:18:39 mxgate1 postfix/postscreen[10450]: CONNECT from [121.34.35.123]:27220 to [176.31.12.44]:25
Oct 30 06:18:39 mxgate1 postfix/dnsblog[10451]: addr 121.34.35.123 listed by domain cbl.abuseat.org as 127.0.0.2
Oct 30 06:18:39 mxgate1 postfix/dnsblog[10453]: addr 121.34.35.123 listed by domain zen.spamhaus.org as 127.0.0.3
Oct 30 06:18:39 mxgate1 postfix/dnsblog[10453]: addr 121.34.35.123 listed by domain zen.spamhaus.org as 127.0.0.11
Oct 30 06:18:39 mxgate1 postfix/dnsblog[10453]: addr 121.34.35.123 listed by domain zen.spamhaus.org as 127.0.0.4
Oct 30 06:18:39 mxgate1 postfix/dnsblog[10454]: addr 121.34.35.123 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2
Oct 30 06:18:39 mxgate1 postfix/dnsblog[10455]: addr 121.34.35.123 listed by domain b.barracudacentral.org as 127.0.0.2
Oct 30 06:18:45 mxgate1 postfix/postscreen[10450]: DNSBL rank 5 for [121.34.35.123]:27220
Oct x@x
Oct 30 06:18:46 mxgate1 postfix/postscreen[10450]: DISCONNECT [121.34.35.123]:27220


........
-------------------------------
2019-10-30 23:53:15
62.234.68.246 attack
Oct 30 16:37:08 server sshd\[19952\]: Invalid user adamian from 62.234.68.246
Oct 30 16:37:08 server sshd\[19952\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.68.246 
Oct 30 16:37:10 server sshd\[19952\]: Failed password for invalid user adamian from 62.234.68.246 port 42737 ssh2
Oct 30 16:57:36 server sshd\[24521\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.68.246  user=root
Oct 30 16:57:38 server sshd\[24521\]: Failed password for root from 62.234.68.246 port 36803 ssh2
...
2019-10-31 00:12:34
50.4.93.74 attackbots
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/50.4.93.74/ 
 
 US - 1H : (236)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : US 
 NAME ASN : ASN12083 
 
 IP : 50.4.93.74 
 
 CIDR : 50.4.92.0/22 
 
 PREFIX COUNT : 944 
 
 UNIQUE IP COUNT : 1142272 
 
 
 ATTACKS DETECTED ASN12083 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 1 
 24H - 1 
 
 DateTime : 2019-10-30 12:51:07 
 
 INFO : Port SSH 22 Scan Detected and Blocked by ADMIN  - data recovery
2019-10-31 00:01:58

Recently Reported IPs

107.99.137.196 233.71.44.8 176.199.185.128 133.89.86.181
202.157.191.5 80.34.49.204 120.128.71.47 39.140.69.236
13.78.39.164 2.173.149.243 204.160.139.178 162.122.84.12
63.4.85.1 165.238.215.187 159.48.96.190 156.122.7.122
104.169.207.213 92.90.90.82 17.179.61.52 26.159.228.51