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

;; QUESTION SECTION:
;134.119.240.106.		IN	A

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

;; Query time: 26 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 12:17:04 CST 2022
;; MSG SIZE  rcvd: 108
Host info
106.240.119.134.in-addr.arpa domain name pointer m20s2-1-20db.ispgateway.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
106.240.119.134.in-addr.arpa	name = m20s2-1-20db.ispgateway.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
201.26.218.239 attackbotsspam
445/tcp
[2019-06-23]1pkt
2019-06-24 05:06:41
188.131.237.17 attackspam
Jun 23 22:33:07 giegler sshd[14428]: Invalid user tq from 188.131.237.17 port 56088
Jun 23 22:33:09 giegler sshd[14428]: Failed password for invalid user tq from 188.131.237.17 port 56088 ssh2
Jun 23 22:33:07 giegler sshd[14428]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.131.237.17
Jun 23 22:33:07 giegler sshd[14428]: Invalid user tq from 188.131.237.17 port 56088
Jun 23 22:33:09 giegler sshd[14428]: Failed password for invalid user tq from 188.131.237.17 port 56088 ssh2
2019-06-24 04:46:09
162.243.150.154 attackbotsspam
Port scan: Attack repeated for 24 hours
2019-06-24 05:11:03
120.194.172.176 attack
failed_logins
2019-06-24 05:16:59
203.104.193.31 attack
Brute force attempt
2019-06-24 04:48:56
171.245.206.134 attackspambots
23/tcp
[2019-06-23]1pkt
2019-06-24 05:15:59
62.4.21.103 attackbots
SIP Server BruteForce Attack
2019-06-24 04:46:36
134.209.15.14 attackbotsspam
Jun 23 23:35:40 server2 sshd\[879\]: User root from 134.209.15.14 not allowed because not listed in AllowUsers
Jun 23 23:35:43 server2 sshd\[881\]: Invalid user admin from 134.209.15.14
Jun 23 23:35:45 server2 sshd\[883\]: User root from 134.209.15.14 not allowed because not listed in AllowUsers
Jun 23 23:35:47 server2 sshd\[887\]: Invalid user admin from 134.209.15.14
Jun 23 23:35:49 server2 sshd\[899\]: Invalid user user from 134.209.15.14
Jun 23 23:35:52 server2 sshd\[903\]: Invalid user user from 134.209.15.14
2019-06-24 04:51:52
114.25.132.91 attack
37215/tcp
[2019-06-23]1pkt
2019-06-24 04:59:59
170.100.8.254 attackbots
On mail server
2019-06-24 05:13:08
61.12.38.162 attackbots
Jun 23 22:55:12 atlassian sshd[5596]: Invalid user kai from 61.12.38.162 port 60774
2019-06-24 05:01:43
118.200.41.41 attackbots
SSH Brute Force, server-1 sshd[30369]: Failed password for invalid user jb from 118.200.41.41 port 51640 ssh2
2019-06-24 04:53:34
187.121.21.32 attackbotsspam
TCP port 23 (Telnet) attempt blocked by firewall. [2019-06-23 22:09:32]
2019-06-24 05:19:06
123.23.62.11 attackbots
445/tcp
[2019-06-23]1pkt
2019-06-24 04:53:00
200.105.241.90 attack
Unauthorized connection attempt from IP address 200.105.241.90 on Port 445(SMB)
2019-06-24 05:22:14

Recently Reported IPs

134.119.247.22 134.119.249.26 134.119.253.165 134.119.253.180
134.119.253.193 134.119.253.197 134.119.253.79 134.119.253.207
134.119.35.232 134.119.29.129 134.119.44.37 134.119.40.38
134.119.253.60 134.119.45.140 241.150.219.30 134.119.45.166
134.119.45.159 134.119.45.213 134.119.86.229 134.119.45.222