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
138.68.30.2 attack
138.68.30.2 - - \[28/Dec/2019:20:38:27 +0100\] "POST /wp-login.php HTTP/1.0" 200 3080 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
138.68.30.2 - - \[28/Dec/2019:20:38:29 +0100\] "POST /wp-login.php HTTP/1.0" 200 3039 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
138.68.30.2 - - \[28/Dec/2019:20:38:32 +0100\] "POST /wp-login.php HTTP/1.0" 200 3048 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-12-29 06:02:51
138.68.30.2 attack
Automatic report - Banned IP Access
2019-11-26 00:59:16
138.68.30.2 attack
11/24/2019-07:29:55.129981 138.68.30.2 Protocol: 6 ET POLICY Cleartext WordPress Login
2019-11-24 14:45:51
138.68.30.68 attackbots
53413/udp 53413/udp 53413/udp...
[2019-10-21/11-21]1223pkt,1pt.(udp)
2019-11-21 19:51:21
138.68.30.68 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-11-10 19:55:08
138.68.30.68 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-11-07 01:08:00
138.68.30.68 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2019-11-01 00:43:09
138.68.30.68 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-10-30 20:32:01
138.68.30.2 attack
WordPress wp-login brute force :: 138.68.30.2 0.116 BYPASS [24/Oct/2019:14:45:53  1100] [censored_1] "POST /wp-login.php HTTP/1.1" 200 3972 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-10-24 18:35:47
138.68.30.2 attack
plussize.fitness 138.68.30.2 \[20/Sep/2019:01:05:51 +0200\] "POST /wp-login.php HTTP/1.1" 200 5629 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
plussize.fitness 138.68.30.2 \[20/Sep/2019:01:05:52 +0200\] "POST /wp-login.php HTTP/1.1" 200 5582 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-09-20 09:02:58
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 138.68.30.74
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 14778
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;138.68.30.74.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 04:04:27 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 74.30.68.138.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 74.30.68.138.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
144.217.89.55 attack
Nov 22 06:14:38 auw2 sshd\[30100\]: Invalid user tomcat from 144.217.89.55
Nov 22 06:14:38 auw2 sshd\[30100\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=55.ip-144-217-89.net
Nov 22 06:14:41 auw2 sshd\[30100\]: Failed password for invalid user tomcat from 144.217.89.55 port 41954 ssh2
Nov 22 06:18:20 auw2 sshd\[30492\]: Invalid user scpuser from 144.217.89.55
Nov 22 06:18:20 auw2 sshd\[30492\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=55.ip-144-217-89.net
2019-11-23 00:53:34
49.235.139.216 attackspam
Nov 22 17:24:02 sd-53420 sshd\[14180\]: Invalid user admin from 49.235.139.216
Nov 22 17:24:02 sd-53420 sshd\[14180\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.139.216
Nov 22 17:24:04 sd-53420 sshd\[14180\]: Failed password for invalid user admin from 49.235.139.216 port 52976 ssh2
Nov 22 17:28:48 sd-53420 sshd\[15575\]: Invalid user tammer from 49.235.139.216
Nov 22 17:28:48 sd-53420 sshd\[15575\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.139.216
...
2019-11-23 01:02:21
193.29.13.20 attackbotsspam
firewall-block, port(s): 33896/tcp
2019-11-23 00:58:41
45.55.173.225 attackbotsspam
Nov 22 18:12:00 server sshd\[30297\]: Invalid user ident from 45.55.173.225 port 52997
Nov 22 18:12:00 server sshd\[30297\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.173.225
Nov 22 18:12:01 server sshd\[30297\]: Failed password for invalid user ident from 45.55.173.225 port 52997 ssh2
Nov 22 18:16:18 server sshd\[17647\]: Invalid user sinusbot from 45.55.173.225 port 42636
Nov 22 18:16:18 server sshd\[17647\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.173.225
2019-11-23 00:34:56
41.196.0.189 attackbotsspam
Nov 22 17:18:24 eventyay sshd[16282]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.196.0.189
Nov 22 17:18:26 eventyay sshd[16282]: Failed password for invalid user daviet from 41.196.0.189 port 34090 ssh2
Nov 22 17:26:31 eventyay sshd[16411]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.196.0.189
...
2019-11-23 00:37:07
91.196.121.49 attack
Spam
2019-11-23 00:51:46
119.49.146.179 attackspam
11/22/2019-09:51:08.987574 119.49.146.179 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-11-23 00:16:12
114.104.235.20 attack
badbot
2019-11-23 00:19:12
180.68.177.15 attackspam
Nov 22 17:48:19 cp sshd[13278]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.68.177.15
Nov 22 17:48:19 cp sshd[13278]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.68.177.15
2019-11-23 00:49:17
5.45.6.66 attackspam
Nov 22 16:16:53 sd-53420 sshd\[25771\]: Invalid user hh123456 from 5.45.6.66
Nov 22 16:16:53 sd-53420 sshd\[25771\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.45.6.66
Nov 22 16:16:55 sd-53420 sshd\[25771\]: Failed password for invalid user hh123456 from 5.45.6.66 port 43022 ssh2
Nov 22 16:19:49 sd-53420 sshd\[26648\]: Invalid user yuanshang01 from 5.45.6.66
Nov 22 16:19:49 sd-53420 sshd\[26648\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.45.6.66
...
2019-11-23 01:00:15
46.38.144.32 attack
Nov 22 17:50:15 webserver postfix/smtpd\[3649\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 22 17:51:27 webserver postfix/smtpd\[3344\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 22 17:52:39 webserver postfix/smtpd\[3344\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 22 17:53:46 webserver postfix/smtpd\[3344\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 22 17:55:03 webserver postfix/smtpd\[3344\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-11-23 00:55:45
117.175.128.188 attackspambots
badbot
2019-11-23 00:56:56
222.186.180.41 attackspambots
Nov 22 17:40:02 SilenceServices sshd[18853]: Failed password for root from 222.186.180.41 port 30276 ssh2
Nov 22 17:40:06 SilenceServices sshd[18853]: Failed password for root from 222.186.180.41 port 30276 ssh2
Nov 22 17:40:17 SilenceServices sshd[18853]: Failed password for root from 222.186.180.41 port 30276 ssh2
Nov 22 17:40:17 SilenceServices sshd[18853]: error: maximum authentication attempts exceeded for root from 222.186.180.41 port 30276 ssh2 [preauth]
2019-11-23 00:43:23
119.28.143.26 attackspam
Nov 22 17:18:33 mout sshd[8645]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.28.143.26  user=root
Nov 22 17:18:35 mout sshd[8645]: Failed password for root from 119.28.143.26 port 32974 ssh2
2019-11-23 00:18:46
185.88.152.64 attack
Automatic report - XMLRPC Attack
2019-11-23 00:47:31

Recently Reported IPs

138.68.26.55 138.68.37.201 138.68.34.161 138.68.39.77
138.68.40.62 138.68.41.104 138.68.46.126 138.68.42.43
138.68.5.82 138.68.40.94 138.68.51.69 138.68.53.193
138.68.54.93 138.68.58.120 138.68.61.232 138.68.61.104
138.68.58.229 138.68.63.70 138.68.66.254 138.68.65.150