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

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

;; QUESTION SECTION:
;3.107.136.214.			IN	A

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

;; Query time: 38 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 04 01:54:00 CST 2025
;; MSG SIZE  rcvd: 106
Host info
214.136.107.3.in-addr.arpa domain name pointer ec2-3-107-136-214.ap-southeast-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
214.136.107.3.in-addr.arpa	name = ec2-3-107-136-214.ap-southeast-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
132.232.7.197 attackbots
Dec 31 05:26:52 localhost sshd\[113128\]: Invalid user im from 132.232.7.197 port 39712
Dec 31 05:26:52 localhost sshd\[113128\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.7.197
Dec 31 05:26:53 localhost sshd\[113128\]: Failed password for invalid user im from 132.232.7.197 port 39712 ssh2
Dec 31 05:30:15 localhost sshd\[113222\]: Invalid user demo from 132.232.7.197 port 37222
Dec 31 05:30:15 localhost sshd\[113222\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.7.197
...
2019-12-31 13:39:34
77.247.108.238 attackbotsspam
Dec 31 05:55:35 debian-2gb-nbg1-2 kernel: \[27470.668579\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=77.247.108.238 DST=195.201.40.59 LEN=444 TOS=0x00 PREC=0x00 TTL=51 ID=57243 DF PROTO=UDP SPT=5253 DPT=50601 LEN=424
2019-12-31 14:03:16
180.180.100.65 attack
Automatic report - Port Scan Attack
2019-12-31 14:13:58
183.87.215.180 attack
Unauthorized connection attempt detected from IP address 183.87.215.180 to port 445
2019-12-31 14:15:07
60.13.241.118 attack
Unauthorised access (Dec 31) SRC=60.13.241.118 LEN=52 TTL=112 ID=32073 DF TCP DPT=445 WINDOW=8192 SYN
2019-12-31 13:46:30
182.74.68.58 attack
Unauthorized connection attempt detected from IP address 182.74.68.58 to port 445
2019-12-31 14:01:30
86.242.29.0 attackbots
Dec 31 05:52:27 ns382633 sshd\[13326\]: Invalid user admin from 86.242.29.0 port 57196
Dec 31 05:52:27 ns382633 sshd\[13326\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=86.242.29.0
Dec 31 05:52:29 ns382633 sshd\[13326\]: Failed password for invalid user admin from 86.242.29.0 port 57196 ssh2
Dec 31 05:56:16 ns382633 sshd\[14076\]: Invalid user ubuntu from 86.242.29.0 port 58344
Dec 31 05:56:16 ns382633 sshd\[14076\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=86.242.29.0
2019-12-31 13:39:57
85.10.22.166 attackbotsspam
Automatic report - XMLRPC Attack
2019-12-31 14:06:41
112.85.42.172 attack
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.172  user=root
Failed password for root from 112.85.42.172 port 4437 ssh2
Failed password for root from 112.85.42.172 port 4437 ssh2
Failed password for root from 112.85.42.172 port 4437 ssh2
Failed password for root from 112.85.42.172 port 4437 ssh2
2019-12-31 13:41:53
54.243.10.114 attack
Automatic report - XMLRPC Attack
2019-12-31 14:06:09
188.226.171.36 attack
Dec 31 05:56:07 mout sshd[28047]: Invalid user yuechu from 188.226.171.36 port 52064
2019-12-31 13:44:56
122.51.115.226 attackspambots
Invalid user oseas from 122.51.115.226 port 57274
2019-12-31 14:17:38
138.99.6.65 attack
Dec 31 00:31:23 server sshd\[12801\]: Invalid user vestrum from 138.99.6.65
Dec 31 00:31:23 server sshd\[12801\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.99.6.65 
Dec 31 00:31:25 server sshd\[12801\]: Failed password for invalid user vestrum from 138.99.6.65 port 58436 ssh2
Dec 31 07:55:54 server sshd\[21881\]: Invalid user user1 from 138.99.6.65
Dec 31 07:55:54 server sshd\[21881\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.99.6.65 
...
2019-12-31 13:51:58
94.218.199.21 attackbotsspam
Dec 31 05:55:42 pornomens sshd\[14040\]: Invalid user mysql from 94.218.199.21 port 36760
Dec 31 05:55:42 pornomens sshd\[14040\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.218.199.21
Dec 31 05:55:44 pornomens sshd\[14040\]: Failed password for invalid user mysql from 94.218.199.21 port 36760 ssh2
...
2019-12-31 13:56:41
106.12.99.173 attackspam
Dec 31 05:55:38 MK-Soft-VM5 sshd[30796]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.99.173 
Dec 31 05:55:40 MK-Soft-VM5 sshd[30796]: Failed password for invalid user mysql from 106.12.99.173 port 43362 ssh2
...
2019-12-31 13:57:27

Recently Reported IPs

119.104.195.155 208.150.12.86 242.126.109.3 192.24.187.114
119.1.154.14 59.150.182.110 97.134.194.153 35.23.154.120
14.49.159.217 208.130.71.137 243.180.137.212 35.209.146.97
2.23.195.136 3.133.17.37 14.103.137.230 59.140.243.30
127.109.69.178 87.3.7.10 24.187.192.254 152.109.146.26