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: None

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

;; QUESTION SECTION:
;104.22.1.124.			IN	A

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

;; Query time: 57 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Mar 05 01:16:55 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 124.1.22.104.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 124.1.22.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
129.213.36.226 attackbotsspam
Invalid user pi from 129.213.36.226 port 45244
2020-01-17 04:11:12
180.89.58.27 attackspambots
$f2bV_matches
2020-01-17 04:03:59
178.128.21.38 attack
Jan 16 10:15:38 server sshd\[20297\]: Failed password for invalid user fbm from 178.128.21.38 port 58290 ssh2
Jan 16 21:52:44 server sshd\[2665\]: Invalid user prueba from 178.128.21.38
Jan 16 21:52:44 server sshd\[2665\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=emr.teravibe.com 
Jan 16 21:52:46 server sshd\[2665\]: Failed password for invalid user prueba from 178.128.21.38 port 52114 ssh2
Jan 16 22:07:06 server sshd\[6357\]: Invalid user admin from 178.128.21.38
Jan 16 22:07:06 server sshd\[6357\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=emr.teravibe.com 
...
2020-01-17 04:05:06
103.75.48.179 attackbots
Invalid user pi from 103.75.48.179 port 55988
2020-01-17 04:18:32
129.204.94.79 attack
Jan 16 20:23:47 vps691689 sshd[19407]: Failed password for root from 129.204.94.79 port 46078 ssh2
Jan 16 20:26:30 vps691689 sshd[19502]: Failed password for root from 129.204.94.79 port 43018 ssh2
...
2020-01-17 04:11:25
197.32.33.166 attackspam
Invalid user admin from 197.32.33.166 port 48836
2020-01-17 04:01:29
101.255.52.171 attack
SSH Brute Force
2020-01-17 03:53:09
159.203.88.67 attackspam
Invalid user oracle from 159.203.88.67 port 42572
2020-01-17 04:06:16
37.187.104.135 attack
Jan 16 17:35:21 unicornsoft sshd\[3733\]: Invalid user den from 37.187.104.135
Jan 16 17:35:21 unicornsoft sshd\[3733\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.187.104.135
Jan 16 17:35:23 unicornsoft sshd\[3733\]: Failed password for invalid user den from 37.187.104.135 port 40258 ssh2
2020-01-17 04:22:55
37.182.164.249 attack
Unauthorized connection attempt detected from IP address 37.182.164.249 to port 2220 [J]
2020-01-17 04:23:09
122.51.162.201 attack
Invalid user tjones from 122.51.162.201 port 52654
2020-01-17 04:13:11
49.234.179.127 attackspam
Invalid user g from 49.234.179.127 port 45988
2020-01-17 03:55:29
144.217.7.75 attackspam
Invalid user ubuntu from 144.217.7.75 port 60030
2020-01-17 04:08:30
150.223.17.117 attack
Unauthorized connection attempt detected from IP address 150.223.17.117 to port 2220 [J]
2020-01-17 04:07:19
211.24.110.125 attackspambots
SSH Brute-Force reported by Fail2Ban
2020-01-17 03:59:02

Recently Reported IPs

104.219.26.29 104.219.72.122 104.22.0.246 104.22.1.12
114.37.28.221 104.22.10.158 104.22.1.246 104.22.10.73
104.22.10.243 104.22.10.32 104.22.11.243 104.22.11.158
104.22.10.97 104.22.10.198 104.22.11.32 104.22.11.97
104.22.11.73 104.22.12.180 104.22.12.55 104.22.11.198