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

Region: California

Country: United States

Internet Service Provider: Hurricane Electric LLC

Hostname: unknown

Organization: Hurricane Electric LLC

Usage Type: Data Center/Web Hosting/Transit

Comments:
Type Details Datetime
attack
 TCP (SYN) 216.218.206.68:34288 -> port 443, len 44
2020-09-01 15:36:04
attackspambots
Unauthorized connection attempt detected from IP address 216.218.206.68 to port 4786 [T]
2020-08-16 19:16:15
attackspambots
harvesting idiots since EST 1986
2020-08-09 06:57:33
attack
Unauthorized connection attempt detected from IP address 216.218.206.68 to port 5900
2020-07-22 03:50:16
attackbots
Unauthorized connection attempt detected from IP address 216.218.206.68 to port 23
2020-07-19 05:01:21
attackspambots
Unauthorized connection attempt detected from IP address 216.218.206.68 to port 8080
2020-07-06 22:09:28
attackspam
Fail2Ban Ban Triggered
2020-04-27 22:34:19
attackspambots
srv02 Mass scanning activity detected Target: 50070  ..
2020-04-26 01:08:30
attackspambots
Unauthorized connection attempt detected from IP address 216.218.206.68 to port 7547
2020-03-17 21:38:29
attack
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-20 04:20:59
attackspam
TCP port 3389: Scan and connection
2020-02-07 03:09:42
attackspambots
Unauthorized connection attempt detected from IP address 216.218.206.68 to port 3389
2019-12-29 19:09:31
attackspam
Unauthorized connection attempt detected from IP address 216.218.206.68 to port 8443
2019-12-29 02:33:59
attack
scan r
2019-12-14 17:24:00
attackbotsspam
scan r
2019-12-04 20:07:27
attackbots
Connection by 216.218.206.68 on port: 6379 got caught by honeypot at 11/12/2019 1:38:18 PM
2019-11-13 02:03:58
attackspam
scan z
2019-11-06 15:47:17
attackbots
19/9/25@04:16:56: FAIL: Alarm-Intrusion address from=216.218.206.68
...
2019-09-25 18:29:11
attackspambots
19/7/28@07:28:36: FAIL: Alarm-Intrusion address from=216.218.206.68
...
2019-07-28 21:38:21
attackbots
port scan and connect, tcp 27017 (mongodb)
2019-07-20 23:22:10
attackbots
3389BruteforceFW21
2019-07-08 21:42:56
attack
Port scan: Attack repeated for 24 hours 216.218.206.68 - - [06/Jul/2018:16:42:39  0300] "GET / HTTP/1.1" 404 1832 "-" "-"
216.218.206.68 - - [24/Jun/2018:18:29:56  0300] "GET / HTTP/1.1" 404 1832 "-" "-"
216.218.206.68 - - [28/Jun/2018:18:26:34  0300] "GET / HTTP/1.1" 404 1832 "-" "-"
2019-07-07 16:48:12
attackbotsspam
3389BruteforceFW22
2019-07-01 19:47:33
attack
7547/tcp 5900/tcp 6379/tcp...
[2019-04-23/06-22]24pkt,17pt.(tcp)
2019-06-22 23:43:32
Comments on same subnet:
IP Type Details Datetime
216.218.206.72 attackproxy
Vulnerability Scanner
2025-06-26 12:55:51
216.218.206.102 proxy
Vulnerability Scanner
2024-08-22 21:15:28
216.218.206.101 botsattackproxy
SMB bot
2024-06-19 20:50:36
216.218.206.125 attackproxy
Vulnerability Scanner
2024-04-25 21:28:54
216.218.206.55 spam
There is alot of spammers at uphsl.edu.ph aka a0800616@uphsl.edu.ph
2023-08-08 01:09:41
216.218.206.92 proxy
VPN
2023-01-23 13:58:39
216.218.206.66 proxy
VPN
2023-01-20 13:48:44
216.218.206.126 proxy
Attack VPN
2022-12-08 13:51:17
216.218.206.90 attackproxy
ataque a router
2021-05-17 12:16:31
216.218.206.102 attackproxy
ataque a mi router
2021-05-17 12:12:18
216.218.206.86 attack
This IP has been trying for about a month (since then I noticed) to try to connect via VPN / WEB to the router using different accounts (admin, root, vpn, test, etc.). What does an ISP do in this situation?

May/06/2021 03:52:17 216.218.206.82 failed to get valid proposal.
May/06/2021 03:52:17 216.218.206.82 failed to pre-process ph1 packet (side: 1, status 1).
May/06/2021 03:52:17 216.218.206.82 phase1 negotiation failed.
2021-05-06 19:38:14
216.218.206.97 attack
Port scan: Attack repeated for 24 hours
2020-10-14 01:00:06
216.218.206.97 attackspam
srv02 Mass scanning activity detected Target: 1434(ms-sql-m) ..
2020-10-13 16:10:07
216.218.206.97 attackspambots
srv02 Mass scanning activity detected Target: 445(microsoft-ds) ..
2020-10-13 08:45:33
216.218.206.106 attack
UDP port : 500
2020-10-12 22:22:49
Whois info:
b
Dig info:

; <<>> DiG 9.10.3-P4-Ubuntu <<>> 216.218.206.68
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 32845
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 74 msec
;; SERVER: 67.207.67.3#53(67.207.67.3)
;; WHEN: Mon Apr 22 22:40:28 +08 2019
;; MSG SIZE  rcvd: 118

Host info
68.206.218.216.in-addr.arpa is an alias for 68.64-26.206.218.216.in-addr.arpa.
68.64-26.206.218.216.in-addr.arpa domain name pointer scan-07.shadowserver.org.
Nslookup info:
Server:		67.207.67.3
Address:	67.207.67.3#53

