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

;; QUESTION SECTION:
;196.53.8.104.			IN	A

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

;; Query time: 35 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jan 31 11:07:30 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 104.8.53.196.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 104.8.53.196.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
104.131.29.92 attackspam
SSH Brute-Force attacks
2020-04-09 15:38:40
74.7.85.62 attackbotsspam
Apr  9 07:35:17 localhost sshd\[8544\]: Invalid user ts from 74.7.85.62 port 39432
Apr  9 07:35:17 localhost sshd\[8544\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=74.7.85.62
Apr  9 07:35:19 localhost sshd\[8544\]: Failed password for invalid user ts from 74.7.85.62 port 39432 ssh2
...
2020-04-09 15:35:36
23.104.184.173 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 lakechirocenter.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 any
2020-04-09 15:27:57
94.247.180.153 attackbots
Apr  8 12:34:35 finn sshd[15439]: Invalid user test from 94.247.180.153 port 39368
Apr  8 12:34:35 finn sshd[15439]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.247.180.153
Apr  8 12:34:37 finn sshd[15439]: Failed password for invalid user test from 94.247.180.153 port 39368 ssh2
Apr  8 12:34:37 finn sshd[15439]: Received disconnect from 94.247.180.153 port 39368:11: Bye Bye [preauth]
Apr  8 12:34:37 finn sshd[15439]: Disconnected from 94.247.180.153 port 39368 [preauth]
Apr  8 12:38:53 finn sshd[16581]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.247.180.153  user=postgres
Apr  8 12:38:55 finn sshd[16581]: Failed password for postgres from 94.247.180.153 port 40252 ssh2
Apr  8 12:38:55 finn sshd[16581]: Received disconnect from 94.247.180.153 port 40252:11: Bye Bye [preauth]
Apr  8 12:38:55 finn sshd[16581]: Disconnected from 94.247.180.153 port 40252 [preauth]


........
--------------------------------------------
2020-04-09 15:00:40
47.75.172.46 attackbots
xmlrpc attack
2020-04-09 15:03:40
203.83.121.14 spambotsattackproxynormal
Sent attack
2020-04-09 15:02:09
167.172.220.44 attack
Port scanning with `GET /nice%20ports%2C/Tri%6Eity.txt%2ebak HTTP/1.0` and others
2020-04-09 15:15:03
218.92.0.175 attack
Apr  9 08:56:57 vpn01 sshd[10268]: Failed password for root from 218.92.0.175 port 23765 ssh2
Apr  9 08:57:00 vpn01 sshd[10268]: Failed password for root from 218.92.0.175 port 23765 ssh2
...
2020-04-09 14:57:18
49.233.183.7 attack
Apr  9 06:55:38 powerpi2 sshd[19542]: Invalid user zps from 49.233.183.7 port 32958
Apr  9 06:55:40 powerpi2 sshd[19542]: Failed password for invalid user zps from 49.233.183.7 port 32958 ssh2
Apr  9 07:04:48 powerpi2 sshd[20002]: Invalid user ftp_user from 49.233.183.7 port 53388
...
2020-04-09 15:35:09
106.13.57.117 attackbotsspam
Apr  8 22:34:29 pixelmemory sshd[31345]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.57.117
Apr  8 22:34:30 pixelmemory sshd[31345]: Failed password for invalid user postgres from 106.13.57.117 port 49406 ssh2
Apr  8 22:41:40 pixelmemory sshd[435]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.57.117
...
2020-04-09 15:17:38
112.85.42.173 attack
" "
2020-04-09 15:17:59
72.220.171.102 spambotsattackproxynormal
Sent attack
2020-04-09 14:58:02
222.186.180.9 attackbotsspam
Apr  9 09:00:10 vpn01 sshd[10382]: Failed password for root from 222.186.180.9 port 6382 ssh2
Apr  9 09:00:20 vpn01 sshd[10382]: Failed password for root from 222.186.180.9 port 6382 ssh2
...
2020-04-09 15:08:54
91.117.89.50 attackbots
php vulnerability probing
2020-04-09 15:15:33
185.176.27.162 attack
Apr  9 08:44:34 debian-2gb-nbg1-2 kernel: \[8673687.636148\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.162 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=5868 PROTO=TCP SPT=43638 DPT=27010 WINDOW=1024 RES=0x00 SYN URGP=0
2020-04-09 15:16:46

Recently Reported IPs

27.185.65.245 118.86.26.34 153.177.104.143 75.51.209.222
157.118.251.185 180.185.145.224 118.185.25.213 18.159.141.165
89.243.103.170 2.181.53.66 53.20.1.178 186.189.138.91
213.105.158.53 240.58.105.134 141.78.109.48 46.96.161.4
172.6.244.21 30.47.10.138 7.102.82.156 253.245.182.182