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

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

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

;; Query time: 106 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Mar 29 08:58:54 CST 2020
;; MSG SIZE  rcvd: 117
Host info
Host 221.92.86.134.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 221.92.86.134.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
39.32.235.59 attackbotsspam
Honeypot attack, port: 445, PTR: PTR record not found
2020-02-08 17:34:55
221.248.106.106 attack
Honeypot attack, port: 139, PTR: 221x248x106x106.ap221.ftth.ucom.ne.jp.
2020-02-08 17:33:04
189.7.17.61 attack
Fail2Ban - SSH Bruteforce Attempt
2020-02-08 17:49:31
54.223.144.91 attackbots
Feb  8 09:15:32 mout sshd[16600]: Invalid user xni from 54.223.144.91 port 57855
2020-02-08 17:47:53
92.118.37.67 attackbotsspam
Feb  8 10:39:08 [host] kernel: [4353809.744353] [U
Feb  8 10:44:47 [host] kernel: [4354148.944074] [U
Feb  8 10:48:32 [host] kernel: [4354373.268946] [U
Feb  8 11:02:21 [host] kernel: [4355202.654918] [U
Feb  8 11:02:33 [host] kernel: [4355214.312668] [U
Feb  8 11:04:29 [host] kernel: [4355330.500918] [U
2020-02-08 18:05:53
114.119.37.143 attackspambots
CN_APNIC-HM_<177>1581137610 [1:2010935:3] ET SCAN Suspicious inbound to MSSQL port 1433 [Classification: Potentially Bad Traffic] [Priority: 2] {TCP} 114.119.37.143:56742
2020-02-08 17:41:06
73.167.84.250 attack
Feb  8 08:26:33 lnxded64 sshd[10361]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=73.167.84.250
2020-02-08 17:33:36
109.75.37.20 attackbots
Feb  8 05:53:21 debian-2gb-nbg1-2 kernel: \[3396842.090193\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=109.75.37.20 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=51 ID=31727 PROTO=TCP SPT=44851 DPT=88 WINDOW=32019 RES=0x00 SYN URGP=0
2020-02-08 17:46:00
106.13.86.136 attack
Automatic report - SSH Brute-Force Attack
2020-02-08 17:30:46
69.229.6.10 attack
Feb  8 09:42:44 legacy sshd[25705]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.229.6.10
Feb  8 09:42:46 legacy sshd[25705]: Failed password for invalid user eej from 69.229.6.10 port 36922 ssh2
Feb  8 09:48:08 legacy sshd[26057]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.229.6.10
...
2020-02-08 17:40:41
119.92.241.82 attack
Automatic report - Port Scan Attack
2020-02-08 18:02:39
142.93.83.218 attackbotsspam
Feb  8 06:04:47 srv-ubuntu-dev3 sshd[34041]: Invalid user ntz from 142.93.83.218
Feb  8 06:04:47 srv-ubuntu-dev3 sshd[34041]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.83.218
Feb  8 06:04:47 srv-ubuntu-dev3 sshd[34041]: Invalid user ntz from 142.93.83.218
Feb  8 06:04:49 srv-ubuntu-dev3 sshd[34041]: Failed password for invalid user ntz from 142.93.83.218 port 39128 ssh2
Feb  8 06:07:48 srv-ubuntu-dev3 sshd[34301]: Invalid user bxz from 142.93.83.218
Feb  8 06:07:48 srv-ubuntu-dev3 sshd[34301]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.83.218
Feb  8 06:07:48 srv-ubuntu-dev3 sshd[34301]: Invalid user bxz from 142.93.83.218
Feb  8 06:07:50 srv-ubuntu-dev3 sshd[34301]: Failed password for invalid user bxz from 142.93.83.218 port 40686 ssh2
Feb  8 06:10:47 srv-ubuntu-dev3 sshd[34751]: Invalid user km from 142.93.83.218
...
2020-02-08 18:00:05
122.172.103.229 attackbots
Automatic report - Port Scan Attack
2020-02-08 17:39:41
45.251.56.49 attackbots
2020-02-08T07:06:40.702263jeroenwennink sshd[2525]: Did not receive identification string from 45.251.56.49 port 62101
2020-02-08T07:06:53.112912jeroenwennink sshd[2543]: Invalid user support from 45.251.56.49 port 63274
2020-02-08T07:06:54.232874jeroenwennink sshd[2543]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.251.56.49
2020-02-08T07:06:53.112912jeroenwennink sshd[2543]: Invalid user support from 45.251.56.49 port 63274
2020-02-08T07:06:56.857326jeroenwennink sshd[2543]: Failed password for invalid user support from 45.251.56.49 port 63274 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=45.251.56.49
2020-02-08 17:36:19
111.75.222.141 attackspam
Honeypot attack, port: 445, PTR: PTR record not found
2020-02-08 17:52:05

Recently Reported IPs

114.228.155.59 181.211.252.186 179.83.5.96 9.67.114.145
106.13.97.10 193.93.76.91 217.112.142.78 123.113.191.199
1.51.87.219 200.155.116.176 35.108.37.111 154.121.235.231
110.228.249.61 158.158.76.186 157.135.25.22 62.138.42.154
255.197.132.163 39.155.215.146 165.35.153.207 168.74.197.49