Non-authoritative answer:
68.206.218.216.in-addr.arpa	canonical name = 68.64-26.206.218.216.in-addr.arpa.
68.64-26.206.218.216.in-addr.arpa	name = scan-07.shadowserver.org.

Authoritative answers can be found from:

Related IP info:
Related comments:
IP Type Details Datetime
111.68.125.233 attackspambots
Mar 25 13:47:03 debian-2gb-nbg1-2 kernel: \[7399503.187359\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=111.68.125.233 DST=195.201.40.59 LEN=44 TOS=0x00 PREC=0x00 TTL=52 ID=0 DF PROTO=TCP SPT=80 DPT=24452 WINDOW=14600 RES=0x00 ACK SYN URGP=0
2020-03-26 01:58:11
184.154.189.92 attackspambots
Honeypot attack, port: 445, PTR: sh-chi-us-gp1-wk111.internet-census.org.
2020-03-26 01:52:29
91.196.222.194 attackbots
1585140463 - 03/25/2020 13:47:43 Host: 91.196.222.194/91.196.222.194 Port: 161 UDP Blocked
...
2020-03-26 01:13:56
211.253.9.160 attackbots
Mar 25 18:44:47 ns381471 sshd[24395]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.253.9.160
Mar 25 18:44:49 ns381471 sshd[24395]: Failed password for invalid user ubuntu from 211.253.9.160 port 44908 ssh2
2020-03-26 01:45:45
111.229.126.37 attack
Mar 25 18:15:08 Ubuntu-1404-trusty-64-minimal sshd\[3124\]: Invalid user dedicated from 111.229.126.37
Mar 25 18:15:08 Ubuntu-1404-trusty-64-minimal sshd\[3124\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.229.126.37
Mar 25 18:15:10 Ubuntu-1404-trusty-64-minimal sshd\[3124\]: Failed password for invalid user dedicated from 111.229.126.37 port 45578 ssh2
Mar 25 18:26:45 Ubuntu-1404-trusty-64-minimal sshd\[9212\]: Invalid user kristo from 111.229.126.37
Mar 25 18:26:45 Ubuntu-1404-trusty-64-minimal sshd\[9212\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.229.126.37
2020-03-26 01:44:39
122.152.197.6 attackbotsspam
Mar 25 13:47:16 santamaria sshd\[17156\]: Invalid user shuyang from 122.152.197.6
Mar 25 13:47:16 santamaria sshd\[17156\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.152.197.6
Mar 25 13:47:18 santamaria sshd\[17156\]: Failed password for invalid user shuyang from 122.152.197.6 port 59012 ssh2
...
2020-03-26 01:39:54
38.143.23.189 attack
Mar 25 13:46:54  exim[24525]: [1\51] 1jH5Qr-0006NZ-CR H=(rhythm.anidorai.com) [38.143.23.189] F= rejected after DATA: This message scored 102.9 spam points.
2020-03-26 01:54:41
122.160.82.142 attackbotsspam
Invalid user discordbot from 122.160.82.142 port 59740
2020-03-26 01:48:18
118.97.23.33 attack
Mar 24 03:39:06 pi sshd[16321]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.97.23.33 
Mar 24 03:39:07 pi sshd[16321]: Failed password for invalid user www from 118.97.23.33 port 51928 ssh2
2020-03-26 01:21:38
27.210.154.245 attackbots
Unauthorised access (Mar 25) SRC=27.210.154.245 LEN=40 TTL=49 ID=56494 TCP DPT=8080 WINDOW=22624 SYN 
Unauthorised access (Mar 25) SRC=27.210.154.245 LEN=40 TTL=49 ID=40745 TCP DPT=8080 WINDOW=42942 SYN 
Unauthorised access (Mar 24) SRC=27.210.154.245 LEN=40 TTL=49 ID=38265 TCP DPT=8080 WINDOW=25614 SYN 
Unauthorised access (Mar 22) SRC=27.210.154.245 LEN=40 TTL=49 ID=8790 TCP DPT=8080 WINDOW=13821 SYN
2020-03-26 01:36:07
14.82.72.217 attackspambots
Mar 25 13:47:11 debian-2gb-nbg1-2 kernel: \[7399511.616250\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=14.82.72.217 DST=195.201.40.59 LEN=44 TOS=0x00 PREC=0x00 TTL=46 ID=0 DF PROTO=TCP SPT=7547 DPT=22529 WINDOW=14600 RES=0x00 ACK SYN URGP=0
2020-03-26 01:48:45
49.51.171.154 attackspam
SSH Bruteforce attack
2020-03-26 01:55:12
42.119.100.140 attackspambots
20/3/25@08:47:44: FAIL: Alarm-Network address from=42.119.100.140
...
2020-03-26 01:12:11
222.186.30.57 attackspam
Mar 25 18:28:26 vps691689 sshd[2847]: Failed password for root from 222.186.30.57 port 43720 ssh2
Mar 25 18:28:28 vps691689 sshd[2847]: Failed password for root from 222.186.30.57 port 43720 ssh2
Mar 25 18:28:31 vps691689 sshd[2847]: Failed password for root from 222.186.30.57 port 43720 ssh2
...
2020-03-26 01:36:53
122.116.75.124 attackbots
Invalid user ts3 from 122.116.75.124 port 59572
2020-03-26 01:59:14

Recently Reported IPs

115.16.71.128 115.157.95.124 117.171.179.180 198.108.66.58
212.161.33.218 3.129.103.55 198.108.66.59 134.171.222.26
52.27.14.143 102.150.42.77 198.108.66.90 201.248.126.169
83.102.218.92 34.109.156.81 146.80.123.238 214.247.35.192
198.108.66.91 163.51.152.30 54.86.251.109 45.61.167.19