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

;; QUESTION SECTION:
;145.45.130.119.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jan 27 09:08:37 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 119.130.45.145.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 119.130.45.145.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
45.61.172.235 attackbotsspam
(From eric@talkwithcustomer.com) Hey,

You have a website westsidechiroga.com, right?

Of course you do. I am looking at your website now.

It gets traffic every day – that you’re probably spending $2 / $4 / $10 or more a click to get.  Not including all of the work you put into creating social media, videos, blog posts, emails, and so on.

So you’re investing seriously in getting people to that site.

But how’s it working?  Great? Okay?  Not so much?

If that answer could be better, then it’s likely you’re putting a lot of time, effort, and money into an approach that’s not paying off like it should.

Now… imagine doubling your lead conversion in just minutes… In fact, I’ll go even better.
 
You could actually get up to 100X more conversions!

I’m not making this up.  As Chris Smith, best-selling author of The Conversion Code says: Speed is essential - there is a 100x decrease in Leads when a Lead is contacted within 14 minutes vs being contacted within 5 minutes.

He’s backed up by a stu
2019-10-20 16:49:03
212.237.37.100 attackbotsspam
2019-10-20T04:59:21.074494shield sshd\[14744\]: Invalid user bulldogs from 212.237.37.100 port 38228
2019-10-20T04:59:21.079537shield sshd\[14744\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.237.37.100
2019-10-20T04:59:23.080322shield sshd\[14744\]: Failed password for invalid user bulldogs from 212.237.37.100 port 38228 ssh2
2019-10-20T05:03:07.327978shield sshd\[15724\]: Invalid user Server@1234 from 212.237.37.100 port 48822
2019-10-20T05:03:07.333258shield sshd\[15724\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.237.37.100
2019-10-20 17:10:02
36.68.53.128 attackbots
php WP PHPmyadamin ABUSE blocked for 12h
2019-10-20 17:06:44
142.93.215.102 attackspambots
Oct 20 10:55:51 XXX sshd[43758]: Invalid user ts3sleep from 142.93.215.102 port 53482
2019-10-20 17:25:50
185.156.1.99 attack
Oct 20 07:27:49 SilenceServices sshd[16703]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.156.1.99
Oct 20 07:27:51 SilenceServices sshd[16703]: Failed password for invalid user Nn123456789 from 185.156.1.99 port 37991 ssh2
Oct 20 07:31:57 SilenceServices sshd[17784]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.156.1.99
2019-10-20 16:48:11
104.168.123.81 attack
(From eric@talkwithcustomer.com) Hey,

You have a website westsidechiroga.com, right?

Of course you do. I am looking at your website now.

It gets traffic every day – that you’re probably spending $2 / $4 / $10 or more a click to get.  Not including all of the work you put into creating social media, videos, blog posts, emails, and so on.

So you’re investing seriously in getting people to that site.

But how’s it working?  Great? Okay?  Not so much?

If that answer could be better, then it’s likely you’re putting a lot of time, effort, and money into an approach that’s not paying off like it should.

Now… imagine doubling your lead conversion in just minutes… In fact, I’ll go even better.
 
You could actually get up to 100X more conversions!

I’m not making this up.  As Chris Smith, best-selling author of The Conversion Code says: Speed is essential - there is a 100x decrease in Leads when a Lead is contacted within 14 minutes vs being contacted within 5 minutes.

He’s backed up by a stu
2019-10-20 16:47:18
106.13.23.141 attackspam
Oct 20 09:05:01 server sshd\[24738\]: Invalid user 1234 from 106.13.23.141 port 44632
Oct 20 09:05:01 server sshd\[24738\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.23.141
Oct 20 09:05:03 server sshd\[24738\]: Failed password for invalid user 1234 from 106.13.23.141 port 44632 ssh2
Oct 20 09:10:15 server sshd\[30233\]: Invalid user passw0rd! from 106.13.23.141 port 52408
Oct 20 09:10:15 server sshd\[30233\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.23.141
2019-10-20 17:26:52
185.40.14.67 attack
3389BruteforceFW21
2019-10-20 16:53:45
103.36.84.100 attack
Oct 20 08:54:39 ovpn sshd\[20448\]: Invalid user wildfly from 103.36.84.100
Oct 20 08:54:39 ovpn sshd\[20448\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.36.84.100
Oct 20 08:54:41 ovpn sshd\[20448\]: Failed password for invalid user wildfly from 103.36.84.100 port 34220 ssh2
Oct 20 09:04:41 ovpn sshd\[22324\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.36.84.100  user=root
Oct 20 09:04:43 ovpn sshd\[22324\]: Failed password for root from 103.36.84.100 port 51334 ssh2
2019-10-20 17:07:41
178.128.213.126 attackspam
(sshd) Failed SSH login from 178.128.213.126 (SG/Singapore/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Oct 20 06:45:39 server2 sshd[15893]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.213.126  user=root
Oct 20 06:45:41 server2 sshd[15893]: Failed password for root from 178.128.213.126 port 38370 ssh2
Oct 20 07:06:12 server2 sshd[16380]: Invalid user oracle from 178.128.213.126 port 49082
Oct 20 07:06:14 server2 sshd[16380]: Failed password for invalid user oracle from 178.128.213.126 port 49082 ssh2
Oct 20 07:10:32 server2 sshd[16489]: Invalid user school from 178.128.213.126 port 60496
2019-10-20 16:59:09
176.57.217.251 attackbots
firewall-block, port(s): 1001/tcp, 9001/tcp
2019-10-20 16:56:43
91.197.57.196 attackbots
[portscan] Port scan
2019-10-20 17:19:18
111.231.139.30 attackspambots
Oct 20 05:49:13 ArkNodeAT sshd\[17857\]: Invalid user QWER4321g from 111.231.139.30
Oct 20 05:49:13 ArkNodeAT sshd\[17857\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.231.139.30
Oct 20 05:49:15 ArkNodeAT sshd\[17857\]: Failed password for invalid user QWER4321g from 111.231.139.30 port 60584 ssh2
2019-10-20 17:26:31
182.61.33.2 attack
2019-10-20T10:30:58.951310  sshd[20458]: Invalid user Tennis from 182.61.33.2 port 35612
2019-10-20T10:30:58.962783  sshd[20458]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.33.2
2019-10-20T10:30:58.951310  sshd[20458]: Invalid user Tennis from 182.61.33.2 port 35612
2019-10-20T10:31:00.370728  sshd[20458]: Failed password for invalid user Tennis from 182.61.33.2 port 35612 ssh2
2019-10-20T10:35:52.565174  sshd[20485]: Invalid user tayler from 182.61.33.2 port 41898
...
2019-10-20 17:11:40
185.40.14.206 attack
slow and persistent scanner
2019-10-20 17:12:02

Recently Reported IPs

193.202.159.23 93.54.249.34 115.42.215.238 156.3.135.27
214.188.216.204 43.81.103.40 129.130.219.19 221.140.25.158
243.115.180.207 179.114.115.164 123.237.5.214 76.14.137.58
129.153.227.185 62.59.24.46 108.30.122.38 44.153.18.238
238.55.67.196 185.58.95.220 230.27.25.235 41.119.108.71