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 of America (the)

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

;; QUESTION SECTION:
;47.214.21.49.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jan 26 05:10:16 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 49.21.214.47.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 49.21.214.47.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
139.99.78.208 attackspam
Oct  6 09:46:05 vps01 sshd[21340]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.99.78.208
Oct  6 09:46:08 vps01 sshd[21340]: Failed password for invalid user Qq@123 from 139.99.78.208 port 38728 ssh2
2019-10-06 16:09:40
185.160.62.221 attackbots
" "
2019-10-06 16:02:30
174.138.26.48 attack
Oct  5 22:01:09 sachi sshd\[4855\]: Invalid user Ronald@123 from 174.138.26.48
Oct  5 22:01:09 sachi sshd\[4855\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.26.48
Oct  5 22:01:11 sachi sshd\[4855\]: Failed password for invalid user Ronald@123 from 174.138.26.48 port 46030 ssh2
Oct  5 22:06:55 sachi sshd\[23750\]: Invalid user P@\$\$w0rt0101 from 174.138.26.48
Oct  5 22:06:55 sachi sshd\[23750\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.26.48
2019-10-06 16:12:34
152.136.84.139 attackspambots
Oct  6 06:48:05 markkoudstaal sshd[5897]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.136.84.139
Oct  6 06:48:07 markkoudstaal sshd[5897]: Failed password for invalid user JeanPaul from 152.136.84.139 port 53190 ssh2
Oct  6 06:53:51 markkoudstaal sshd[6412]: Failed password for root from 152.136.84.139 port 36556 ssh2
2019-10-06 16:10:53
62.219.160.251 attackbotsspam
Automatic report - Port Scan Attack
2019-10-06 16:19:38
112.84.61.63 attackspam
Brute force SMTP login attempts.
2019-10-06 15:53:02
46.105.99.163 attackspam
SS5,DEF GET //wp-login.php
2019-10-06 15:54:59
210.112.97.19 attackbots
[Sun Oct 06 00:49:04.653601 2019] [:error] [pid 92610] [client 210.112.97.19:55796] [client 210.112.97.19] ModSecurity: Access denied with code 403 (phase 2). Operator GE matched 5 at TX:anomaly_score. [file "/usr/share/modsecurity-crs/rules/REQUEST-949-BLOCKING-EVALUATION.conf"] [line "91"] [id "949110"] [msg "Inbound Anomaly Score Exceeded (Total Score: 8)"] [severity "CRITICAL"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-generic"] [hostname "200.132.59.212"] [uri "/public/index.php"] [unique_id "XZlkMOdR3fmuIP0nmsqPfAAAAAI"]
...
2019-10-06 16:12:17
23.129.64.161 attack
Oct  6 08:57:03 vpn01 sshd[9053]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=23.129.64.161
Oct  6 08:57:05 vpn01 sshd[9053]: Failed password for invalid user admin from 23.129.64.161 port 58553 ssh2
...
2019-10-06 15:56:26
123.214.231.90 attackbotsspam
Oct  6 05:49:58 mc1 kernel: \[1620204.025153\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=123.214.231.90 DST=159.69.205.51 LEN=52 TOS=0x00 PREC=0x00 TTL=115 ID=139 DF PROTO=TCP SPT=10408 DPT=1433 WINDOW=8192 RES=0x00 SYN URGP=0 
Oct  6 05:50:01 mc1 kernel: \[1620207.035496\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=123.214.231.90 DST=159.69.205.51 LEN=52 TOS=0x00 PREC=0x00 TTL=115 ID=1180 DF PROTO=TCP SPT=10408 DPT=1433 WINDOW=8192 RES=0x00 SYN URGP=0 
Oct  6 05:50:07 mc1 kernel: \[1620213.045444\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=123.214.231.90 DST=159.69.205.51 LEN=48 TOS=0x00 PREC=0x00 TTL=115 ID=3256 DF PROTO=TCP SPT=10408 DPT=1433 WINDOW=65535 RES=0x00 SYN URGP=0 
...
2019-10-06 15:42:39
193.29.15.185 attackbots
Scanning random ports - tries to find possible vulnerable services
2019-10-06 15:59:21
125.35.93.62 attackspam
Brute force attempt
2019-10-06 16:05:30
49.88.112.114 attackspam
2019-10-06T08:09:28.647812abusebot.cloudsearch.cf sshd\[22013\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.114  user=root
2019-10-06 16:15:07
195.43.189.10 attackspambots
Oct  6 06:41:04 piServer sshd[17621]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.43.189.10
Oct  6 06:41:06 piServer sshd[17621]: Failed password for invalid user P@$$wort1! from 195.43.189.10 port 33682 ssh2
Oct  6 06:44:33 piServer sshd[17844]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.43.189.10
...
2019-10-06 15:58:26
185.130.56.71 attackspam
nginx-botsearch jail
2019-10-06 16:09:15

Recently Reported IPs

156.128.83.238 165.111.244.88 55.44.90.16 88.122.26.137
77.184.106.151 239.239.77.103 227.35.206.43 14.146.222.74
246.246.153.99 13.93.13.215 221.139.105.105 166.115.0.248
118.97.208.65 61.13.152.54 220.196.30.63 70.203.178.76
120.132.222.211 142.132.128.51 188.156.119.27 194.83.102.99