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:
IP Type Details Datetime
104.248.30.249 attackspambots
Nov 10 16:31:00 legacy sshd[31148]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.30.249
Nov 10 16:31:02 legacy sshd[31148]: Failed password for invalid user administrator from 104.248.30.249 port 34712 ssh2
Nov 10 16:34:24 legacy sshd[31253]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.30.249
...
2019-11-10 23:42:14
104.248.30.249 attackbots
2019-10-26T21:29:29.896816abusebot-3.cloudsearch.cf sshd\[14340\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.30.249  user=root
2019-10-27 05:54:19
104.248.30.249 attack
Oct 24 08:31:16 minden010 sshd[8490]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.30.249
Oct 24 08:31:18 minden010 sshd[8490]: Failed password for invalid user homerj from 104.248.30.249 port 38342 ssh2
Oct 24 08:34:38 minden010 sshd[11076]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.30.249
...
2019-10-24 14:36:46
104.248.30.249 attackspam
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.30.249  user=root
Failed password for root from 104.248.30.249 port 44632 ssh2
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.30.249  user=root
Failed password for root from 104.248.30.249 port 38940 ssh2
Invalid user wedding from 104.248.30.249 port 50310
2019-10-21 04:59:36
104.248.30.249 attack
$f2bV_matches
2019-10-16 07:02:34
104.248.30.249 attack
2019-10-15T13:18:18.069840abusebot-3.cloudsearch.cf sshd\[25340\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.30.249  user=root
2019-10-15 21:30:00
104.248.30.249 attackspambots
Oct  6 18:46:19 vmanager6029 sshd\[24481\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.30.249  user=root
Oct  6 18:46:22 vmanager6029 sshd\[24481\]: Failed password for root from 104.248.30.249 port 36106 ssh2
Oct  6 18:49:49 vmanager6029 sshd\[24532\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.30.249  user=root
2019-10-07 01:12:03
104.248.30.249 attackbots
Sep 27 07:49:00 MK-Soft-VM7 sshd[5909]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.30.249 
Sep 27 07:49:02 MK-Soft-VM7 sshd[5909]: Failed password for invalid user magda from 104.248.30.249 port 56732 ssh2
...
2019-09-27 18:55:36
104.248.30.249 attackspam
Automatic report - Banned IP Access
2019-09-20 06:58:10
104.248.30.249 attackspam
Sep 19 08:44:59 ny01 sshd[3004]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.30.249
Sep 19 08:45:01 ny01 sshd[3004]: Failed password for invalid user paula from 104.248.30.249 port 40220 ssh2
Sep 19 08:48:43 ny01 sshd[3635]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.30.249
2019-09-20 03:30:42
104.248.30.249 attackbotsspam
Sep  5 22:34:49 ny01 sshd[17352]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.30.249
Sep  5 22:34:51 ny01 sshd[17352]: Failed password for invalid user ubuntu from 104.248.30.249 port 38848 ssh2
Sep  5 22:38:25 ny01 sshd[18159]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.30.249
2019-09-06 10:42:08
104.248.30.249 attackbotsspam
Sep  2 13:22:47 rotator sshd\[29227\]: Invalid user york from 104.248.30.249Sep  2 13:22:49 rotator sshd\[29227\]: Failed password for invalid user york from 104.248.30.249 port 54934 ssh2Sep  2 13:26:36 rotator sshd\[30030\]: Invalid user gyc from 104.248.30.249Sep  2 13:26:39 rotator sshd\[30030\]: Failed password for invalid user gyc from 104.248.30.249 port 43844 ssh2Sep  2 13:30:25 rotator sshd\[30805\]: Invalid user maria from 104.248.30.249Sep  2 13:30:27 rotator sshd\[30805\]: Failed password for invalid user maria from 104.248.30.249 port 60990 ssh2
...
2019-09-02 20:44:06
104.248.30.249 attack
Aug 26 07:05:48 plex sshd[10700]: Invalid user magento from 104.248.30.249 port 44758
2019-08-26 14:04:19
104.248.30.249 attackspambots
SSH Brute-Forcing (ownc)
2019-08-19 10:04:45
104.248.30.249 attack
Jul 11 14:07:19 dallas01 sshd[30136]: Failed password for invalid user test from 104.248.30.249 port 33856 ssh2
Jul 11 14:08:39 dallas01 sshd[30279]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.30.249
Jul 11 14:08:41 dallas01 sshd[30279]: Failed password for invalid user as from 104.248.30.249 port 50428 ssh2
Jul 11 14:09:59 dallas01 sshd[30642]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.30.249
2019-07-31 17:45:03
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.248.30.163
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 53068
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;104.248.30.163.			IN	A

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

;; Query time: 70 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Apr 03 06:09:54 CST 2022
;; MSG SIZE  rcvd: 107
Host info
163.30.248.104.in-addr.arpa domain name pointer enklereliv.no.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
163.30.248.104.in-addr.arpa	name = enklereliv.no.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
177.170.142.2 attackspambots
Unauthorized connection attempt detected from IP address 177.170.142.2 to port 23 [J]
2020-02-05 18:11:42
159.65.158.30 attackbots
Unauthorized connection attempt detected from IP address 159.65.158.30 to port 2220 [J]
2020-02-05 17:47:50
114.236.202.7 attack
Unauthorized connection attempt detected from IP address 114.236.202.7 to port 6656 [J]
2020-02-05 17:51:24
186.251.94.109 attackbotsspam
Unauthorized connection attempt detected from IP address 186.251.94.109 to port 8080 [J]
2020-02-05 17:42:10
200.84.55.63 attackspambots
Unauthorized connection attempt detected from IP address 200.84.55.63 to port 8080 [J]
2020-02-05 17:40:07
200.194.36.217 attackbotsspam
Unauthorized connection attempt detected from IP address 200.194.36.217 to port 23 [J]
2020-02-05 18:08:25
175.136.184.195 attackspambots
Unauthorized connection attempt detected from IP address 175.136.184.195 to port 80 [J]
2020-02-05 17:46:27
220.120.10.181 attackspambots
Unauthorized connection attempt detected from IP address 220.120.10.181 to port 2004 [J]
2020-02-05 18:06:42
95.59.145.108 attackspam
Unauthorized connection attempt detected from IP address 95.59.145.108 to port 23 [J]
2020-02-05 17:54:40
185.109.251.37 attackbotsspam
Unauthorized connection attempt detected from IP address 185.109.251.37 to port 23 [J]
2020-02-05 17:43:04
14.29.147.131 attack
Unauthorized connection attempt detected from IP address 14.29.147.131 to port 2220 [J]
2020-02-05 18:03:37
43.228.65.43 attack
Unauthorized connection attempt detected from IP address 43.228.65.43 to port 1433 [J]
2020-02-05 18:00:34
114.231.42.184 attackbotsspam
Unauthorized connection attempt detected from IP address 114.231.42.184 to port 3389 [J]
2020-02-05 17:51:44
23.129.64.157 attackbotsspam
Unauthorized connection attempt detected from IP address 23.129.64.157 to port 122 [J]
2020-02-05 17:35:05
210.7.13.166 attack
Unauthorized connection attempt detected from IP address 210.7.13.166 to port 23 [J]
2020-02-05 18:07:40

Recently Reported IPs

104.248.25.17 104.248.32.221 104.248.36.150 104.248.36.220
104.248.40.75 104.248.53.181 104.248.57.173 104.248.58.15
104.248.83.9 104.248.87.242 104.248.9.225 104.248.90.125
104.248.91.49 104.248.92.190 106.1.104.119 106.1.149.252
106.1.18.97 106.1.20.205 106.102.0.233 106.102.0.248