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

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

;; QUESTION SECTION:
;242.130.128.34.			IN	A

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

;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 12 08:18:35 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 34.128.130.242.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 34.128.130.242.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
77.241.193.14 attack
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/77.241.193.14/ 
 
 LT - 1H : (1)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : LT 
 NAME ASN : ASN15440 
 
 IP : 77.241.193.14 
 
 CIDR : 77.241.192.0/20 
 
 PREFIX COUNT : 36 
 
 UNIQUE IP COUNT : 34304 
 
 
 ATTACKS DETECTED ASN15440 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 1 
 24H - 1 
 
 DateTime : 2020-01-24 05:54:59 
 
 INFO :  HACK ! - Looking for resource vulnerabilities Scan Detected and Blocked by ADMIN  - data recovery
2020-01-24 13:13:00
106.13.97.121 attackspam
Jan 24 07:09:41 pkdns2 sshd\[24160\]: Invalid user gogs from 106.13.97.121Jan 24 07:09:44 pkdns2 sshd\[24160\]: Failed password for invalid user gogs from 106.13.97.121 port 54880 ssh2Jan 24 07:11:51 pkdns2 sshd\[24337\]: Invalid user pw from 106.13.97.121Jan 24 07:11:53 pkdns2 sshd\[24337\]: Failed password for invalid user pw from 106.13.97.121 port 46792 ssh2Jan 24 07:14:06 pkdns2 sshd\[24461\]: Failed password for root from 106.13.97.121 port 38708 ssh2Jan 24 07:16:17 pkdns2 sshd\[24637\]: Failed password for root from 106.13.97.121 port 58862 ssh2
...
2020-01-24 13:27:22
68.183.197.33 attackbots
Jan 23 19:17:56 eddieflores sshd\[8784\]: Invalid user rafal from 68.183.197.33
Jan 23 19:17:56 eddieflores sshd\[8784\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.197.33
Jan 23 19:17:58 eddieflores sshd\[8784\]: Failed password for invalid user rafal from 68.183.197.33 port 43084 ssh2
Jan 23 19:21:21 eddieflores sshd\[9172\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.197.33  user=root
Jan 23 19:21:23 eddieflores sshd\[9172\]: Failed password for root from 68.183.197.33 port 46142 ssh2
2020-01-24 13:41:04
138.68.168.137 attackspam
Jan 24 05:52:15 vps691689 sshd[23745]: Failed password for root from 138.68.168.137 port 55866 ssh2
Jan 24 05:55:04 vps691689 sshd[23888]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.168.137
...
2020-01-24 13:08:12
68.183.231.137 attackbotsspam
Unauthorized connection attempt detected from IP address 68.183.231.137 to port 2220 [J]
2020-01-24 13:12:02
182.61.48.209 attack
Unauthorized connection attempt detected from IP address 182.61.48.209 to port 2220 [J]
2020-01-24 13:19:11
185.53.88.116 attackbots
*Port Scan* detected from 185.53.88.116 (NL/Netherlands/-). 4 hits in the last 145 seconds
2020-01-24 13:06:59
51.75.123.107 attackspambots
Jan 23 18:52:58 php1 sshd\[18955\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.ip-51-75-123.eu  user=root
Jan 23 18:53:00 php1 sshd\[18955\]: Failed password for root from 51.75.123.107 port 60832 ssh2
Jan 23 18:54:53 php1 sshd\[19143\]: Invalid user zheng from 51.75.123.107
Jan 23 18:54:53 php1 sshd\[19143\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.ip-51-75-123.eu
Jan 23 18:54:56 php1 sshd\[19143\]: Failed password for invalid user zheng from 51.75.123.107 port 39846 ssh2
2020-01-24 13:14:57
91.83.190.117 attackspam
Automatic report - Port Scan Attack
2020-01-24 13:37:17
218.92.0.175 attackspam
Jan 23 18:56:00 sachi sshd\[30027\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.175  user=root
Jan 23 18:56:02 sachi sshd\[30027\]: Failed password for root from 218.92.0.175 port 41212 ssh2
Jan 23 18:56:21 sachi sshd\[30052\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.175  user=root
Jan 23 18:56:23 sachi sshd\[30052\]: Failed password for root from 218.92.0.175 port 8288 ssh2
Jan 23 18:56:35 sachi sshd\[30052\]: Failed password for root from 218.92.0.175 port 8288 ssh2
2020-01-24 13:02:51
81.248.6.143 attackspam
Unauthorized connection attempt detected from IP address 81.248.6.143 to port 23 [J]
2020-01-24 13:20:46
46.38.144.102 attack
Jan 24 06:19:20 vmanager6029 postfix/smtpd\[11166\]: warning: unknown\[46.38.144.102\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan 24 06:20:12 vmanager6029 postfix/smtpd\[11166\]: warning: unknown\[46.38.144.102\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2020-01-24 13:29:56
82.64.40.245 attack
(sshd) Failed SSH login from 82.64.40.245 (FR/France/82-64-40-245.subs.proxad.net): 2 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Jan 24 05:54:49 ubnt-55d23 sshd[19522]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.64.40.245  user=root
Jan 24 05:54:52 ubnt-55d23 sshd[19522]: Failed password for root from 82.64.40.245 port 57666 ssh2
2020-01-24 13:16:54
192.3.9.2 attack
(From eric@talkwithcustomer.com) 
Hi,

Let’s take a quick trip to Tomorrow-land.

I’m not talking about a theme park, I’m talking about your business’s future…

Don’t worry, we won’t even need a crystal ball.  

Just imagine… 

… a future where the money you invest in driving traffic to your site denvertechchiro.com pays off with tons of calls from qualified leads.
 
And the difference between what you experienced in the past is staggering – you’re seeing 10X, 20X, 50X, even up to a 100X more leads coming from your website denvertechchiro.com.  Leads that are already engaged with what you have to offer and are ready to learn more and even open their wallets.

Seeing all this taking place in your business, you think back: What did I do only a short time ago that made such a huge difference?

And then it hits you: You took advantage of a free 14 day Test Drive of TalkWithCustomer.

You installed TalkWithCustomer on denvertechchiro.com – it was a snap.

And practically overnight customers st
2020-01-24 13:17:51
196.202.220.95 attackspam
spam
2020-01-24 13:44:18

Recently Reported IPs

76.170.180.73 239.141.179.42 154.5.240.36 155.15.66.110
140.132.238.163 199.2.7.196 155.212.177.77 177.127.81.73
68.49.182.33 4.22.172.65 41.133.150.64 227.69.156.170
212.13.56.205 255.143.250.241 55.222.251.199 150.123.156.221
131.207.121.37 54.104.224.56 62.150.247.129 243.178.126.203