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

Region: New Jersey

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

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

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

;; Query time: 108 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Oct 02 04:44:03 CST 2019
;; MSG SIZE  rcvd: 117
Host info
Host 22.214.22.162.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server:		183.60.82.98
Address:	183.60.82.98#53

** server can't find 22.214.22.162.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
221.214.53.94 attackspam
01/02/2020-15:58:24.741316 221.214.53.94 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2020-01-02 23:08:19
46.101.104.225 attackbotsspam
Jan  2 15:58:16 wordpress wordpress(www.ruhnke.cloud)[98797]: Blocked authentication attempt for admin from ::ffff:46.101.104.225
2020-01-02 23:14:56
106.12.83.146 attack
Jan  2 15:09:33 zeus sshd[12604]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.83.146 
Jan  2 15:09:35 zeus sshd[12604]: Failed password for invalid user rpm from 106.12.83.146 port 37358 ssh2
Jan  2 15:13:33 zeus sshd[12757]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.83.146 
Jan  2 15:13:35 zeus sshd[12757]: Failed password for invalid user hung from 106.12.83.146 port 58844 ssh2
2020-01-02 23:26:47
222.186.30.218 attack
Unauthorized connection attempt detected from IP address 222.186.30.218 to port 22
2020-01-02 22:56:54
119.27.167.231 attack
Automatic report - Banned IP Access
2020-01-02 22:56:27
37.221.194.7 attackbots
Jan  2 08:09:05 dedicated sshd[15073]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.221.194.7  user=root
Jan  2 08:09:07 dedicated sshd[15073]: Failed password for root from 37.221.194.7 port 38526 ssh2
2020-01-02 22:46:45
14.63.194.162 attack
Unauthorized connection attempt detected from IP address 14.63.194.162 to port 22
2020-01-02 23:22:22
103.52.16.35 attackbots
ssh failed login
2020-01-02 23:14:42
49.234.28.54 attackbotsspam
Invalid user benneyworth from 49.234.28.54 port 47998
2020-01-02 22:52:46
222.186.169.192 attack
web-1 [ssh] SSH Attack
2020-01-02 23:18:16
71.198.158.5 attack
ssh failed login
2020-01-02 22:52:30
222.212.82.160 attackbotsspam
Unauthorised access (Jan  2) SRC=222.212.82.160 LEN=40 TTL=53 ID=64168 TCP DPT=23 WINDOW=41321 SYN
2020-01-02 23:10:00
109.116.196.174 attackbots
$f2bV_matches
2020-01-02 22:56:10
27.67.134.138 attackbots
20/1/2@09:57:49: FAIL: Alarm-Network address from=27.67.134.138
20/1/2@09:57:50: FAIL: Alarm-Network address from=27.67.134.138
...
2020-01-02 23:27:28
105.112.98.49 attack
1577977068 - 01/02/2020 15:57:48 Host: 105.112.98.49/105.112.98.49 Port: 445 TCP Blocked
2020-01-02 23:28:58

Recently Reported IPs

134.73.76.230 80.93.182.145 37.111.198.153 79.121.123.35
114.46.119.156 125.24.170.192 64.246.161.42 188.16.150.42
181.70.131.212 60.178.46.169 179.162.89.252 197.162.145.39
162.48.212.129 46.242.61.37 169.247.38.230 18.118.153.16
94.170.85.45 18.221.64.220 177.96.148.92 46.0.149.210