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

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

;; QUESTION SECTION:
;218.138.68.161.			IN	A

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

;; Query time: 89 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 06 06:01:31 CST 2022
;; MSG SIZE  rcvd: 107
Host info
161.68.138.218.in-addr.arpa domain name pointer softbank218138068161.bbtec.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
161.68.138.218.in-addr.arpa	name = softbank218138068161.bbtec.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
173.220.206.162 attack
Oct 10 14:22:13 herz-der-gamer sshd[4218]: Invalid user pi from 173.220.206.162 port 5933
...
2019-10-10 20:26:06
137.74.131.224 attackbots
Invalid user pi from 137.74.131.224 port 33254
2019-10-10 20:30:59
124.128.97.146 attackbotsspam
Invalid user ftpuser from 124.128.97.146 port 4015
2019-10-10 20:32:12
188.16.146.219 attackbots
Invalid user admin from 188.16.146.219 port 47410
2019-10-10 20:25:15
129.204.123.216 attackspambots
2019-10-10T13:54:10.801217lon01.zurich-datacenter.net sshd\[18962\]: Invalid user 123 from 129.204.123.216 port 50610
2019-10-10T13:54:10.806457lon01.zurich-datacenter.net sshd\[18962\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.123.216
2019-10-10T13:54:13.146399lon01.zurich-datacenter.net sshd\[18962\]: Failed password for invalid user 123 from 129.204.123.216 port 50610 ssh2
2019-10-10T13:59:08.931270lon01.zurich-datacenter.net sshd\[19064\]: Invalid user q2w3e4r5t6y7 from 129.204.123.216 port 60022
2019-10-10T13:59:08.936151lon01.zurich-datacenter.net sshd\[19064\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.123.216
...
2019-10-10 20:19:09
203.156.63.19 attackbotsspam
203.156.63.19:42724 - - [09/Oct/2019:14:01:46 +0200] "GET /wp-login.php HTTP/1.1" 404 297
2019-10-10 20:14:15
219.73.5.236 attackspam
Unauthorised access (Oct 10) SRC=219.73.5.236 LEN=40 TTL=49 ID=5694 TCP DPT=23 WINDOW=28367 RES=0x30 CWR SYN
2019-10-10 20:08:40
129.204.50.75 attackspam
2019-10-10T16:58:34.020750enmeeting.mahidol.ac.th sshd\[2655\]: User root from 129.204.50.75 not allowed because not listed in AllowUsers
2019-10-10T16:58:34.146619enmeeting.mahidol.ac.th sshd\[2655\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.50.75  user=root
2019-10-10T16:58:35.960349enmeeting.mahidol.ac.th sshd\[2655\]: Failed password for invalid user root from 129.204.50.75 port 56590 ssh2
...
2019-10-10 19:54:29
190.210.42.83 attackbotsspam
Automatic report - Banned IP Access
2019-10-10 19:56:49
43.240.65.236 attackspambots
2019-10-10T13:57:01.175468mail01 postfix/smtpd[27241]: warning: unknown[43.240.65.236]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-10-10T13:58:50.213669mail01 postfix/smtpd[28031]: warning: unknown[43.240.65.236]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-10-10T13:59:22.193040mail01 postfix/smtpd[30331]: warning: unknown[43.240.65.236]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-10-10 20:13:28
206.189.136.160 attackspam
Invalid user postgres from 206.189.136.160 port 40716
2019-10-10 20:21:42
49.88.112.113 attack
Oct 10 13:59:38 MK-Soft-Root2 sshd[22980]: Failed password for root from 49.88.112.113 port 40147 ssh2
Oct 10 13:59:42 MK-Soft-Root2 sshd[22980]: Failed password for root from 49.88.112.113 port 40147 ssh2
...
2019-10-10 20:00:36
180.126.59.16 attackspam
(Oct 10)  LEN=44 TOS=0x10 PREC=0x40 TTL=49 ID=57131 TCP DPT=8080 WINDOW=2203 SYN 
 (Oct  9)  LEN=44 TOS=0x10 PREC=0x40 TTL=49 ID=821 TCP DPT=8080 WINDOW=28504 SYN 
 (Oct  9)  LEN=44 TOS=0x10 PREC=0x40 TTL=49 ID=41115 TCP DPT=8080 WINDOW=37291 SYN 
 (Oct  8)  LEN=44 TOS=0x10 PREC=0x40 TTL=49 ID=2690 TCP DPT=8080 WINDOW=28504 SYN 
 (Oct  8)  LEN=44 TOS=0x10 PREC=0x40 TTL=49 ID=50485 TCP DPT=8080 WINDOW=27337 SYN 
 (Oct  7)  LEN=44 TOS=0x10 PREC=0x40 TTL=49 ID=40779 TCP DPT=8080 WINDOW=27337 SYN 
 (Oct  7)  LEN=44 TOS=0x10 PREC=0x40 TTL=49 ID=39233 TCP DPT=8080 WINDOW=37291 SYN 
 (Oct  6)  LEN=44 TOS=0x10 PREC=0x40 TTL=49 ID=22062 TCP DPT=8080 WINDOW=28504 SYN 
 (Oct  6)  LEN=44 TOS=0x10 PREC=0x40 TTL=49 ID=31213 TCP DPT=8080 WINDOW=27337 SYN 
 (Oct  6)  LEN=44 TOS=0x10 PREC=0x40 TTL=49 ID=42471 TCP DPT=8080 WINDOW=28504 SYN
2019-10-10 20:17:01
157.245.193.75 attackbots
Invalid user support from 157.245.193.75 port 62860
2019-10-10 20:27:56
185.232.67.5 attack
$f2bV_matches_ltvn
2019-10-10 20:10:07

Recently Reported IPs

217.80.112.116 18.213.167.26 243.21.189.78 218.79.115.248
219.33.101.100 22.133.219.100 22.236.139.143 114.185.121.224
175.131.146.165 221.143.68.243 221.77.169.130 154.255.30.162
68.42.18.249 225.29.232.166 78.172.50.209 137.102.84.169
222.90.125.133 223.150.23.152 223.230.69.135 223.66.150.119