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

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

;; QUESTION SECTION:
;204.145.19.52.			IN	A

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

;; Query time: 187 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 14 12:22:55 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 52.19.145.204.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 52.19.145.204.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
107.175.79.136 attack
(From eric@talkwithcustomer.com) Hello ehschiro.com,

People ask, “why does TalkWithCustomer work so well?”

It’s simple.

TalkWithCustomer enables you to connect with a prospective customer at EXACTLY the Perfect Time.

- NOT one week, two weeks, three weeks after they’ve checked out your website ehschiro.com.
- NOT with a form letter style email that looks like it was written by a bot.
- NOT with a robocall that could come at any time out of the blue.

TalkWithCustomer connects you to that person within seconds of THEM asking to hear from YOU.

They kick off the conversation.

They take that first step.

They ask to hear from you regarding what you have to offer and how it can make their life better. 

And it happens almost immediately. In real time. While they’re still looking over your website ehschiro.com, trying to make up their mind whether you are right for them.

When you connect with them at that very moment it’s the ultimate in Perfect Timing – as one famous marketer put it, “
2019-12-30 20:36:18
185.175.93.27 attackbots
ET DROP Dshield Block Listed Source group 1 - port: 44957 proto: TCP cat: Misc Attack
2019-12-30 20:39:38
121.67.246.132 attackspam
Dec 30 13:28:05 v22018076622670303 sshd\[20975\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.67.246.132  user=root
Dec 30 13:28:07 v22018076622670303 sshd\[20975\]: Failed password for root from 121.67.246.132 port 37654 ssh2
Dec 30 13:34:12 v22018076622670303 sshd\[21007\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.67.246.132  user=mail
...
2019-12-30 20:38:23
116.214.56.11 attackbots
Dec 30 10:24:34 herz-der-gamer sshd[30726]: Invalid user atlanta from 116.214.56.11 port 48550
Dec 30 10:24:34 herz-der-gamer sshd[30726]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.214.56.11
Dec 30 10:24:34 herz-der-gamer sshd[30726]: Invalid user atlanta from 116.214.56.11 port 48550
Dec 30 10:24:36 herz-der-gamer sshd[30726]: Failed password for invalid user atlanta from 116.214.56.11 port 48550 ssh2
...
2019-12-30 20:51:57
114.237.194.220 attackspambots
Dec 30 07:22:11 grey postfix/smtpd\[12275\]: NOQUEUE: reject: RCPT from unknown\[114.237.194.220\]: 554 5.7.1 Service unavailable\; Client host \[114.237.194.220\] blocked using cbl.abuseat.org\; Blocked - see http://www.abuseat.org/lookup.cgi\?ip=114.237.194.220\; from=\ to=\ proto=SMTP helo=\
...
2019-12-30 20:45:53
123.206.63.186 attack
Dec 30 08:48:38 amit sshd\[17277\]: Invalid user public from 123.206.63.186
Dec 30 08:48:38 amit sshd\[17277\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.206.63.186
Dec 30 08:48:40 amit sshd\[17277\]: Failed password for invalid user public from 123.206.63.186 port 34174 ssh2
...
2019-12-30 20:18:01
112.85.42.185 attack
sshd jail - ssh hack attempt
2019-12-30 20:35:03
95.58.194.148 attackspambots
Dec 30 08:27:05 ArkNodeAT sshd\[12968\]: Invalid user 00 from 95.58.194.148
Dec 30 08:27:05 ArkNodeAT sshd\[12968\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=95.58.194.148
Dec 30 08:27:07 ArkNodeAT sshd\[12968\]: Failed password for invalid user 00 from 95.58.194.148 port 40452 ssh2
2019-12-30 20:49:21
213.234.26.179 attackbots
Dec 30 09:03:14 server sshd\[11114\]: Invalid user saldana from 213.234.26.179
Dec 30 09:03:14 server sshd\[11114\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ftp1.rlan.ru 
Dec 30 09:03:16 server sshd\[11114\]: Failed password for invalid user saldana from 213.234.26.179 port 51929 ssh2
Dec 30 09:22:04 server sshd\[15007\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ftp1.rlan.ru  user=root
Dec 30 09:22:07 server sshd\[15007\]: Failed password for root from 213.234.26.179 port 36641 ssh2
...
2019-12-30 20:48:18
114.99.4.29 attackspambots
Dec 30 07:10:02 garuda postfix/smtpd[1105]: connect from unknown[114.99.4.29]
Dec 30 07:10:02 garuda postfix/smtpd[1105]: connect from unknown[114.99.4.29]
Dec 30 07:10:04 garuda postfix/smtpd[1105]: warning: unknown[114.99.4.29]: SASL LOGIN authentication failed: generic failure
Dec 30 07:10:04 garuda postfix/smtpd[1105]: warning: unknown[114.99.4.29]: SASL LOGIN authentication failed: generic failure
Dec 30 07:10:04 garuda postfix/smtpd[1105]: lost connection after AUTH from unknown[114.99.4.29]
Dec 30 07:10:04 garuda postfix/smtpd[1105]: lost connection after AUTH from unknown[114.99.4.29]
Dec 30 07:10:04 garuda postfix/smtpd[1105]: disconnect from unknown[114.99.4.29] ehlo=1 auth=0/1 commands=1/2
Dec 30 07:10:04 garuda postfix/smtpd[1105]: disconnect from unknown[114.99.4.29] ehlo=1 auth=0/1 commands=1/2
Dec 30 07:10:04 garuda postfix/smtpd[1105]: connect from unknown[114.99.4.29]
Dec 30 07:10:04 garuda postfix/smtpd[1105]: connect from unknown[114.99.4.29]
Dec 30 0........
-------------------------------
2019-12-30 20:14:31
138.94.160.57 attack
Automatic report - Banned IP Access
2019-12-30 20:46:58
59.153.74.43 attackbotsspam
Dec 30 11:09:30 MK-Soft-Root1 sshd[21074]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.153.74.43 
Dec 30 11:09:32 MK-Soft-Root1 sshd[21074]: Failed password for invalid user sondueimer from 59.153.74.43 port 41697 ssh2
...
2019-12-30 20:26:03
211.75.174.135 attackbots
(sshd) Failed SSH login from 211.75.174.135 (211-75-174-135.HINET-IP.hinet.net): 5 in the last 3600 secs
2019-12-30 20:53:05
14.191.173.43 attackspambots
19/12/30@01:22:01: FAIL: Alarm-Network address from=14.191.173.43
19/12/30@01:22:01: FAIL: Alarm-Network address from=14.191.173.43
...
2019-12-30 20:50:31
112.21.188.251 attackbots
Unauthorized connection attempt detected from IP address 112.21.188.251 to port 22
2019-12-30 20:35:31

Recently Reported IPs

232.110.100.243 118.155.244.102 248.138.75.223 12.87.234.27
9.39.165.86 35.72.106.78 228.152.152.76 80.153.136.153
21.91.206.153 245.37.162.250 161.255.39.165 153.104.153.3
250.82.121.44 39.214.67.142 152.96.238.49 186.251.217.137
71.153.176.46 239.128.214.148 78.164.96.46 168.156.192.97