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

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

;; QUESTION SECTION:
;43.80.99.221.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 22 03:28:12 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 221.99.80.43.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 221.99.80.43.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
5.66.110.247 attackspambots
Automatic report - Port Scan Attack
2019-10-14 07:52:41
62.210.252.184 attack
2019-10-14T03:11:15.931064enmeeting.mahidol.ac.th sshd\[1375\]: User root from 62-210-252-184.rev.poneytelecom.eu not allowed because not listed in AllowUsers
2019-10-14T03:11:16.057960enmeeting.mahidol.ac.th sshd\[1375\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62-210-252-184.rev.poneytelecom.eu  user=root
2019-10-14T03:11:18.695276enmeeting.mahidol.ac.th sshd\[1375\]: Failed password for invalid user root from 62.210.252.184 port 55490 ssh2
...
2019-10-14 08:17:07
58.244.173.130 attack
Automatic report - Banned IP Access
2019-10-14 12:03:04
167.71.40.112 attack
Sep 21 15:40:03 yesfletchmain sshd\[29258\]: Invalid user deploy from 167.71.40.112 port 45248
Sep 21 15:40:03 yesfletchmain sshd\[29258\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.40.112
Sep 21 15:40:05 yesfletchmain sshd\[29258\]: Failed password for invalid user deploy from 167.71.40.112 port 45248 ssh2
Sep 21 15:44:02 yesfletchmain sshd\[29361\]: Invalid user uw from 167.71.40.112 port 58968
Sep 21 15:44:02 yesfletchmain sshd\[29361\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.40.112
...
2019-10-14 07:53:24
129.213.96.241 attackbotsspam
(sshd) Failed SSH login from 129.213.96.241 (US/United States/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Oct 14 00:38:24 server2 sshd[9844]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.213.96.241  user=root
Oct 14 00:38:27 server2 sshd[9844]: Failed password for root from 129.213.96.241 port 27448 ssh2
Oct 14 00:41:51 server2 sshd[9969]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.213.96.241  user=root
Oct 14 00:41:53 server2 sshd[9969]: Failed password for root from 129.213.96.241 port 48052 ssh2
Oct 14 00:45:25 server2 sshd[10048]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.213.96.241  user=root
2019-10-14 07:53:53
62.231.176.154 attackbots
Wordpress Admin Login attack
2019-10-14 07:51:24
103.139.12.24 attackbotsspam
Oct 14 01:58:09 vps01 sshd[9734]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.139.12.24
Oct 14 01:58:11 vps01 sshd[9734]: Failed password for invalid user Monster@2017 from 103.139.12.24 port 53181 ssh2
2019-10-14 08:12:26
167.71.197.133 attackspambots
Sep 21 02:57:05 yesfletchmain sshd\[6814\]: Invalid user tq from 167.71.197.133 port 42266
Sep 21 02:57:05 yesfletchmain sshd\[6814\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.197.133
Sep 21 02:57:07 yesfletchmain sshd\[6814\]: Failed password for invalid user tq from 167.71.197.133 port 42266 ssh2
Sep 21 03:01:17 yesfletchmain sshd\[6935\]: Invalid user testuser from 167.71.197.133 port 55168
Sep 21 03:01:17 yesfletchmain sshd\[6935\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.197.133
...
2019-10-14 08:09:48
139.199.20.202 attack
Oct 13 18:04:14 Tower sshd[31081]: Connection from 139.199.20.202 port 37440 on 192.168.10.220 port 22
Oct 13 18:04:16 Tower sshd[31081]: Failed password for root from 139.199.20.202 port 37440 ssh2
Oct 13 18:04:16 Tower sshd[31081]: Received disconnect from 139.199.20.202 port 37440:11: Bye Bye [preauth]
Oct 13 18:04:16 Tower sshd[31081]: Disconnected from authenticating user root 139.199.20.202 port 37440 [preauth]
2019-10-14 08:05:52
94.23.253.88 attackspam
10/13/2019-16:11:35.959493 94.23.253.88 Protocol: 17 ET SCAN Sipvicious Scan
2019-10-14 08:10:16
106.13.150.163 attack
Oct 13 22:02:30 heissa sshd\[8589\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.150.163  user=root
Oct 13 22:02:31 heissa sshd\[8589\]: Failed password for root from 106.13.150.163 port 52896 ssh2
Oct 13 22:06:50 heissa sshd\[9240\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.150.163  user=root
Oct 13 22:06:51 heissa sshd\[9240\]: Failed password for root from 106.13.150.163 port 35144 ssh2
Oct 13 22:11:09 heissa sshd\[9943\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.150.163  user=root
2019-10-14 08:22:28
1.10.179.94 attackbots
SSH invalid-user multiple login try
2019-10-14 08:24:33
51.68.189.69 attackbots
Oct 14 01:45:24 SilenceServices sshd[21932]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.68.189.69
Oct 14 01:45:26 SilenceServices sshd[21932]: Failed password for invalid user 123Kent from 51.68.189.69 port 40016 ssh2
Oct 14 01:49:30 SilenceServices sshd[24483]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.68.189.69
2019-10-14 08:02:52
141.98.10.62 attackspam
Oct 13 22:27:48 heicom postfix/smtpd\[834\]: warning: unknown\[141.98.10.62\]: SASL LOGIN authentication failed: authentication failure
Oct 13 22:52:39 heicom postfix/smtpd\[834\]: warning: unknown\[141.98.10.62\]: SASL LOGIN authentication failed: authentication failure
Oct 13 23:17:18 heicom postfix/smtpd\[834\]: warning: unknown\[141.98.10.62\]: SASL LOGIN authentication failed: authentication failure
Oct 13 23:41:55 heicom postfix/smtpd\[834\]: warning: unknown\[141.98.10.62\]: SASL LOGIN authentication failed: authentication failure
Oct 14 00:06:49 heicom postfix/smtpd\[2189\]: warning: unknown\[141.98.10.62\]: SASL LOGIN authentication failed: authentication failure
...
2019-10-14 08:12:00
167.114.246.179 attackspam
Feb 13 10:53:23 dillonfme sshd\[5455\]: Invalid user test from 167.114.246.179 port 40333
Feb 13 10:53:23 dillonfme sshd\[5455\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.114.246.179
Feb 13 10:53:25 dillonfme sshd\[5455\]: Failed password for invalid user test from 167.114.246.179 port 40333 ssh2
Feb 13 10:58:19 dillonfme sshd\[5616\]: Invalid user rabbit from 167.114.246.179 port 35877
Feb 13 10:58:19 dillonfme sshd\[5616\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.114.246.179
...
2019-10-14 08:18:58

Recently Reported IPs

155.28.183.216 9.231.166.175 36.142.71.53 1.37.46.113
78.60.143.179 161.70.68.159 254.169.123.87 55.124.7.56
224.50.118.220 166.241.143.158 204.44.116.132 51.153.248.224
62.180.159.151 22.139.27.242 98.16.185.27 74.64.227.24
90.249.106.44 159.77.133.10 218.205.102.33 222.142.152.164