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

Internet Service Provider: Amazon Technologies Inc.

Hostname: unknown

Organization: unknown

Usage Type: Data Center/Web Hosting/Transit

Comments:
Type Details Datetime
attackspam
Feb  2 07:07:28 [munged] sshd[2995]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=3.12.45.0
2020-02-02 18:16:38
attack
Unauthorized connection attempt detected from IP address 3.12.45.0 to port 2220 [J]
2020-01-27 21:46:11
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 3.12.45.0
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 44502
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;3.12.45.0.			IN	A

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

;; Query time: 101 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jan 27 21:46:07 CST 2020
;; MSG SIZE  rcvd: 113
Host info
0.45.12.3.in-addr.arpa domain name pointer ec2-3-12-45-0.us-east-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
0.45.12.3.in-addr.arpa	name = ec2-3-12-45-0.us-east-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
213.97.62.3 attack
Unauthorized connection attempt detected from IP address 213.97.62.3 to port 22
2020-01-06 02:13:32
156.96.151.237 attackspambots
Unauthorized connection attempt detected from IP address 156.96.151.237 to port 25 [J]
2020-01-06 02:23:04
181.129.112.130 attack
Unauthorized connection attempt detected from IP address 181.129.112.130 to port 445
2020-01-06 02:21:06
75.144.62.81 attack
Unauthorized connection attempt detected from IP address 75.144.62.81 to port 9000 [J]
2020-01-06 02:04:46
95.245.201.103 attack
Unauthorized connection attempt detected from IP address 95.245.201.103 to port 80 [J]
2020-01-06 02:27:19
177.188.199.178 attackbotsspam
Unauthorized connection attempt detected from IP address 177.188.199.178 to port 8080
2020-01-06 01:54:18
196.219.91.150 attackbotsspam
Unauthorized connection attempt detected from IP address 196.219.91.150 to port 22
2020-01-06 01:48:51
193.227.11.123 attackbots
Unauthorized connection attempt detected from IP address 193.227.11.123 to port 445
2020-01-06 01:49:56
78.189.142.189 attackbots
Unauthorized connection attempt detected from IP address 78.189.142.189 to port 23
2020-01-06 02:03:14
93.115.148.228 attackspam
Unauthorized connection attempt detected from IP address 93.115.148.228 to port 23 [J]
2020-01-06 02:28:27
122.114.75.90 attackbotsspam
Jan  5 16:45:27 master sshd[23117]: Failed password for invalid user hadoop from 122.114.75.90 port 52232 ssh2
2020-01-06 02:24:43
217.208.141.71 attackbotsspam
Unauthorized connection attempt detected from IP address 217.208.141.71 to port 23 [J]
2020-01-06 02:13:13
186.38.56.3 attackbots
Unauthorized connection attempt detected from IP address 186.38.56.3 to port 88 [J]
2020-01-06 02:19:38
41.41.66.19 attackbots
Unauthorized connection attempt detected from IP address 41.41.66.19 to port 22
2020-01-06 02:09:35
74.95.164.190 attack
Unauthorized connection attempt detected from IP address 74.95.164.190 to port 3389
2020-01-06 02:05:02

Recently Reported IPs

41.65.112.50 101.53.102.213 84.42.47.163 189.175.163.71
183.129.211.18 77.179.184.69 200.60.145.230 185.39.163.69
219.95.75.225 49.144.67.86 192.99.210.172 103.19.59.2
139.59.20.94 109.99.168.234 139.180.192.108 40.122.55.174
164.47.122.28 199.71.188.9 109.203.205.66 91.203.193.251