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

;; QUESTION SECTION:
;104.248.200.148.		IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 16:12:07 CST 2022
;; MSG SIZE  rcvd: 108
Host info
148.200.248.104.in-addr.arpa domain name pointer ru-sm.club.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
148.200.248.104.in-addr.arpa	name = ru-sm.club.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
94.231.136.154 attack
Oct 24 16:36:04 MK-Soft-VM3 sshd[21547]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.231.136.154 
Oct 24 16:36:06 MK-Soft-VM3 sshd[21547]: Failed password for invalid user ftpuser from 94.231.136.154 port 50722 ssh2
...
2019-10-24 23:14:38
41.232.52.126 attack
Invalid user admin from 41.232.52.126 port 34764
2019-10-24 22:56:40
68.183.110.49 attackspam
Invalid user basic from 68.183.110.49 port 48486
2019-10-24 22:52:42
114.67.230.197 attack
SSH Brute-Force reported by Fail2Ban
2019-10-24 22:42:12
182.61.182.50 attack
Invalid user eurek from 182.61.182.50 port 33254
2019-10-24 23:04:27
109.132.226.86 attackbots
Oct 24 04:26:28 auw2 sshd\[23927\]: Invalid user pi from 109.132.226.86
Oct 24 04:26:28 auw2 sshd\[23931\]: Invalid user pi from 109.132.226.86
Oct 24 04:26:28 auw2 sshd\[23927\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.132.226.86
Oct 24 04:26:28 auw2 sshd\[23931\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.132.226.86
Oct 24 04:26:31 auw2 sshd\[23927\]: Failed password for invalid user pi from 109.132.226.86 port 58506 ssh2
2019-10-24 22:44:23
221.148.45.168 attack
2019-10-24T14:48:11.301211abusebot-8.cloudsearch.cf sshd\[30782\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.148.45.168  user=root
2019-10-24 22:59:56
154.8.233.189 attackbotsspam
Invalid user nakahide from 154.8.233.189 port 40650
2019-10-24 23:04:58
192.144.184.199 attackspambots
Oct 24 16:09:56 localhost sshd\[30300\]: Invalid user ph from 192.144.184.199 port 29394
Oct 24 16:09:56 localhost sshd\[30300\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.144.184.199
Oct 24 16:09:58 localhost sshd\[30300\]: Failed password for invalid user ph from 192.144.184.199 port 29394 ssh2
2019-10-24 22:31:42
78.139.5.47 attackbotsspam
Invalid user device from 78.139.5.47 port 53278
2019-10-24 23:16:30
138.68.20.158 attackbots
Unauthorized SSH login attempts
2019-10-24 22:38:34
175.211.105.99 attackspambots
frenzy
2019-10-24 22:34:08
179.108.179.237 attackspam
Invalid user support from 179.108.179.237 port 63981
2019-10-24 22:33:42
139.155.34.87 attackspambots
Invalid user support from 139.155.34.87 port 39278
2019-10-24 23:06:08
92.46.223.98 attackbotsspam
Invalid user zimbra from 92.46.223.98 port 26788
2019-10-24 23:15:51

Recently Reported IPs

104.248.20.158 104.248.200.131 104.248.200.136 104.248.200.157
104.248.200.176 104.248.200.1 104.248.200.189 104.248.200.183
104.248.200.184 104.248.200.186 109.81.181.136 104.248.200.201
104.248.200.202 104.248.200.219 104.248.200.223 104.248.200.245
104.248.200.242 104.248.200.232 104.248.201.155 104.248.200.89