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:
IP Type Details Datetime
134.209.214.75 attack
DigitalOcean BotNet attack - 10s of requests to non-existent pages - :443/app-ads.txt - typically bursts of 8 requests per second - undefined, XSS attacks
node-superagent/4.1.0
2020-03-10 02:49:14
134.209.214.75 attackbotsspam
DigitalOcean BotNet attack - 10s of requests to non-existent pages - :443/app-ads.txt - typically bursts of 8 requests per second - undefined, XSS attacks
node-superagent/4.1.0
2020-02-27 02:50:10
134.209.214.165 attackbots
DigitalOcean BotNet attack - 10s of requests to non-existent pages - :443/app-ads.txt - typically bursts of 8 requests per second - undefined, XSS attacks
node-superagent/4.1.0
2019-12-04 22:34:43
134.209.214.245 attackbotsspam
Jul  5 04:30:37 localhost postfix/smtpd[13391]: lost connection after eclipseT from unknown[134.209.214.245]
Jul x@x
Jul  5 04:30:37 localhost postfix/smtpd[13392]: lost connection after eclipseT from unknown[134.209.214.245]
Jul  5 04:53:26 localhost postfix/smtpd[19374]: lost connection after eclipseT from unknown[134.209.214.245]
Jul x@x


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=134.209.214.245
2019-07-11 18:18:20
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 134.209.214.220
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 13213
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;134.209.214.220.		IN	A

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

;; Query time: 90 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 05:57:15 CST 2022
;; MSG SIZE  rcvd: 108
Host info
Host 220.214.209.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 220.214.209.134.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
178.135.92.143 attack
Unauthorized IMAP connection attempt
2019-12-31 04:39:27
222.186.175.220 attackbots
Dec 30 21:44:22 root sshd[3729]: Failed password for root from 222.186.175.220 port 45118 ssh2
Dec 30 21:44:26 root sshd[3729]: Failed password for root from 222.186.175.220 port 45118 ssh2
Dec 30 21:44:30 root sshd[3729]: Failed password for root from 222.186.175.220 port 45118 ssh2
Dec 30 21:44:35 root sshd[3729]: Failed password for root from 222.186.175.220 port 45118 ssh2
...
2019-12-31 04:47:12
200.82.170.206 attackspambots
port scan and connect, tcp 23 (telnet)
2019-12-31 04:44:44
195.223.30.235 attack
Dec 30 21:25:58 [host] sshd[755]: Invalid user 123password123 from 195.223.30.235
Dec 30 21:25:58 [host] sshd[755]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.223.30.235
Dec 30 21:25:59 [host] sshd[755]: Failed password for invalid user 123password123 from 195.223.30.235 port 36655 ssh2
2019-12-31 04:54:24
176.31.211.52 attack
Dec 30 21:12:17 SilenceServices sshd[1221]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.31.211.52
Dec 30 21:12:20 SilenceServices sshd[1221]: Failed password for invalid user jenkins from 176.31.211.52 port 46136 ssh2
Dec 30 21:13:29 SilenceServices sshd[1525]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.31.211.52
2019-12-31 05:11:20
50.205.116.1 attackspam
Dec 30 21:13:45 debian-2gb-nbg1-2 kernel: \[1389529.796938\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=50.205.116.1 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=49 ID=44168 PROTO=TCP SPT=34092 DPT=8080 WINDOW=53536 RES=0x00 SYN URGP=0
2019-12-31 04:59:08
218.92.0.164 attackbotsspam
k+ssh-bruteforce
2019-12-31 04:49:38
45.224.105.50 attack
Cluster member 192.168.0.31 (-) said, DENY 45.224.105.50, Reason:[(imapd) Failed IMAP login from 45.224.105.50 (AR/Argentina/-): 1 in the last 3600 secs]
2019-12-31 04:42:26
159.203.30.120 attack
Dec 30 21:57:38 localhost sshd\[32268\]: Invalid user lorraine from 159.203.30.120 port 48772
Dec 30 21:57:38 localhost sshd\[32268\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.203.30.120
Dec 30 21:57:40 localhost sshd\[32268\]: Failed password for invalid user lorraine from 159.203.30.120 port 48772 ssh2
2019-12-31 05:08:13
119.202.174.15 attackbotsspam
" "
2019-12-31 04:48:34
112.133.245.29 attackspambots
Automatic report - Port Scan Attack
2019-12-31 05:01:48
77.247.108.14 attackbots
12/30/2019-21:38:08.923111 77.247.108.14 Protocol: 17 ET SCAN Sipvicious Scan
2019-12-31 04:40:06
170.0.125.64 attackspambots
Sent mail to target address hacked/leaked from abandonia in 2016
2019-12-31 05:09:01
201.249.59.205 attackspam
Dec 30 21:13:33 vpn01 sshd[31477]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.249.59.205
Dec 30 21:13:35 vpn01 sshd[31477]: Failed password for invalid user pcap from 201.249.59.205 port 42682 ssh2
...
2019-12-31 05:06:04
144.217.136.227 attack
Dec 30 21:13:42 MK-Soft-Root2 sshd[3884]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.217.136.227 
Dec 30 21:13:45 MK-Soft-Root2 sshd[3884]: Failed password for invalid user caecilie from 144.217.136.227 port 56344 ssh2
...
2019-12-31 05:01:26

Recently Reported IPs

134.209.212.73 134.209.214.209 134.209.214.229 134.209.214.196
134.209.214.204 134.209.213.23 134.209.214.236 118.173.119.131
134.209.214.239 134.209.214.95 134.209.215.13 134.209.214.249
134.209.216.100 134.209.215.105 118.173.119.132 134.209.214.99
134.209.215.51 134.209.215.163 134.209.215.176 134.209.216.135