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

;; QUESTION SECTION:
;104.149.252.197.		IN	A

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

;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 15:40:35 CST 2022
;; MSG SIZE  rcvd: 108
Host info
197.252.149.104.in-addr.arpa domain name pointer unassigned.psychz.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
197.252.149.104.in-addr.arpa	name = unassigned.psychz.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
212.102.33.47 attack
(From stubbs.alejandro@outlook.com) Hello,

I’m David Domine, owner of Louisville Historic Tours that operates here in Old Louisville, Kentucky.  
Like many businesses, I’m sure you and your employees have probably been stuck at home because of the Kentucky-wide lockdown. Most restaurants and bars still aren’t accepting large groups. This is making get-togethers or outside team building exercises currently impossible. 

That’s why I’m reaching out today.  I run a Daytime Walking Tour and a Nighttime Ghost Tour right here in Louisville.  Since our tours are outside, we are operating fully, and we are able to take groups of people (as long as we follow the social distancing guidelines.)

I’ve had a huge increase in the amount of organizations booking private tours for their employees since everyone is looking for a way to get together.  I wanted to reach out to you about the same possibility.    

Here’s the Daytime Walking Tour:

https://bit.ly/DaytimeWalkingTour

And here’s a bit of detail on the
2020-06-28 13:36:05
94.23.33.22 attackbotsspam
Jun 28 05:28:59 onepixel sshd[783195]: Invalid user ha from 94.23.33.22 port 50220
Jun 28 05:28:59 onepixel sshd[783195]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.23.33.22 
Jun 28 05:28:59 onepixel sshd[783195]: Invalid user ha from 94.23.33.22 port 50220
Jun 28 05:29:01 onepixel sshd[783195]: Failed password for invalid user ha from 94.23.33.22 port 50220 ssh2
Jun 28 05:31:00 onepixel sshd[784390]: Invalid user user from 94.23.33.22 port 56310
2020-06-28 13:40:36
112.196.54.35 attackspambots
Invalid user postgres from 112.196.54.35 port 47076
2020-06-28 13:20:23
51.38.130.242 attackspambots
2020-06-28T05:16:33.138419shield sshd\[16753\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=242.ip-51-38-130.eu  user=root
2020-06-28T05:16:34.716564shield sshd\[16753\]: Failed password for root from 51.38.130.242 port 52486 ssh2
2020-06-28T05:19:56.021080shield sshd\[18050\]: Invalid user oracle from 51.38.130.242 port 51724
2020-06-28T05:19:56.024764shield sshd\[18050\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=242.ip-51-38-130.eu
2020-06-28T05:19:57.476908shield sshd\[18050\]: Failed password for invalid user oracle from 51.38.130.242 port 51724 ssh2
2020-06-28 13:32:07
186.7.139.13 attackspam
186.7.139.13 - - [28/Jun/2020:04:48:39 +0100] "POST /wp-login.php HTTP/1.1" 200 7828 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)"
186.7.139.13 - - [28/Jun/2020:04:51:06 +0100] "POST /wp-login.php HTTP/1.1" 200 7828 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)"
186.7.139.13 - - [28/Jun/2020:04:55:04 +0100] "POST /wp-login.php HTTP/1.1" 200 7828 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)"
...
2020-06-28 14:00:23
176.122.169.95 attackbots
Invalid user admin from 176.122.169.95 port 40638
2020-06-28 13:37:28
178.33.45.54 attackspambots
Automatic report - XMLRPC Attack
2020-06-28 13:22:04
222.239.124.19 attackbotsspam
SSH Brute-Forcing (server2)
2020-06-28 13:38:35
192.241.224.51 attackspam
trying to access non-authorized port
2020-06-28 13:30:28
125.135.79.128 attackbots
Jun 28 05:55:38 debian-2gb-nbg1-2 kernel: \[15575187.336100\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=125.135.79.128 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=49 ID=6099 PROTO=TCP SPT=63106 DPT=23 WINDOW=19731 RES=0x00 SYN URGP=0
2020-06-28 13:31:24
118.89.69.159 attack
Jun 28 05:39:36 mail sshd[16840]: Failed password for invalid user teamspeak from 118.89.69.159 port 46604 ssh2
...
2020-06-28 13:27:36
37.187.181.155 attackspambots
Unauthorised connection attempt detected at AUO MAIN. System is sshd. Protected by AUO Stack Web Application Firewall (WAF)
2020-06-28 13:34:55
191.189.238.135 attackbotsspam
Jun 28 05:18:30 *** sshd[20813]: Invalid user zwxtusr from 191.189.238.135
2020-06-28 13:23:07
51.75.29.61 attackbotsspam
Jun 27 09:21:16 Tower sshd[18369]: refused connect from 49.233.147.108 (49.233.147.108)
Jun 28 00:25:23 Tower sshd[18369]: Connection from 51.75.29.61 port 51414 on 192.168.10.220 port 22 rdomain ""
Jun 28 00:25:24 Tower sshd[18369]: Invalid user haresh from 51.75.29.61 port 51414
Jun 28 00:25:24 Tower sshd[18369]: error: Could not get shadow information for NOUSER
Jun 28 00:25:24 Tower sshd[18369]: Failed password for invalid user haresh from 51.75.29.61 port 51414 ssh2
Jun 28 00:25:24 Tower sshd[18369]: Received disconnect from 51.75.29.61 port 51414:11: Bye Bye [preauth]
Jun 28 00:25:24 Tower sshd[18369]: Disconnected from invalid user haresh 51.75.29.61 port 51414 [preauth]
2020-06-28 13:35:29
54.37.68.191 attack
Invalid user elena from 54.37.68.191 port 35958
2020-06-28 13:47:00

Recently Reported IPs

104.149.252.194 104.149.246.125 104.149.47.105 104.149.41.215
104.149.53.197 34.174.184.237 104.149.26.162 104.149.53.203
104.149.53.207 104.149.53.210 104.149.53.209 104.149.53.214
104.149.53.208 104.149.53.206 104.149.53.212 227.148.126.4
104.149.53.217 104.149.53.211 104.149.53.215 104.149.53.225