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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 138.201.80.60
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12504
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;138.201.80.60.			IN	A

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

;; Query time: 93 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 11:57:12 CST 2022
;; MSG SIZE  rcvd: 106
Host info
60.80.201.138.in-addr.arpa domain name pointer static.60.80.201.138.clients.your-server.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

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

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
106.13.49.20 attack
Automatic report - Banned IP Access
2020-02-08 16:29:16
124.29.232.173 attackbots
20/2/7@23:54:29: FAIL: Alarm-Network address from=124.29.232.173
20/2/7@23:54:29: FAIL: Alarm-Network address from=124.29.232.173
...
2020-02-08 16:58:49
177.245.195.51 attackbotsspam
Automatic report - Port Scan Attack
2020-02-08 17:13:20
94.181.80.3 attackbots
Feb  8 06:00:08 debian-2gb-nbg1-2 kernel: \[3397248.864123\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=94.181.80.3 DST=195.201.40.59 LEN=60 TOS=0x10 PREC=0x60 TTL=118 ID=6960 DF PROTO=TCP SPT=19700 DPT=22 WINDOW=8192 RES=0x00 SYN URGP=0
2020-02-08 16:54:10
79.120.56.250 attack
Honeypot attack, port: 445, PTR: ppp-250-248.utech.ru.
2020-02-08 16:32:01
47.247.143.1 attackspam
Honeypot attack, port: 445, PTR: PTR record not found
2020-02-08 16:40:45
36.85.222.224 attackspambots
Feb  8 09:54:48 mail sshd\[16805\]: Invalid user toor from 36.85.222.224
Feb  8 09:54:49 mail sshd\[16805\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.85.222.224
Feb  8 09:54:50 mail sshd\[16805\]: Failed password for invalid user toor from 36.85.222.224 port 31219 ssh2
...
2020-02-08 17:07:31
220.157.159.69 attack
Honeypot attack, port: 445, PTR: s159069.dynamic.ppp.asahi-net.or.jp.
2020-02-08 16:42:20
198.46.81.54 attack
[munged]::443 198.46.81.54 - - [08/Feb/2020:05:51:47 +0100] "POST /[munged]: HTTP/1.1" 200 5658 "-" "-"
[munged]::443 198.46.81.54 - - [08/Feb/2020:05:52:04 +0100] "POST /[munged]: HTTP/1.1" 200 5658 "-" "-"
[munged]::443 198.46.81.54 - - [08/Feb/2020:05:52:19 +0100] "POST /[munged]: HTTP/1.1" 200 5658 "-" "-"
[munged]::443 198.46.81.54 - - [08/Feb/2020:05:52:35 +0100] "POST /[munged]: HTTP/1.1" 200 5658 "-" "-"
[munged]::443 198.46.81.54 - - [08/Feb/2020:05:52:51 +0100] "POST /[munged]: HTTP/1.1" 200 5658 "-" "-"
[munged]::443 198.46.81.54 - - [08/Feb/2020:05:53:07 +0100] "POST /[munged]: HTTP/1.1" 200 5658 "-" "-"
[munged]::443 198.46.81.54 - - [08/Feb/2020:05:53:23 +0100] "POST /[munged]: HTTP/1.1" 200 5658 "-" "-"
[munged]::443 198.46.81.54 - - [08/Feb/2020:05:53:40 +0100] "POST /[munged]: HTTP/1.1" 200 5658 "-" "-"
[munged]::443 198.46.81.54 - - [08/Feb/2020:05:53:55 +0100] "POST /[munged]: HTTP/1.1" 200 5658 "-" "-"
[munged]::443 198.46.81.54 - - [08/Feb/2020:05:54:11 +0100] "POST /[munged]: HTTP/1.1" 2
2020-02-08 17:11:34
45.76.171.51 attackspambots
*Port Scan* detected from 45.76.171.51 (US/United States/45.76.171.51.vultr.com). 4 hits in the last 290 seconds
2020-02-08 16:34:01
185.234.216.206 attackbotsspam
smtp attack
2020-02-08 17:05:04
171.100.80.102 attack
Feb  8 04:54:14 *** sshd[32363]: Invalid user admin from 171.100.80.102
2020-02-08 17:09:09
220.133.77.233 attackbotsspam
Fri Feb  7 21:54:14 2020 - Child process 20102 handling connection
Fri Feb  7 21:54:14 2020 - New connection from: 220.133.77.233:45941
Fri Feb  7 21:54:14 2020 - Sending data to client: [Login: ]
Fri Feb  7 21:54:46 2020 - Child aborting
Fri Feb  7 21:54:46 2020 - Reporting IP address: 220.133.77.233 - mflag: 0
2020-02-08 17:10:25
159.203.117.137 attack
Feb  8 09:06:36 vlre-nyc-1 sshd\[22872\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.203.117.137  user=root
Feb  8 09:06:38 vlre-nyc-1 sshd\[22872\]: Failed password for root from 159.203.117.137 port 59052 ssh2
Feb  8 09:07:29 vlre-nyc-1 sshd\[22881\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.203.117.137  user=root
Feb  8 09:07:31 vlre-nyc-1 sshd\[22881\]: Failed password for root from 159.203.117.137 port 38900 ssh2
Feb  8 09:08:22 vlre-nyc-1 sshd\[22901\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.203.117.137  user=root
...
2020-02-08 17:09:29
113.163.182.46 attack
Automatic report - Port Scan Attack
2020-02-08 16:52:34

Recently Reported IPs

138.201.80.43 138.201.81.166 138.201.80.86 138.201.81.170
138.201.82.142 138.201.83.235 138.201.81.95 138.201.84.149
138.201.84.190 138.201.85.108 138.201.81.240 138.201.85.216
138.201.85.232 138.201.85.222 138.201.85.234 138.201.86.136
138.201.86.137 138.201.86.61 138.201.88.140 138.201.88.251