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

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

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

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

;; Query time: 12 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Thu Jun 06 11:27:32 CST 2019
;; MSG SIZE  rcvd: 117

Host info
150.68.216.12.in-addr.arpa is an alias for 150.128-25.68.216.12.in-addr.arpa.
150.128-25.68.216.12.in-addr.arpa domain name pointer mail.generalprocurement.com.
Nslookup info:
Server:		67.207.67.2
Address:	67.207.67.2#53

Non-authoritative answer:
150.68.216.12.in-addr.arpa	canonical name = 150.128-25.68.216.12.in-addr.arpa.
150.128-25.68.216.12.in-addr.arpa	name = mail.generalprocurement.com.

Authoritative answers can be found from:

Related IP info:
Related comments:
IP Type Details Datetime
61.218.122.198 attackspam
$f2bV_matches
2020-04-03 05:54:12
185.103.51.85 attack
SASL PLAIN auth failed: ruser=...
2020-04-03 06:12:32
95.170.202.18 attack
ssh brute force, port scan
2020-04-03 05:45:33
139.219.9.120 attack
Apr  2 17:53:10 mail sshd\[42680\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.219.9.120  user=root
...
2020-04-03 06:03:21
222.186.180.8 attackspambots
Fail2Ban Ban Triggered
2020-04-03 05:56:08
47.89.18.71 attackspam
Apr  2 21:39:12 wordpress wordpress(www.ruhnke.cloud)[18032]: Blocked authentication attempt for admin from ::ffff:47.89.18.71
2020-04-03 05:52:18
111.161.74.100 attackbots
2020-04-02T21:45:13.331712shield sshd\[25357\]: Invalid user j from 111.161.74.100 port 48249
2020-04-02T21:45:13.336163shield sshd\[25357\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.161.74.100
2020-04-02T21:45:15.453837shield sshd\[25357\]: Failed password for invalid user j from 111.161.74.100 port 48249 ssh2
2020-04-02T21:47:54.794371shield sshd\[26129\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.161.74.100  user=root
2020-04-02T21:47:56.682028shield sshd\[26129\]: Failed password for root from 111.161.74.100 port 41234 ssh2
2020-04-03 05:53:43
123.207.74.24 attackbotsspam
Apr  2 23:46:54 meumeu sshd[25388]: Failed password for root from 123.207.74.24 port 33290 ssh2
Apr  2 23:49:10 meumeu sshd[25730]: Failed password for root from 123.207.74.24 port 58346 ssh2
...
2020-04-03 06:08:02
111.231.33.135 attackbots
Apr  2 23:48:04 eventyay sshd[15044]: Failed password for root from 111.231.33.135 port 45618 ssh2
Apr  2 23:50:34 eventyay sshd[15138]: Failed password for root from 111.231.33.135 port 48950 ssh2
...
2020-04-03 06:10:35
223.247.223.39 attack
Apr  2 21:47:10 vlre-nyc-1 sshd\[25010\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.247.223.39  user=root
Apr  2 21:47:11 vlre-nyc-1 sshd\[25010\]: Failed password for root from 223.247.223.39 port 58032 ssh2
Apr  2 21:52:58 vlre-nyc-1 sshd\[25157\]: Invalid user benjamin from 223.247.223.39
Apr  2 21:52:58 vlre-nyc-1 sshd\[25157\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.247.223.39
Apr  2 21:53:00 vlre-nyc-1 sshd\[25157\]: Failed password for invalid user benjamin from 223.247.223.39 port 33510 ssh2
...
2020-04-03 06:09:40
118.25.11.204 attackspam
[ssh] SSH attack
2020-04-03 05:48:14
139.99.45.201 attack
Automatic report - XMLRPC Attack
2020-04-03 06:20:07
61.155.234.38 attackbotsspam
Apr  2 23:53:01 prox sshd[21793]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.155.234.38 
Apr  2 23:53:03 prox sshd[21793]: Failed password for invalid user timson from 61.155.234.38 port 47536 ssh2
2020-04-03 06:09:07
103.81.156.10 attackspambots
Feb  5 12:07:44 yesfletchmain sshd\[17329\]: Invalid user support from 103.81.156.10 port 48864
Feb  5 12:07:44 yesfletchmain sshd\[17329\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.81.156.10
Feb  5 12:07:46 yesfletchmain sshd\[17329\]: Failed password for invalid user support from 103.81.156.10 port 48864 ssh2
Feb  5 12:10:18 yesfletchmain sshd\[17473\]: User root from 103.81.156.10 not allowed because not listed in AllowUsers
Feb  5 12:10:18 yesfletchmain sshd\[17473\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.81.156.10  user=root
...
2020-04-03 05:46:13
101.91.114.27 attackspambots
Mar 31 13:20:15 yesfletchmain sshd\[7703\]: Invalid user so from 101.91.114.27 port 41708
Mar 31 13:20:15 yesfletchmain sshd\[7703\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.91.114.27
Mar 31 13:20:17 yesfletchmain sshd\[7703\]: Failed password for invalid user so from 101.91.114.27 port 41708 ssh2
Mar 31 13:24:53 yesfletchmain sshd\[7850\]: User root from 101.91.114.27 not allowed because not listed in AllowUsers
Mar 31 13:24:53 yesfletchmain sshd\[7850\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.91.114.27  user=root
...
2020-04-03 05:43:47

Recently Reported IPs

15.206.98.85 182.49.248.52 68.183.190.10 41.35.44.170
186.150.202.235 253.123.102.161 24.4.128.189 5.189.157.90
221.142.138.30 118.56.121.178 173.249.4.73 208.102.21.209
160.96.6.63 125.77.30.107 109.123.117.234 101.174.169.94
88.99.103.29 66.214.125.12 61.94.111.11 43.228.71.4