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: DigitalOcean LLC

Hostname: unknown

Organization: unknown

Usage Type: Data Center/Web Hosting/Transit

Comments:
Type Details Datetime
attackspambots
port scan and connect, tcp 27019 (mongodb-cluster-alt)
2019-09-12 10:38:27
Comments on same subnet:
IP Type Details Datetime
138.68.208.8 proxy
aggressive VPN
2023-03-02 13:44:21
138.68.208.196 attackspam
port scan and connect, tcp 465 (smtps)
2019-09-10 14:05:23
138.68.208.175 attack
Hits on port : 4786
2019-09-10 14:01:28
138.68.208.157 attack
09/09/2019-21:20:20.000896 138.68.208.157 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-09-10 12:42:27
138.68.208.97 attackspam
firewall-block, port(s): 50000/tcp
2019-09-10 02:50:47
138.68.208.190 attackbotsspam
Portscan or hack attempt detected by psad/fwsnort
2019-09-09 18:11:54
138.68.208.157 attackbots
135/tcp 5672/tcp 5632/udp...
[2019-09-06/08]5pkt,4pt.(tcp),1pt.(udp)
2019-09-09 12:12:58
138.68.208.175 attackspam
587/tcp 2362/udp 808/tcp
[2019-09-06/08]3pkt
2019-09-09 12:10:41
138.68.208.152 attackspambots
port scan and connect, tcp 5432 (postgresql)
2019-09-09 12:05:11
138.68.208.25 attackspam
8080/tcp 995/tcp 8123/tcp...
[2019-09-06/08]4pkt,4pt.(tcp)
2019-09-09 12:01:28
138.68.208.69 attackbotsspam
port scan and connect, tcp 2638 (sql-anywhere)
2019-09-09 11:37:28
138.68.208.159 attack
SASL Brute Force
2019-09-09 11:31:02
138.68.208.45 attackbotsspam
SASL Brute Force
2019-09-09 06:13:41
138.68.208.48 attackbots
Lines containing failures of 138.68.208.48


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=138.68.208.48
2019-09-09 04:16:38
138.68.208.149 attackbots
992/tcp 465/tcp 9042/tcp...
[2019-09-06/07]5pkt,5pt.(tcp)
2019-09-08 20:47:03
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 138.68.208.39
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62003
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 3 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Thu Sep 12 10:38:21 CST 2019
;; MSG SIZE  rcvd: 117
Host info
39.208.68.138.in-addr.arpa domain name pointer zg-0905a-110.stretchoid.com.
Nslookup info:
Server:		67.207.67.2
Address:	67.207.67.2#53

Non-authoritative answer:
39.208.68.138.in-addr.arpa	name = zg-0905a-110.stretchoid.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
193.32.163.123 attackbots
auto-add
2019-12-01 20:01:47
119.194.91.157 attack
Fail2Ban Ban Triggered
2019-12-01 19:53:38
12.207.39.227 attackbotsspam
UTC: 2019-11-30 port: 23/tcp
2019-12-01 20:14:46
2.229.92.112 attackspambots
Nov 30 20:55:01 web1 sshd\[10266\]: Invalid user walmsley from 2.229.92.112
Nov 30 20:55:01 web1 sshd\[10266\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=2.229.92.112
Nov 30 20:55:03 web1 sshd\[10266\]: Failed password for invalid user walmsley from 2.229.92.112 port 48968 ssh2
Nov 30 20:57:03 web1 sshd\[10460\]: Invalid user walmsley from 2.229.92.112
Nov 30 20:57:03 web1 sshd\[10460\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=2.229.92.112
2019-12-01 20:15:01
93.178.40.238 attackspambots
UTC: 2019-11-30 port: 26/tcp
2019-12-01 19:57:17
180.165.255.155 attack
This person that owns this ip address has been trying to hack in my email from China. Please be aware.
2019-12-01 19:46:01
85.12.208.134 attackbots
UTC: 2019-11-30 pkts: 2 port: 80/tcp
2019-12-01 19:54:31
74.82.47.17 attack
5900/tcp 548/tcp 27017/tcp...
[2019-10-03/12-01]28pkt,10pt.(tcp),1pt.(udp)
2019-12-01 19:43:07
37.195.50.41 attack
(sshd) Failed SSH login from 37.195.50.41 (RU/Russia/l37-195-50-41.novotelecom.ru): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Dec  1 10:37:18 s1 sshd[18038]: Invalid user darius from 37.195.50.41 port 40410
Dec  1 10:37:21 s1 sshd[18038]: Failed password for invalid user darius from 37.195.50.41 port 40410 ssh2
Dec  1 10:51:19 s1 sshd[18335]: Failed password for root from 37.195.50.41 port 49662 ssh2
Dec  1 10:55:41 s1 sshd[18416]: Invalid user ben from 37.195.50.41 port 56406
Dec  1 10:55:44 s1 sshd[18416]: Failed password for invalid user ben from 37.195.50.41 port 56406 ssh2
2019-12-01 20:18:41
180.153.59.105 attackbotsspam
fail2ban
2019-12-01 20:06:45
149.71.51.137 attack
UTC: 2019-11-30 port: 81/tcp
2019-12-01 19:39:18
186.50.30.170 attack
UTC: 2019-11-30 port: 23/tcp
2019-12-01 20:11:01
109.121.136.19 attack
Dec  1 01:25:28 web9 sshd\[2486\]: Invalid user fitzsimons from 109.121.136.19
Dec  1 01:25:28 web9 sshd\[2486\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.121.136.19
Dec  1 01:25:31 web9 sshd\[2486\]: Failed password for invalid user fitzsimons from 109.121.136.19 port 40411 ssh2
Dec  1 01:29:00 web9 sshd\[2942\]: Invalid user samarat from 109.121.136.19
Dec  1 01:29:00 web9 sshd\[2942\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.121.136.19
2019-12-01 19:52:04
80.82.70.118 attackbots
12/01/2019-12:21:20.344829 80.82.70.118 Protocol: 6 ET CINS Active Threat Intelligence Poor Reputation IP group 82
2019-12-01 20:05:31
120.77.223.23 attack
Unauthorised access (Dec  1) SRC=120.77.223.23 LEN=60 TTL=46 ID=17875 DF TCP DPT=8080 WINDOW=29200 SYN
2019-12-01 20:11:50

Recently Reported IPs

184.183.166.23 115.53.61.59 133.176.158.164 177.223.136.140
154.47.98.24 103.79.156.199 75.132.169.12 98.198.138.96
45.235.131.130 88.250.141.34 13.161.174.219 90.95.62.27
1.133.92.187 208.75.123.179 25.234.190.203 75.33.111.88
61.110.210.81 167.49.65.99 26.27.136.162 137.251.201.152