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: Frankfurt am Main

Region: Hessen

Country: Germany

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.100.102 attackbotsspam
Lines containing failures of 138.68.100.102
Oct  8 08:42:23 newdogma sshd[22234]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.100.102  user=r.r
Oct  8 08:42:25 newdogma sshd[22234]: Failed password for r.r from 138.68.100.102 port 36538 ssh2
Oct  8 08:42:26 newdogma sshd[22234]: Received disconnect from 138.68.100.102 port 36538:11: Bye Bye [preauth]
Oct  8 08:42:26 newdogma sshd[22234]: Disconnected from authenticating user r.r 138.68.100.102 port 36538 [preauth]
Oct  8 08:58:51 newdogma sshd[22800]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.100.102  user=r.r
Oct  8 08:58:53 newdogma sshd[22800]: Failed password for r.r from 138.68.100.102 port 37066 ssh2
Oct  8 08:58:55 newdogma sshd[22800]: Received disconnect from 138.68.100.102 port 37066:11: Bye Bye [preauth]
Oct  8 08:58:55 newdogma sshd[22800]: Disconnected from authenticating user r.r 138.68.100.102 port 37066........
------------------------------
2020-10-10 02:09:51
138.68.100.102 attackbotsspam
Lines containing failures of 138.68.100.102
Oct  8 08:42:23 newdogma sshd[22234]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.100.102  user=r.r
Oct  8 08:42:25 newdogma sshd[22234]: Failed password for r.r from 138.68.100.102 port 36538 ssh2
Oct  8 08:42:26 newdogma sshd[22234]: Received disconnect from 138.68.100.102 port 36538:11: Bye Bye [preauth]
Oct  8 08:42:26 newdogma sshd[22234]: Disconnected from authenticating user r.r 138.68.100.102 port 36538 [preauth]
Oct  8 08:58:51 newdogma sshd[22800]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.100.102  user=r.r
Oct  8 08:58:53 newdogma sshd[22800]: Failed password for r.r from 138.68.100.102 port 37066 ssh2
Oct  8 08:58:55 newdogma sshd[22800]: Received disconnect from 138.68.100.102 port 37066:11: Bye Bye [preauth]
Oct  8 08:58:55 newdogma sshd[22800]: Disconnected from authenticating user r.r 138.68.100.102 port 37066........
------------------------------
2020-10-09 17:54:43
138.68.100.212 attack
Brute-force attempt banned
2020-09-07 20:26:45
138.68.100.212 attackbotsspam
Sep  7 04:03:16 *** sshd[24427]: Did not receive identification string from 138.68.100.212
2020-09-07 12:11:36
138.68.100.212 attackbotsspam
2020-09-06T22:49:23.908027amanda2.illicoweb.com sshd\[40741\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.100.212  user=root
2020-09-06T22:49:25.914967amanda2.illicoweb.com sshd\[40741\]: Failed password for root from 138.68.100.212 port 53432 ssh2
2020-09-06T22:49:47.395516amanda2.illicoweb.com sshd\[40757\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.100.212  user=root
2020-09-06T22:49:49.698429amanda2.illicoweb.com sshd\[40757\]: Failed password for root from 138.68.100.212 port 60480 ssh2
2020-09-06T22:50:12.493685amanda2.illicoweb.com sshd\[40767\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.100.212  user=root
...
2020-09-07 04:55:20
138.68.100.204 attack
Jul 26 13:58:49 localhost sshd[2093694]: Unable to negotiate with 138.68.100.204 port 42368: no matching key exchange method found. Their offer: diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 [preauth]
...
2020-07-26 12:58:39
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 138.68.100.206
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 41274
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;138.68.100.206.			IN	A

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

;; Query time: 62 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 18 18:19:44 CST 2023
;; MSG SIZE  rcvd: 107
Host info
206.100.68.138.in-addr.arpa domain name pointer 894884.cloudwaysapps.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
206.100.68.138.in-addr.arpa	name = 894884.cloudwaysapps.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
77.107.41.186 attackbotsspam
Unauthorized connection attempt detected from IP address 77.107.41.186 to port 23 [J]
2020-01-05 03:34:23
136.25.25.201 attackspambots
Jan  4 19:58:17 server sshd\[26296\]: Invalid user tn from 136.25.25.201
Jan  4 19:58:17 server sshd\[26296\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.25.25.136.in-addr.arpa 
Jan  4 19:58:20 server sshd\[26296\]: Failed password for invalid user tn from 136.25.25.201 port 45558 ssh2
Jan  4 20:46:34 server sshd\[5104\]: Invalid user ofm from 136.25.25.201
Jan  4 20:46:34 server sshd\[5104\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.25.25.136.in-addr.arpa 
...
2020-01-05 03:12:18
95.32.0.185 attack
Unauthorized connection attempt detected from IP address 95.32.0.185 to port 8080 [J]
2020-01-05 03:15:30
178.217.168.84 attackbots
Unauthorized connection attempt detected from IP address 178.217.168.84 to port 1433 [J]
2020-01-05 03:09:51
103.120.200.42 attack
Unauthorized connection attempt detected from IP address 103.120.200.42 to port 80 [J]
2020-01-05 03:01:08
167.60.20.126 attack
Unauthorized connection attempt detected from IP address 167.60.20.126 to port 23 [J]
2020-01-05 03:27:55
221.220.23.204 attackbotsspam
Unauthorized connection attempt detected from IP address 221.220.23.204 to port 1433 [J]
2020-01-05 03:05:45
200.78.207.229 attackbotsspam
Unauthorized connection attempt detected from IP address 200.78.207.229 to port 23 [J]
2020-01-05 03:08:19
2.144.247.24 attackspam
Unauthorized connection attempt detected from IP address 2.144.247.24 to port 2220 [J]
2020-01-05 03:22:10
81.177.6.164 attackspambots
Unauthorized connection attempt detected from IP address 81.177.6.164 to port 2220 [J]
2020-01-05 03:17:02
106.12.34.160 attackbotsspam
Unauthorized connection attempt detected from IP address 106.12.34.160 to port 2220 [J]
2020-01-05 03:15:14
2.191.187.162 attackbots
Unauthorized connection attempt detected from IP address 2.191.187.162 to port 8080 [J]
2020-01-05 03:21:55
183.82.138.41 attack
Unauthorized connection attempt detected from IP address 183.82.138.41 to port 445 [J]
2020-01-05 03:25:08
41.41.77.154 attackspambots
Unauthorized connection attempt detected from IP address 41.41.77.154 to port 23 [J]
2020-01-05 03:20:41
197.155.40.115 attackbots
Unauthorized connection attempt detected from IP address 197.155.40.115 to port 1433 [J]
2020-01-05 03:24:07

Recently Reported IPs

218.104.197.156 112.172.67.209 216.71.221.255 216.138.115.207
215.122.127.200 115.221.121.48 212.55.26.231 211.69.98.246
59.105.229.210 210.200.155.106 21.222.121.29 208.218.200.68
205.91.132.28 172.105.89.193 205.225.231.238 205.127.79.244
43.205.130.78 204.8.13.142 167.106.31.254 203.169.138.69