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: 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.201.123.170 attack
WordPress admin/config access attempt: "GET /wp-admin/"
2020-07-14 16:19:11
138.201.128.9 attack
Triggered: repeated knocking on closed ports.
2020-06-26 01:04:29
138.201.129.164 attackbots
Forbidden directory scan :: 2020/01/24 12:36:14 [error] 1008#1008: *738018 access forbidden by rule, client: 138.201.129.164, server: [censored_1], request: "GET /knowledge-base/tech-tips-tricks/... HTTP/1.1", host: "www.[censored_1]"
2020-01-24 23:56:17
138.201.128.152 attackspam
Sep  7 14:57:54 tdfoods sshd\[5151\]: Invalid user abcde12345 from 138.201.128.152
Sep  7 14:57:54 tdfoods sshd\[5151\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=dawala.nolsatu.id
Sep  7 14:57:56 tdfoods sshd\[5151\]: Failed password for invalid user abcde12345 from 138.201.128.152 port 59720 ssh2
Sep  7 15:01:47 tdfoods sshd\[5484\]: Invalid user 123 from 138.201.128.152
Sep  7 15:01:47 tdfoods sshd\[5484\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=dawala.nolsatu.id
2019-09-08 09:27:57
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 138.201.12.7
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 23980
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;138.201.12.7.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 19 03:37:28 CST 2022
;; MSG SIZE  rcvd: 105
Host info
7.12.201.138.in-addr.arpa domain name pointer static.7.12.201.138.clients.your-server.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
7.12.201.138.in-addr.arpa	name = static.7.12.201.138.clients.your-server.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
111.229.219.226 attackbots
May  8 14:23:41 home sshd[32735]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.229.219.226
May  8 14:23:42 home sshd[32735]: Failed password for invalid user himanshu from 111.229.219.226 port 50238 ssh2
May  8 14:26:04 home sshd[655]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.229.219.226
...
2020-05-09 01:57:41
128.199.76.37 attackspam
2020-05-08T18:01:09.814145v22018076590370373 sshd[1405]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.76.37
2020-05-08T18:01:09.808260v22018076590370373 sshd[1405]: Invalid user customer from 128.199.76.37 port 34963
2020-05-08T18:01:11.620168v22018076590370373 sshd[1405]: Failed password for invalid user customer from 128.199.76.37 port 34963 ssh2
2020-05-08T18:05:03.692522v22018076590370373 sshd[29705]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.76.37  user=root
2020-05-08T18:05:05.953999v22018076590370373 sshd[29705]: Failed password for root from 128.199.76.37 port 60283 ssh2
...
2020-05-09 01:48:56
165.227.6.68 attackbotsspam
May  8 19:33:23 ns381471 sshd[28358]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.6.68
May  8 19:33:25 ns381471 sshd[28358]: Failed password for invalid user web from 165.227.6.68 port 46454 ssh2
2020-05-09 01:42:12
59.52.92.78 attackspambots
Icarus honeypot on github
2020-05-09 01:18:23
222.186.175.202 attack
May  8 17:09:05 ip-172-31-61-156 sshd[13170]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.202  user=root
May  8 17:09:07 ip-172-31-61-156 sshd[13170]: Failed password for root from 222.186.175.202 port 24470 ssh2
...
2020-05-09 01:15:24
221.226.43.62 attack
May  8 10:21:27 ny01 sshd[26811]: Failed password for root from 221.226.43.62 port 44711 ssh2
May  8 10:26:39 ny01 sshd[27885]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.226.43.62
May  8 10:26:41 ny01 sshd[27885]: Failed password for invalid user demo from 221.226.43.62 port 41252 ssh2
2020-05-09 01:45:58
211.169.234.55 attackspam
May  8 19:56:32 home sshd[16154]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.169.234.55
May  8 19:56:34 home sshd[16154]: Failed password for invalid user pratik from 211.169.234.55 port 36132 ssh2
May  8 20:00:54 home sshd[16822]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.169.234.55
...
2020-05-09 02:02:24
162.243.136.126 attack
imap-login: Info: Disconnected (no auth attempts in 10 secs): user=<>, rip=162.243.136.126, lip=, TLS handshaking: SSL_accept() syscall failed: Success, session=<+tTgZSWl9Iei84h+

daft bot
2020-05-09 02:02:36
106.12.33.226 attack
May  8 15:25:29 rotator sshd\[17870\]: Invalid user cps from 106.12.33.226May  8 15:25:31 rotator sshd\[17870\]: Failed password for invalid user cps from 106.12.33.226 port 41212 ssh2May  8 15:30:04 rotator sshd\[17899\]: Invalid user admin from 106.12.33.226May  8 15:30:06 rotator sshd\[17899\]: Failed password for invalid user admin from 106.12.33.226 port 52594 ssh2May  8 15:32:08 rotator sshd\[18658\]: Invalid user vtl from 106.12.33.226May  8 15:32:10 rotator sshd\[18658\]: Failed password for invalid user vtl from 106.12.33.226 port 44172 ssh2
...
2020-05-09 02:07:33
141.98.81.83 attackbotsspam
May  8 18:53:05 piServer sshd[23622]: Failed password for root from 141.98.81.83 port 43543 ssh2
May  8 18:53:36 piServer sshd[23669]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=141.98.81.83 
May  8 18:53:39 piServer sshd[23669]: Failed password for invalid user guest from 141.98.81.83 port 35719 ssh2
...
2020-05-09 01:43:57
137.33.102.114 attackspambots
05/08/2020-14:11:11.749073 137.33.102.114 Protocol: 6 ET DROP Spamhaus DROP Listed Traffic Inbound group 10
2020-05-09 01:40:32
188.234.247.110 attack
$f2bV_matches
2020-05-09 01:15:51
170.246.144.88 attack
Automatic report - Port Scan Attack
2020-05-09 01:21:23
87.64.240.218 attack
(sshd) Failed SSH login from 87.64.240.218 (BE/Belgium/218.240-64-87.adsl-dyn.isp.belgacom.be): 3 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: May  8 12:10:54 andromeda sshd[3026]: Invalid user pi from 87.64.240.218 port 49488
May  8 12:10:54 andromeda sshd[3027]: Invalid user pi from 87.64.240.218 port 49490
May  8 12:10:57 andromeda sshd[3027]: Failed password for invalid user pi from 87.64.240.218 port 49490 ssh2
2020-05-09 01:55:25
206.189.139.179 attack
May  8 16:55:36 mail sshd\[14371\]: Invalid user intranet from 206.189.139.179
May  8 16:55:36 mail sshd\[14371\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.139.179
May  8 16:55:38 mail sshd\[14371\]: Failed password for invalid user intranet from 206.189.139.179 port 55578 ssh2
...
2020-05-09 01:53:24

Recently Reported IPs

138.201.1.148 138.201.205.25 138.201.167.231 138.201.197.207
138.201.193.252 138.201.231.210 138.201.177.98 138.201.192.35
138.201.249.98 138.201.21.43 138.201.55.48 138.201.78.70
138.201.49.67 138.201.8.179 138.201.88.218 138.201.82.97
138.201.93.7 138.68.102.158 138.68.190.116 138.68.247.109