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:
IP Type Details Datetime
3.0.22.213 attack
2020-05-22T09:57:36.886926dmca.cloudsearch.cf sshd[4691]: Invalid user Tlhua from 3.0.22.213 port 60606
2020-05-22T09:57:36.892693dmca.cloudsearch.cf sshd[4691]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=ec2-3-0-22-213.ap-southeast-1.compute.amazonaws.com
2020-05-22T09:57:36.886926dmca.cloudsearch.cf sshd[4691]: Invalid user Tlhua from 3.0.22.213 port 60606
2020-05-22T09:57:38.499108dmca.cloudsearch.cf sshd[4691]: Failed password for invalid user Tlhua from 3.0.22.213 port 60606 ssh2
2020-05-22T10:05:41.741374dmca.cloudsearch.cf sshd[5313]: Invalid user ep from 3.0.22.213 port 45170
2020-05-22T10:05:41.747545dmca.cloudsearch.cf sshd[5313]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=ec2-3-0-22-213.ap-southeast-1.compute.amazonaws.com
2020-05-22T10:05:41.741374dmca.cloudsearch.cf sshd[5313]: Invalid user ep from 3.0.22.213 port 45170
2020-05-22T10:05:43.606534dmca.cloudsearch.cf sshd[5313]: Failed 
...
2020-05-22 19:14:36
3.0.22.213 attack
May 18 20:26:11 xeon sshd[34346]: Failed password for invalid user myq from 3.0.22.213 port 43518 ssh2
2020-05-20 01:24:44
3.0.223.188 attack
WordPress brute force
2020-03-08 06:07:15
3.0.245.124 attackbots
Unauthorized connection attempt detected from IP address 3.0.245.124 to port 2220 [J]
2020-02-03 20:28:25
3.0.2.221 attackspambots
Unauthorized connection attempt detected from IP address 3.0.2.221 to port 2220 [J]
2020-01-27 13:53:33
3.0.2.221 attack
Unauthorized connection attempt detected from IP address 3.0.2.221 to port 2220 [J]
2020-01-22 23:15:14
3.0.245.124 attack
$f2bV_matches
2020-01-22 02:29:22
3.0.245.124 attack
Unauthorized connection attempt detected from IP address 3.0.245.124 to port 2220 [J]
2020-01-13 02:57:39
3.0.221.80 attackbotsspam
SMTP/25/465/587-993/995 Probe, Reject, BadAuth, Hack, SPAM -
2019-07-09 00:44:00
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 3.0.2.81
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 23828
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;3.0.2.81.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 27 19:12:45 CST 2025
;; MSG SIZE  rcvd: 101
Host info
81.2.0.3.in-addr.arpa domain name pointer ec2-3-0-2-81.ap-southeast-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
81.2.0.3.in-addr.arpa	name = ec2-3-0-2-81.ap-southeast-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
136.243.142.18 attack
Oct  6 10:54:00 ms-srv sshd[16250]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=136.243.142.18  user=root
Oct  6 10:54:03 ms-srv sshd[16250]: Failed password for invalid user root from 136.243.142.18 port 33542 ssh2
2020-10-06 18:48:25
107.181.228.250 attack
 TCP (SYN) 107.181.228.250:1259 -> port 1433, len 52
2020-10-06 18:17:20
31.23.147.255 attackbotsspam
445/tcp
[2020-10-05]1pkt
2020-10-06 18:51:21
188.114.102.62 attackspambots
srv02 DDoS Malware Target(80:http) ..
2020-10-06 18:23:39
105.29.155.182 normal
Need to get some school work done of grade 1.2
2020-10-06 18:14:23
103.133.109.40 attackbotsspam
Oct  6 08:53:26 ns308116 postfix/smtpd[31001]: warning: unknown[103.133.109.40]: SASL LOGIN authentication failed: authentication failure
Oct  6 08:53:26 ns308116 postfix/smtpd[31001]: warning: unknown[103.133.109.40]: SASL LOGIN authentication failed: authentication failure
Oct  6 08:53:27 ns308116 postfix/smtpd[31001]: warning: unknown[103.133.109.40]: SASL LOGIN authentication failed: authentication failure
Oct  6 08:53:27 ns308116 postfix/smtpd[31001]: warning: unknown[103.133.109.40]: SASL LOGIN authentication failed: authentication failure
Oct  6 08:53:28 ns308116 postfix/smtpd[31001]: warning: unknown[103.133.109.40]: SASL LOGIN authentication failed: authentication failure
Oct  6 08:53:28 ns308116 postfix/smtpd[31001]: warning: unknown[103.133.109.40]: SASL LOGIN authentication failed: authentication failure
...
2020-10-06 18:37:17
222.95.180.220 attackbots
23/tcp
[2020-10-05]1pkt
2020-10-06 18:47:10
173.92.67.203 attackspambots
445/tcp 445/tcp
[2020-10-05]2pkt
2020-10-06 18:44:07
117.50.49.57 attackspam
Invalid user test2 from 117.50.49.57 port 51428
2020-10-06 18:32:26
187.162.28.163 attack
23/tcp 23/tcp 23/tcp...
[2020-10-05]4pkt,1pt.(tcp)
2020-10-06 18:26:07
139.99.203.12 attack
$f2bV_matches
2020-10-06 18:20:20
140.143.19.237 attackspambots
Oct  6 11:33:59 router sshd[20439]: Failed password for root from 140.143.19.237 port 52966 ssh2
Oct  6 11:37:41 router sshd[20460]: Failed password for root from 140.143.19.237 port 35880 ssh2
...
2020-10-06 18:35:29
59.33.37.158 attackspambots
1433/tcp
[2020-10-05]1pkt
2020-10-06 18:22:49
186.88.92.175 attackbotsspam
1601930292 - 10/05/2020 22:38:12 Host: 186.88.92.175/186.88.92.175 Port: 445 TCP Blocked
2020-10-06 18:38:08
186.147.160.189 attackbots
DATE:2020-10-06 10:51:25, IP:186.147.160.189, PORT:ssh SSH brute force auth (docker-dc)
2020-10-06 18:27:43

Recently Reported IPs

130.91.113.177 172.235.132.118 202.4.16.2 117.35.120.198
18.31.111.103 115.142.184.114 85.234.188.22 25.198.11.232
7.23.67.230 22.218.165.190 16.171.54.89 96.183.131.100
176.21.128.121 212.6.24.61 249.25.197.71 206.197.225.34
150.70.61.233 244.111.252.236 200.184.251.33 33.143.124.205