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

;; QUESTION SECTION:
;104.21.48.122.			IN	A

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

;; Query time: 55 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 17 23:03:10 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 122.48.21.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 122.48.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
106.124.143.24 attack
2020-04-08T21:40:31.784305abusebot-5.cloudsearch.cf sshd[2429]: Invalid user rupesh from 106.124.143.24 port 51764
2020-04-08T21:40:31.791603abusebot-5.cloudsearch.cf sshd[2429]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.124.143.24
2020-04-08T21:40:31.784305abusebot-5.cloudsearch.cf sshd[2429]: Invalid user rupesh from 106.124.143.24 port 51764
2020-04-08T21:40:33.154061abusebot-5.cloudsearch.cf sshd[2429]: Failed password for invalid user rupesh from 106.124.143.24 port 51764 ssh2
2020-04-08T21:48:46.368220abusebot-5.cloudsearch.cf sshd[2579]: Invalid user test from 106.124.143.24 port 46775
2020-04-08T21:48:46.374257abusebot-5.cloudsearch.cf sshd[2579]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.124.143.24
2020-04-08T21:48:46.368220abusebot-5.cloudsearch.cf sshd[2579]: Invalid user test from 106.124.143.24 port 46775
2020-04-08T21:48:48.358777abusebot-5.cloudsearch.cf sshd[2579]: Failed
...
2020-04-09 08:22:48
36.111.184.80 attackbotsspam
Apr  6 08:59:39 cloud sshd[1081]: Failed password for root from 36.111.184.80 port 42286 ssh2
Apr  8 23:49:00 cloud sshd[26203]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.111.184.80
2020-04-09 08:14:16
190.8.149.146 attack
Ssh brute force
2020-04-09 08:19:24
93.235.95.58 attackspambots
RDP Brute-Force
2020-04-09 07:54:31
134.122.29.53 attackspambots
SSH bruteforce (Triggered fail2ban)
2020-04-09 08:15:21
212.198.136.3 attack
RDP Brute-Force
2020-04-09 07:50:49
185.86.164.106 attackspambots
Website administration hacking try
2020-04-09 08:19:44
111.249.37.176 attack
Hits on port : 5555
2020-04-09 08:11:06
167.114.3.105 attackspam
Apr  9 00:39:21 vserver sshd\[22295\]: Invalid user tester from 167.114.3.105Apr  9 00:39:23 vserver sshd\[22295\]: Failed password for invalid user tester from 167.114.3.105 port 37666 ssh2Apr  9 00:44:31 vserver sshd\[22327\]: Invalid user mcserver from 167.114.3.105Apr  9 00:44:33 vserver sshd\[22327\]: Failed password for invalid user mcserver from 167.114.3.105 port 39428 ssh2
...
2020-04-09 08:06:22
172.255.81.176 attackspambots
(From eric@talkwithwebvisitor.com) Hey, my name’s Eric and for just a second, imagine this…

- Someone does a search and winds up at castelluccichiropractic.com.

- They hang out for a minute to check it out.  “I’m interested… but… maybe…”

- And then they hit the back button and check out the other search results instead. 

- Bottom line – you got an eyeball, but nothing else to show for it.

- There they go.

This isn’t really your fault – it happens a LOT – studies show 7 out of 10 visitors to any site disappear without leaving a trace.

But you CAN fix that.

Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number.  It lets you know right then and there – enabling you to call that lead while they’re literally looking over your site.

CLICK HERE http://www.talkwithwebvisitor.com to try out a Live Demo with Talk With Web Visitor now to see exactly how it works.

Time is money when it comes to connecting wit
2020-04-09 07:59:35
222.186.173.215 attackbots
Apr  9 01:40:36 odroid64 sshd\[1619\]: User root from 222.186.173.215 not allowed because not listed in AllowUsers
Apr  9 01:40:37 odroid64 sshd\[1619\]: Failed none for invalid user root from 222.186.173.215 port 53408 ssh2
...
2020-04-09 07:45:31
188.166.251.156 attack
Apr  9 00:58:46  sshd[32287]: Failed password for invalid user licongcong from 188.166.251.156 port 59046 ssh2
2020-04-09 08:07:34
49.236.203.163 attackspambots
Apr  8 23:45:13 meumeu sshd[18739]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.236.203.163 
Apr  8 23:45:14 meumeu sshd[18739]: Failed password for invalid user user from 49.236.203.163 port 38214 ssh2
Apr  8 23:49:25 meumeu sshd[19282]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.236.203.163 
...
2020-04-09 07:38:52
88.218.17.185 attackspambots
RDP Brute-Force
2020-04-09 08:07:06
187.38.26.173 attack
$f2bV_matches
2020-04-09 08:21:26

Recently Reported IPs

43.202.205.208 104.21.48.123 104.21.48.129 104.21.48.131
104.21.48.132 104.21.48.135 242.207.220.58 104.21.48.137
104.21.48.140 104.21.48.141 104.21.48.142 104.21.48.143
104.21.48.144 104.21.48.146 104.21.48.153 104.21.48.158
104.21.48.160 104.21.48.164 104.21.48.166 104.21.48.170