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

Country: Germany

Internet Service Provider: LEIBNIZ-RECHENZENTRUM

Hostname: unknown

Organization: Leibniz-Rechenzentrum

Usage Type: Data Center/Web Hosting/Transit

Comments:
Type Details Datetime
attack
Jul  3 13:25:34   TCP Attack: SRC=2001:4ca0:0108:0042:0000:0080:0006:0009 DST=[Masked] LEN=80 TC=0 HOPLIMIT=245 FLOWLBL=0 PROTO=TCP SPT=47595 DPT=80 WINDOW=65535 RES=0x00 SYN URGP=0
2019-07-03 23:35:10
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 2001:4ca0:108:42:0:80:6:9
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30670
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;2001:4ca0:108:42:0:80:6:9.	IN	A

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

;; Query time: 2 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Wed Jul 03 23:34:57 CST 2019
;; MSG SIZE  rcvd: 129
Host info
9.0.0.0.6.0.0.0.0.8.0.0.0.0.0.0.2.4.0.0.8.0.1.0.0.a.c.4.1.0.0.2.ip6.arpa domain name pointer planetlab9.net.in.tum.de.8.0.1.0.0.a.c.4.1.0.0.2.ip6.arpa.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
9.0.0.0.6.0.0.0.0.8.0.0.0.0.0.0.2.4.0.0.8.0.1.0.0.a.c.4.1.0.0.2.ip6.arpa	name = planetlab9.net.in.tum.de.8.0.1.0.0.a.c.4.1.0.0.2.ip6.arpa.

Authoritative answers can be found from:

Related comments:
IP Type Details Datetime
34.80.248.92 attackbots
Mar 17 01:53:12 host sshd[42313]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.248.80.34.bc.googleusercontent.com  user=root
Mar 17 01:53:15 host sshd[42313]: Failed password for root from 34.80.248.92 port 55450 ssh2
...
2020-03-17 09:59:35
88.250.219.234 attackspam
Automatic report - Port Scan Attack
2020-03-17 10:04:54
198.98.62.43 attack
198.98.62.43 was recorded 5 times by 5 hosts attempting to connect to the following ports: 53413. Incident counter (4h, 24h, all-time): 5, 40, 173
2020-03-17 09:54:16
196.217.240.243 attackspam
1433/tcp 1433/tcp
[2020-02-13/03-16]2pkt
2020-03-17 10:04:30
2.44.168.59 attackbots
23/tcp 81/tcp
[2020-02-11/03-16]2pkt
2020-03-17 10:11:57
40.97.212.117 attackbotsspam
Brute forcing email accounts
2020-03-17 09:47:29
77.42.122.225 attackspam
Automatic report - Port Scan Attack
2020-03-17 09:46:58
60.174.37.226 attackspambots
Wordpress Admin Login attack
2020-03-17 09:43:28
67.8.138.101 attack
Automatic report - Port Scan Attack
2020-03-17 10:21:05
218.92.0.178 attackspam
v+ssh-bruteforce
2020-03-17 09:53:44
113.175.198.134 attackbotsspam
1433/tcp 445/tcp
[2020-03-12/16]2pkt
2020-03-17 10:25:01
185.202.2.237 attackspambots
RDPBruteCAu
2020-03-17 09:48:39
200.32.10.210 attackbots
Unauthorized connection attempt from IP address 200.32.10.210 on Port 445(SMB)
2020-03-17 09:55:49
2.139.155.90 attack
23/tcp 23/tcp 23/tcp
[2020-02-10/03-16]3pkt
2020-03-17 10:02:54
222.186.173.183 attackspambots
Mar 17 02:57:41 SilenceServices sshd[15349]: Failed password for root from 222.186.173.183 port 49576 ssh2
Mar 17 02:57:55 SilenceServices sshd[15349]: error: maximum authentication attempts exceeded for root from 222.186.173.183 port 49576 ssh2 [preauth]
Mar 17 02:58:02 SilenceServices sshd[15475]: Failed password for root from 222.186.173.183 port 19800 ssh2
2020-03-17 10:03:58

Recently Reported IPs

179.99.9.31 2001:4ca0:108:42:0:443:6:9 146.78.157.238 220.193.22.11
104.219.2.148 96.63.16.21 46.101.149.106 117.106.37.236
84.120.41.118 49.176.171.34 155.118.101.182 72.136.17.242
34.77.236.1 218.68.243.133 124.212.160.211 54.244.130.76
2600:387:a:3::1d 107.165.164.2 182.83.138.164 91.196.103.204