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

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

;; QUESTION SECTION:
;134.119.86.212.			IN	A

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

;; Query time: 55 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 20 21:04:14 CST 2022
;; MSG SIZE  rcvd: 107
Host info
212.86.119.134.in-addr.arpa domain name pointer m21s20-3-32da.ispgateway.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
212.86.119.134.in-addr.arpa	name = m21s20-3-32da.ispgateway.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
193.57.40.11 attackbotsspam
Honeypot hit.
2020-08-04 15:13:10
143.255.130.2 attackbotsspam
detected by Fail2Ban
2020-08-04 14:59:35
156.96.59.24 attackbotsspam
(smtpauth) Failed SMTP AUTH login from 156.96.59.24 (US/United States/-): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: 2020-08-04 08:24:36 login authenticator failed for (DMftYgIf) [156.96.59.24]: 535 Incorrect authentication data (set_id=info)
2020-08-04 15:22:56
186.216.154.234 attackspam
Attempted Brute Force (dovecot)
2020-08-04 15:09:21
222.186.30.76 attack
Unauthorized connection attempt detected from IP address 222.186.30.76 to port 22
2020-08-04 15:41:12
60.165.96.153 attackspambots
08/03/2020-23:54:44.400570 60.165.96.153 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2020-08-04 15:21:49
87.251.74.223 attack
Aug  4 08:39:51 debian-2gb-nbg1-2 kernel: \[18781658.060028\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=87.251.74.223 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=43505 PROTO=TCP SPT=49247 DPT=11086 WINDOW=1024 RES=0x00 SYN URGP=0
2020-08-04 15:16:13
52.156.120.194 attackspam
$f2bV_matches
2020-08-04 15:27:47
119.96.120.113 attack
2020-08-04T05:54:14.803792ks3355764 sshd[27761]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.96.120.113  user=root
2020-08-04T05:54:16.631101ks3355764 sshd[27761]: Failed password for root from 119.96.120.113 port 57980 ssh2
...
2020-08-04 15:37:45
119.29.154.221 attack
Aug  4 07:02:44 [host] sshd[29977]: pam_unix(sshd:
Aug  4 07:02:46 [host] sshd[29977]: Failed passwor
Aug  4 07:04:52 [host] sshd[30118]: pam_unix(sshd:
2020-08-04 15:26:28
213.230.6.17 attackbots
Port probing on unauthorized port 1433
2020-08-04 15:25:42
49.234.41.108 attackbotsspam
$f2bV_matches
2020-08-04 15:10:31
58.23.212.134 attack
Aug  4 08:19:35 vpn01 sshd[13918]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.23.212.134
Aug  4 08:19:38 vpn01 sshd[13918]: Failed password for invalid user postgres from 58.23.212.134 port 47990 ssh2
...
2020-08-04 15:26:58
185.176.27.54 attackspam
08/04/2020-02:32:21.276100 185.176.27.54 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-08-04 15:35:49
112.85.42.237 attackbots
Aug  4 03:13:24 NPSTNNYC01T sshd[23364]: Failed password for root from 112.85.42.237 port 62741 ssh2
Aug  4 03:13:58 NPSTNNYC01T sshd[23406]: Failed password for root from 112.85.42.237 port 13855 ssh2
...
2020-08-04 15:32:15

Recently Reported IPs

128.198.196.207 134.119.62.157 134.119.69.147 134.119.45.90
134.119.86.244 134.119.86.196 134.119.50.87 134.119.96.62
134.122.105.122 134.119.9.121 104.219.54.78 134.122.110.216
134.122.107.78 134.122.110.243 134.119.86.222 134.122.136.3
134.122.163.43 134.122.123.42 134.122.12.193 134.122.0.95